Situation 1

·         You want to track Detail Estimate, ToDo and Effort at backlog items level

·         You are not breaking down your backlog items into tasks and tests      OR   

·         You choose to break down into tasks but are not estimating or tracking at task/test level. Tasks/tests serve as reminders of what needs to get done but you keep your estimating at the backlog item level.

Recommendation

Track at the backlog item level.

All data is entered and editable at backlog item level only.  Team members can focus on backlog items to see what work remains.

 

 

Situation 2

·         You will be breaking your backlog items into tasks/tests and entering more granular estimates (usually in units of time) for those tasks and tests.

Recommendation

Track at the task/test level. 

All data is entered and editable at task/test level only.  The rollups at backlog item level will be displayed but not editable.

Team members can see all their work in one place e.g. the Taskboard will capture all work that needs to be completed.  Burndown will accurately reflect all remaining work.

 

 

Situation 3

·         You have some backlog items that you plan to break down into tasks and you have some backlog items that you prefer not to break into tasks.

Recommendation

Create a placeholder task for those backlog items that you did not plan on breaking down.   Track at task/test level. It is not recommended to track at both levels.

Advantages with this approach:

·         all work will be in one repository…all tasks in one spot (i.e.  taskboard) from day one

·         burndown will correctly depict amount of work since it reflects remaining to-do for all tasks.

·         less confusing for the team.  They will not need to have a different process for updating time for backlog items vs tasks.

 

Situation 4

·         You have multiple projects each tracking at different levels e.g. Project A will have all backlog items broken into task and tests.  Project B will not have any backlog items that are broken into tasks and tests.  Members for each project have different processes for entering time.  Members of Proj A not working on Proj B.

Recommendation

Track at both levels so each project team can use the process appropriate to them.  In this example, team members in Project A should have processes to only update task level data.  Team members in Project B will have a process to only update at backlog item level.

Note:  data at both levels will be open for edit.  Team will need to be diligent in the process that they have chosen for their project.