self memo

Guideline for Sprint Planning @Philippines

I wrote about retrospective in the previous entry.

I will write an article about Sprint Planning MTG this time.
Please see below for the details.
---

Sprint Planning

Overview

  • Most HARD ceremony(event).
  • Answer two topics
    • What PBIs can be done in this Sprint?
    • How will be the chosen PBIs get done?

What PBIs can be done this Sprint?

  • Pick up PBIs from PBL from the top of the list.
    • PBL should be ordered by priority, which PO decide.
    • Keep picking up PBI as long as your team can make a commitment.
  • Commitment is important.
    • If you break your promise, …

How will be the chosen PBIs get done?

  • Make a Sprint Backlog.
    • Sprint Backlog consists of chosen PBIs and Tasks.
    • Break down PBI into small tasks.
    • Task has Summary and Estimated time.
    • Estimated time for a task should be less than 6 hours

How to

  1. Determine development capacity in this sprint.
  2. Proposal of sprint goal from PO.
    • Ex.
      • Finish ten PBIs.
      • Release push notification.
  3. Pick up a PBI from PBL from the top of the list.

    • It's the highest priority of the PBL.
  4. PO explains PBI and developers ask questions to make an estimation for it.
  5. Break down PBI into small tasks.

  6. Estimate tasks using hour(s).
  7. Repeat the process of estimation until developers feel that they can't commit to finish PBIs anymore or the capacity gets full.
  8. Review sprint goal.
  9. Make a commitment.

---
Next time I plan to write about Definition of Done and Acceptance Criteria.
[PR]
by aratafuji | 2015-11-05 15:17 | English