techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

4.8K
active users

#StoryPoints

0 posts0 participants0 posts today
Replied in thread

@redezem #PlanningPoker as well as #StoryPoints is only a tool to triage new backlog items. It can help the product owner to quickly find out which stories must be clarified. PO has 60 minutes max to present a dozen brand new stories and leaves that meeting with three stacks: "Well understood", "To be rewritten" and "Potential trainwreck". That is all and almost every application beyond that specific purpose is #agile cargo cult, especially #Velocity as KPI for team performance.

Time is paramount and precious resource, but no system is perfect for balancing development team productivity. As an example, suppose you have: 27 tickets totaling 56 points, team of six developers (two junior, three senior, one lead) has 47 points available. How to remove nine days of work?

I like this example using time-based estimates:
▦ story points as days
▦ collaborative estimation
▦ capacity management
▦ prioritization

Article: hackernoon.com/a-developers-pe

The question "How long will that take?" is a simple one, but providing an answer has always been a challenge.

The Easy Estimation With Story Points technique has been a game-changer for many teams, helping them provide better predictability while also reducing the time spent estimating.

In this full replay of our Scrum Professionals Meetup, we take a deep dive into this technique and explore how it works: youtube.com/watch?v=Dw8y8XeH3j