This way you can clearly identify potential improvement areas in the sprint planning process. I recommend that your sticky-notes include the task ID number (that is automatically generated by the software tool), the initials of whoever has taken on the task, a few words describing the task, and the current time remaining (see Figure 1).įigure 1 – Example content for a sticky-noteĪny unplanned work should also be captured on the task board, though I recommend using a different-colored sticky-note. The trick is to write just enough on the note to make it identifiable. If you are also using a software tool to help manage your Scrum artifacts, there is a fine line between wasting time replicating details (that have already been captured digitally), on the one hand, and not jotting enough detail on the sticky-notes, on the other hand. Try to make each constituent task of a PBI a “vertical,” independently testable slice otherwise, the Ready to Verify column won’t be as meaningful on a task-by-task basis. Basically, each row will be dedicated to a single PBI and its associated tasks.Įach sticky-note represents a specific task item. Don’t use your tape for the rows (just the columns) because the rows will obviously vary per sprint (and retaping every couple of weeks will get very annoying). The rows represent the sprint backlog items, including the PBIs (and associated tasks), that will be focused on during the sprint. Not Started | In Progress | Ready to Verify | Done Rows of Sticky-Notes
0 Comments
Leave a Reply. |