"Eternity"
Next: FixMyProcess
Previous: Email
"The reason the product is being developed."
"A short description of the work being done, and the situation that triggered the analysis effort."
<p>Eternity supports fixed time box iterations. </p>
"Development of civil society processes"
"Establish appropriate software clubs"
"An analysis of the stories that might be supported by the new product."
The product supports these stories:
Story #104
"Create new iteration"
Story #105
"Close current iteration"
Story #106
"Continue as new iteration"
Story #107
"Select item to be addressed during an iteration"
Story #178
"Read list of outstanding work of current iteration"
Story #33
"Review past iterations"
"Determine, with the appropriate stakeholders, which part of the story should be supported by some sort of product and what part should be done entirely by the user."
The product shall satisfy these requirements:
Functional Requirement #11
"The system shall present iteration history"
"Review past iterations"
Functional Requirement #29
"The system shall allow an end date to be set independently of closing the iteration"
"Review iterative working"
Functional Requirement #9
"The system shall support opening and closing iterations"
"Review iterative working"
Functional Requirement #14
"The system shall automatically identify the position of attributes in Trac reports based on the heading row in the first line "
"Review iterative working"
Functional Requirement #8
"The system shall use the __color__ field as a substitute for cost/value ratio if they are not present"
"Review iterative working"
Functional Requirement #17
"The system shall attempt to read cost from ticket description if cost is not present in the TSV report"
"Review iterative working"
Functional Requirement #1
"The system shall present aggregated backlogs"
"Review iterative working"
Functional Requirement #45
"The system shall present cost and value estimates with no more than two decimal places"
"Review iterative working"
Functional Requirement #46
"The system shall present lists of tickets in descending priority order"
"Review iterative working"
Functional Requirement #10
"The system shall record items marked as completed as achievements of active iteration"
"Accept completion of item in iteration plan"
Functional Requirement #35
"The system shall support marking items in aggregated backlog as completed and acceptable"
"Accept completion of item in iteration plan"
Functional Requirement #65
"The system shall release all outstanding tickets from association with the closed iteration"
"Close current iteration"
Functional Requirement #108
"The system shall present lists work items in descending priority order"
"Read list of outstanding work of current iteration"
This product has been included in the following collections:
| Collection |
|---|
| Appropriate Software |