User Story Tasks
You can break a user story into multiple tasks that essentially chalk out the road map to the completion of the user story. It is recommended that each must be an action item that takes no more than eight hours. Tasks are usually defined by the people doing the work (developers, QA, etc). They contain a highly detailed explanation of the job to be completed and are not meant for the end-users.
Purpose of User Story Tasks
The main purpose of user story tasks is to enable the development team better understand what needs to be done.
- Tasks are assigned to someone on the team for implementation.
- Must include enough detail to be effective.
- Ensure that you have the following details when you create the tasks:
- Who are you writing for (experience/capability)?
- What are your timelines?
- Do you have time for trial and error?
- You can use tasks to track the status, where the task is in Not Started, In Progress, Completed, Waiting on someone else, or Deferred status.
- Which environment the task should be completed in (Dev, QA, Prod).
- Credentials for the org.
- Estimated LOE (Level of Effort) and the remaining LOE.
Structure of a User Story Task
Create a User Story Task
To create a User Story Task for a User Story:
- Go to the User Story.
- Scroll down to Estimation > User Story Task > New.
- Enter the details.
- Click Save.