9.4.2. AssignmentWhile deciding the stories and tasks which should be assigned to an iteration, additional details of the assignment may be considered. Generally a team member will be set as the owner of the the story or task and be responsible for its completion. While planning the iteration, ownership assignment can be handled at the same time. Sub-tasks can be assigned to individual users. To assist in the accuracy of the iteration plan, time estimates should also be made on the stories that are assigned to the iteration. Providing the time estimate allows the total time planned for an iteration to be measured for purposes of velocity. The estimated time for individual team members can also be viewed so that individuals are not overloaded during an iteration. Of course, stories themselves should be marked as part of an iteration. Doing so allows the iteration progress to be tracked over time and reports to be generated. Keep in mind that when stories are assigned to an iteration, the sub-tasks of such stories are also considered assigned to the iteration. Remember that iterations are only available for assignment if they have not been marked "Finished". |
1. AgileTrack Overview
2. Installation 3. Server 4. User Interface 5. System Configuration 6. User Management 7. Issues 8. Projects 9. Iterations
9.1. Creating/Modifying Iterations
10. Releases9.2. Date Range 9.3. Release Assignment 9.4. Planning 9.5. Starting/Finishing 9.6. Statistics 9.7. Issue Lists 9.8. Comments 9.9. Attachments 9.10. History 11. Queries 12. Reports 13. Integration APIs 14. Troubleshooting |
AgileTrack
Put your development on the AgileTrack
Put your development on the AgileTrack