Thư viện tri thức trực tuyến
Kho tài liệu với 50,000+ tài liệu học thuật
© 2023 Siêu thị PDF - Kho tài liệu học thuật hàng đầu Việt Nam

Extreme Programming in Perl Robert Nagler phần 3 pptx
Nội dung xem thử
Mô tả chi tiết
StoryTag This is a mixed-case identifier for the story. Giving a handle
to the story simplifies communication about it. In my experience,
customers tend to have trouble filling in this field in the beginning.
Programmers are used to naming things (subroutines, modules, etc.),
and they may be able to help the customer choose appropriate story
tags.
Release The date or name of the release. We use this field loosely to
categorize stories by release or project. We couldn’t predict when
CloseChase would be done, so we just put it in the Misc category.
Some teams work on several projects simultaneously, and this field
helps keep the story cards organized.
Priority After the customer physically orders the story cards, she writes
their numeric priority in this field. The numbering scheme is arbitrary.
Sometimes you need to insert a story card in the middle of a sequence.
We add a letter, for example, 5a, or use a dotted decimal notation,
5.1. If you drop the story cards, it’s important to be able to get them
back in priority order.
Author The person who wrote the story. You then know whom to ask for
the details.
on The date the story was written.
Accepted The date the story’s implementation is accepted by the customer. We do this at the start of every planning game before we get
into the new stories. This helps remind the customer what has just
been accomplished, and, sometimes, lets the customer catch incomplete stories.
Description A few sentences and/or pictures explaining the requirement.
Be brief. If the description isn’t clear, rip up the card and start over.
This is the most important field, so you may want to fill it in first. See
examples in Stories.
Estimate The programmers write their best guess for the implementation
time. See discussion about the time scale in Estimation.
Considerations The programmers list the implementation risks and prerequisites in this section. This gives the customer more information
about the confidence of the estimate and helps her order dependent
Copyright c 2004 Robert Nagler
All rights reserved [email protected]
25