Iteration Planning

See

Try

Buy

< Back to patterns list

A Project Manager (or Scrum Master) has many responsibilities, so she will likely benefit most from using TargetProcess. TargetProcess simplifies almost all activities related to technical project management.

Iterations Planning

Iterations planning is not the most frequent process but one of the most important. In general, it consists of three activities:

  • Prioritize User Stories and Bugs
  • Select User Stories and Bugs that will be implemented/fixed in the next iteration
  • Assign developers and QA Engineers to User Stories and Bugs

TargetProcess provides a drag and drop interface for all these operations. An example: You are planning Iteration #1.1 in Release #1 and want to re-prioritize stories and bugs. The Prioritize screen serves exactly that purpose. You can see all User Stories and Bugs and can re-order them in a natural way simply by dragging them up and down, thus changing priorities.

Use the Plan Iterations screen to assign User Stories and Bugs to a specific iteration. You select Release Backlog to see all User Stories and Bugs in the release backlog sorted by priority. Then you can take the most important User Stories and drag and drop them into Iteration to see whether there is the capacity for more User Stories. If so, you can add more stories; otherwise you can remove some of them.

Subscribe to Tasks / Assign People

The last step in iterations planning is user assignment. In many project management systems this is the most complex step, since there is no summary information readily available. The project manager must keep in mind all existing assignments to create a good plan or constantly check the plan for resource utilization. TargetProcess provides all of this required information in one place.

assign user stories and tasks to developers

On the left side of the screen, you can see all unassigned User Stories and Bugs. On the right side, there is the project team with existing assignments. You can drag an unassigned Bug from the left and drop it on a team member on the right, thus creating an assignment. Later you may change your decision and re-assign this Bug to another team member with a single drag and drop operation. Also you can immediately see users' workloads, so making decisions about assignments becomes quite simple.

< Back to patterns list