How do you create a task in DevOps?
A task describes in technical terms how a user story should be implemented and does not need to be explained from a user perspective. Use this approach when a user story is set to “ready” and needs to be broken down into actionable tasks.
- 8 steps
- Total time: 25 min
- Preparation: 10 min
- Result: One or more tasks in DevOps, linked to the user story, with an estimate, owner, and category in place.
Required tools
- Azure DevOps — The tasks are created under “Related work” in the user story, together with the associated test cases.
Create the task
1.Wait until the user story is “ready”
Once the product owner has created the user story and set it to “ready”, it is the solution owner’s role to design how the story should be implemented.
2.Enter a precise title
Give the task a title that describes the technical solution, not the user need — that is already covered in the user story.
3.Link the task to the user story
Add the task under “Related work” on the user story it addresses, so that the connection is visible to the entire project team.
4.Set category
Categorize the task so that it can be properly tracked in reporting and the WBS overview.
Estimate, own, and complete
5.Estimate together with the person carrying out the work
Involve the person who will carry out the task when setting the estimate, and enter it under “Effort” on the task.
6.Set owner
Assign ownership of the task in accordance with the resource breakdown structure: tasks are owned by the consultant performing them.
7.Update remaining work continuously
Keep the remaining and completed work on the task up to date while it is in progress, so that its status reflects reality.
8.Connect checked-in code
Link the checked-in code to the task in DevOps, and unit test the work before marking it as complete.
Discussion
Ask a question or share what helped you.
