15 January 2019
Work estimation by one Scrum team could be challenging. Typical issues that Scrum teams face are:
-What scale or measuring technique should we use? Story points? Dog breeds? T-shirt sizes? Days/hours? Both?
-Do we estimate size or complexity? Or both?
-How to make sure that team members with different core skill set and domain expertise meaningfully contribute to estimation by the rest of the team?
-When to do Velocity-driven planning and when to do Capacity-driven planning? Or are they just two stages in the same process?
How to use Historical Velocity to plan your next sprint vs. do longer-term strategic planning?