Platform Engineering Team Wiki

Story Point, Target Milestone, & ETA

What's Story Point?

• It is the effort estimation in Agile way.
• 1 point means approximately 2 working days.
• By using Fibonacci Number, the story point will be a number in "1, 2, 3, 5, 8, 13" (Actually 13 is not recommended unless you really have to)

How to apply Story Point?

• Put in whiteboard, format: [p=2]. When you first got the ticket & after a quick estimation.
• The efforts shall include "unit test", "getting review+", "landed".
• When closing a bug, you may make correction to the p to reflect actual efforts.
• p means "the effort you spent", NOT "how long the ticket is closed". For example, you're assigned a bug on Monday, but you wait and start working on it Thursday and Friday then done, p should put as 1, not 3.

Target Milestone

• There is a filed in bugzilla called target milestone. Every milstone is in 2 weeks basis. When doing the sprint planning, this filed has to be assigned an milestone to indicate the bug is planned to be done in the given sprint.

ETA

• Sometimes for the urgent blockers or overdue bugs, the ETA will be required so that the stakeholders will know when the bug is expected to be fixed.

Sprint Tracking

2.0 Sprint 1 (4/28 ~ 5/9)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

2.0 Sprint 2 (5/12 ~ 5/23)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

2.0 Sprint 3 (5/26 ~ 6/6)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

2.0 Sprint 4 (6/9 ~ 6/20)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

2.0 Sprint 5 (6/23 ~ 7/4)

2 Total; 0 Open (0%); 2 Resolved (100%); 0 Verified (0%);

2.0 Sprint 6 (7/7 ~ 7/18)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);