How do iteration plans relate to process iterations?
Iteration plans appear to be the concrete entities for defining work items and the time lines for completing those work items. However, it's not clear to me how the iteration plans relate to the various levels in the hierarchy of process iterations, or how to create an iteration plan at a particular level in the hierarchy.
- What is the relationship between iteration plans and process iterations? - How do I create an iteration plan at different levels in the process iteration hierarchy, and why would I want to create different iteration plans at different levels of the process iteration hierarchy? - What are the best practices and example scenarios for defining iteration plans? |
2 answers
Hi Russell,
it's not clear to me how the iteration plans relate to the various The the work item editor and well as the planning component currently support the the first two hierarchy levels of iterations. The first level, the project phase, contains multiple milestones and is usually used to refer to a complete release cycle. You might want to try using a project phase iteration plan to track RFS items etc. The second level, called milestones, is used to plan the work done for milestones. usually, you will plan defects or tasks to be resolved in a certain milestone. We do not support creating plans for the third level, milestone phases. This hierarchy level is used to split a milestone in phases, eg development, stabilization, endgame etc. It allows you to define different process specifications for the different phases. You can create a Iteration Plan for a project phase or milestone by opening the context menu on the "Plans" folder and select "New" -> "Iteration plan". Simply select the appropriate project phase or milestone in the "Iteration" drop down. - What is the relationship between iteration plans and process Process defines the iterations in the project area editor, work items are planned for one of those iterations. You can create a plan for an iteration; it basically describes a work item query for a given iteration and team area and allows you to manage these planned work items in the iteration plan editor. The attached text pages allow you to write down free-form planning information.
see above
Our teams track the work assigned for a milestone using a plan. The plans are usually created by the team lead before the iteration begins or shortly afterwards. The iteration plans contain an overview page describing themes for the milestone etc. Some plans also have attached pages for additional, important milestone information (build notes, test plans...) Some teams also track RFS items, themes and work that needs to be done for the 0.6 release but are not yet planned for a milestone in a 0.6 (project phase) plan. You might want to have a look at https://jazz.net/jazz/web/projects/Jazz%20Project#action=jazz.viewPage&id=com.ibm.team.apt.web.PlanPerspective to see examples on how we use the plans. Hope this helps, MikeS |
Iteration plans appear to be the concrete entities for defining work items and the time lines for completing those work items. However, it's not clear to me how the iteration plans relate to the various levels in the hierarchy of process iterations, or how to create an iteration plan at a particular level in the hierarchy. It is explained pretty well in the 'Getting Started with Jazz Project Areas and Process' (https://jazz.net/learn/LearnItem.jsp?href=content/docs/process/index.html#Overview_of_the_Team_Process_User) tech note. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.