Work in a Sprint
- Gildas Lanilis Gmail
PTLs: Groom the top of your Product Backlog for next Sprint.
Each Team member creates or assigns to themselves a Story, a Task or a Sub-Task
Each Team member provides daily update on his tasks-stories
Overview
The Scrum process imposes a Daily 15 minutes Standup.
During the daily standup, the Scrum Master insures that:
Every day the Team member selects to a Sprint Backlog Item (Story, Sub-Task).
Every day the Team member moves his/her Sprint Backlog Item from the left to the right. If a Sprint Backlog Item is not moving that means there is an impediment that the Scrum Master need to address.
If a Sprint Backlog Item is not moving it may be due to High estimates (Despite the recommendation of keeping story estimate smaller than 21)
See the whole picture
Below is the heart beat of Scrum: an Active Sprint.
In 3 simple columns labelled "To Do", "In Progress", and "Done" one team member can see what is really happening. Each red rectangle has a purpose.
Each Team members has to move (drag & drop) every day the JIRA Issue from left to right.
Break things down
At any point of time, a Story can be broken down into multiple Sub-Tasks and added within a Sprint (even if the Sprint is already started).
Note that a Task and Sub-Task don't have an Estimate field, only Story has an Estimate field.
Relate things
You may also link an existing Task to a Story, use the Issue Link and use link type relates to.
Move things
You are authorized to add in the active Sprint a Task that was not initially planned.
To do so, from the Product Backlog view drag and drop the JIRA Issue in the active Sprint. You will be asked to confirm the Scope changes.
By doing so, you provide clear visibility to your team mate on your latest achievements. They are certainly very interested knowing this is "Done".