Skip to content

Latest commit

 

History

History
60 lines (42 loc) · 2.2 KB

backlog-refinement.md

File metadata and controls

60 lines (42 loc) · 2.2 KB
Raw

Backlog Refinement / Review

Table of Contents

Agenda

  • Review what tasks remain
  • Review sprint statistics
    • BurnUp Chart
    • Velocity Chart
    • Control Chart
    • To understand scope change, velocity shift and reasons why not starting some tasks
  • Introduce, discuss and estimate the tasks
  • Note uncertain things and assign someone responsible to clarify the requirements
  • AGREE on the sprint goal(s) - no more than three
  • Decide what should be done and what should not be done

Story points

We should NOT start any development if there are no estimation in the tasks

Scale: Fibonacci number is a good tool to follow

Assign the number of story points to a task by:

  1. the amount of understanding
  2. the effort to implement
  3. the testing effort on developers

Meaning of each number

  • 1 (very easy, can be done in less than 1 hour)
  • 2 (easy, but need time to implement and verify, maybe need to spend 1 to several hours)
  • 3 (medium, expected to spend around 1 day to finish it)
  • 5 (complicated, expected days)

Break down the task if larger than 5

  • 8 (very complicated, expected a week)
  • 13 (it will be super huge that we cannot imagine, even cant estimate the timeline)
  • spike

It is possible to say the task is a spike, which means we do not know how to implement it

Best Practices

  • Before the sprint starts:
    • Only Bugs / Tasks tickets have story points
    • Do not put tasks that exceeds the agreed capacity in any cases

Reference