Join Doug Rose for an in-depth discussion in this video Updating the taskboard, part of Agile at Work: Reporting with Agile Charts and Boards.
- The task board is a team report.…It's designed to help the developers coodinate.…If you're the scrum master of the team,…then you need to help ensure…that only the developers update the board.…This starts with the sprint planning meeting.…During sprint planning,…the team will agree on the stories for the sprint.…They'll put their stories in the far left, stories column.…These stories should be in order…prioritized from top to bottom.…The team also creates tasks on yellow sticky notes.…Each note should represent one day of work.…
After the developers create the task,…the team will have a better idea…of how long it takes to complete the story.…Once the tasks are set,…the developers should be the only ones updating the board.…If project managers start moving tasks,…it'll be very difficult for the developers…to keep track of their work.…At the beginning of a new sprint,…all of the tasks should be gathered…under the to do column.…The morning of a new sprint,…your board should have all the user stories…listed in the far left.…
Bonus: Watch the bonus chapter at the end of this course where Doug answers common questions about the agile mindset, including what types of projects would be the best fit.
Lynda.com is a PMI Registered Education Provider. This course qualifies for professional development units (PDUs). To view the activity and PDU details for this course, click here.
The PMI Registered Education Provider logo is a registered mark of the Project Management Institute, Inc.
- Explain the purpose of a taskboard and how it can help keep a project on track.
- List the correct order of the swim lanes on a taskboard.
- Name the two types of burndown charts.
- Recognize the problems that occur when a team does not break down epics into stories.
- Identify the three roles in the triangle of responsibility.