Scrum Board - HOW TO

Scrum Board Instructions

Sprint: A sprint is a short, fixed length of time when the team works to complete a set amount work. For the purpose of this project, a sprint is approximately 1 week, the time between your internal team meetings.

This is a sprint board

This is the board you will be looking at everyday and how we will be tracking who is doing what.

Every team meeting PM and TPM should be review adding and reviewing Tasks

Understanding a Task Status

Backlog: This is the default status for all tasks added to the board. Use this status to hold ideas for future work, tasks that you know will need to be done in the future, or tasks that pop up during the project and need to be assigned, etc.
- If you are aware of due dates for these tasks, you can add them at this point
Ready for Work: This status is for tasks that are ready to be worked on in the upcoming sprint.
- At this point, tasks should include details (filling out the rest of the card/table) including any links to data sets or pull requests, estimated size of work, description of what done looks like.
In Progress: Once a task is actively being worked on, it should be be moved to ‘In Progress’.
- Any tasks that is “In Progress” must have a teammate assigned to it. If the task needs to move from one teammate to another, they must discuss the progress made up until that point.
Ready for Review: Before a task can be complete, it should be reviewed by peers, the project TPM, PM, or EIR. This ensures that any code pushed to the repo is accurate.
Blocked: If a task is blocked for a variety of reasons, client feedback pending, you’re stuck on a technical issues, etc., change the status to “Blocked”. ****
Done: Once a task has been reviewed, and there is no further work, it can be moved to “Done”.