A simple checklist for planning a Sprint Backlog.

  1. Quick refresh of change suggestions from previous Retro
  2. Set a Sprint Goal
    1. The Sprint Goal is an objective that will be met within the Sprint through the implementation of the Product Backlog, and it provides guidance to the Development Team on why it is building the Increment – The Scrum Guide
    2. Goals should be SMART eg Specific, Measurable, Achievable, Realistic and Time-bound.
  3. Capacity Plan – Log team availability in the coming sprint (including feature owners)
  4. Agree Velocity – Based on previous Sprints’ velocity, adjusted for capacity changes
  5. Re-write and re-estimate any not DONE Stories from the previous Sprint (if they are still a PO priority)
  6. Finish writing any incomplete Stories from Grooming
    1. Split Stories where possible – smaller is better
    2. Write Stories according to INVEST http://codesqueeze.com/how-to-invest-in-your-user-stories/
    3. Write tasks on postits
    4. Estimate using planning poker – use fingers for 1, 2, 3, 5, 8, 13, 20 …
  7. Pull prioritised and Estimated Stories into Sprint Backlog  until the Velocity is reached
  8. Hold a fist of 5 vote to check Team’s confidence in getting every Story in the Sprint Plan DONE http://agileanswerman.com/5-reasons-a-scrum-master-should-use-fist-of-five-voting/
  9. Team Commit to getting all of the Stories DONE
  10. Team put printed Stories from Rally and Tasks on their Board
  11. Team hold a mini-huddle to agree the tasks that each Team member will start on first (probably after lunch). Move tasks into In Progress with Avatars.
  12. Update the started Stories in Rally!