Agile Walk Through - Free Beta

Assigning and estimating workload issues

With simple planning

Tasks and bugs can be assigned to team-members who have enough time to do them in desired time-span. Not started tasks or bugs can be estimated and missing tasks can be instantly created - that's what we understand by workload issues estimating.

  • Assignments-in-simplified-planning
  • Assignments-create-reservation-in-simplified-planning

If reservations are turned on, you can check how much of particular team-member's time is assigned in comparison to their availability.

  • In Total you can see overall number of tasks and bugs, total estimated time and total reservations time,
  • In Remaining you can see the number of tasks and bugs which are not finished yet, their aggregated remaining time and reserved time left (day reservations starting from tomorrow).

With iterative planning

When estimating requirements for the project with iterative planning, the difference is that you operate in particular backlog's scope.

Depending on your process you can do estimation and/or assignment of issues at different stages:

  • when requirements are in project backlog, before being planned,
  • when requirements are put to particular release's backlog, before being planned to iteration,
  • finally, you can estimate iteration backlog requirements, which is the least recommended because it results in defining scope size after you have chosen what should be delivered in the iteration.
  • Assignments-estimation-totals

If you use reservations you will see reserved time value only when iteration backlog is selected - and not surprisingly it will be time user is available within iteration's duration. Therefore it's strongly recommended to perform assignment primarily for iteration scopes.

Copyright 2007-2010 Agile Walkthrough