Even Scrum should have detailed Task descriptions

When you create tasks in Scrum you are doing this within a time box and you tend to add only the information you need to remember what the task is. And the entire Team was at the meeting and were involved in the discussions around the task, so why do you need more?

Once you have accepted a task you should then add as much information as possible so that anyone can pick up that task; what if your numbers come up? Will you be into work the next day?

Figure: What if your numbers come up in the lottery?

What if the Team runs a syndicate and all your numbers come up? The point is that anything can happen and you need to protect the integrity of the project, the company and the Customer.

Add as much information to the task as you think is necessary for anyone to work on the task.

If you need to add rich text and images you can do this by attaching an email to the task .

Figure: Bad example, there is not enough information for a non team member to complete this task

Figure: Julie provided a lot more information and another team should be able to pick this up.

This has been published as Do you know to ensure that relevant emails are attached to tasks in our Rules to Better Scrum using TFS .

Technorati Tags: Scrum   SSW Rules   TFS 2010   SSW   SP 2010   SharePoint