Story Points Estimation in Scrum - JUST STOP! - There is a BETTER way

Using story points, velocity and burndown charts for estimation, tracking and performance in Scrum is an outdated concept and has never been part of Scrum or the Scrum Guide. It leads to many bad habits and anti patterns and you should stop wasting yours, the teams and management’s time and drop them completely. There is a much better way and this video discusses that

Join my channel through memberships to get access to perks:

I now offer personal coaching and mentoring, head over to my website for subscription plans and pricing.

Buy Me A Coffee:

Follow me on LinkedIn:

Agile Thoughts Playlist:

#theagileleangardener #agile #scrum

[GrayBanks-yu]

Well said that man, story points are the pits! 👌

[paulgood]

Awesome mate just awesome can’t believe no one has commented yet?!!!! 👍

[steveang]

I can't believe people still cling on to story points with all the evidence and real world experience out there that prove they are a BAD option 👍

[JohnnyJames-qhve]

Exactly, you're saying what every one is frightened of saying, well

[vinventdepaul]

I think many are too scared to comment on this for fear of being flamed but bring it on - story points are trash!

[JohnMichaels-pj]

Totally awesome, story points are trash end of conversation

[MichaelKeywood]

Hello agile gardener, little bit of advice!

We use t shirt sizing to understand as a team the size of something relative to each user story / task and use cycle time to see how we’re performing during the iteration. In the retro we scrutinise whether something really was a small or medium using cycle time, and map out common reasons for wait times / bottlenecks.

What’s your take on that approach?

[mdesnica]

Perhaps SP works for frontend developers, but not for Backend developers. Our tasks can take weeks, sometimes months. It is only a waste of time that could be spent designing or programming.

[GrahamHaughton-xmqv]

Ha! Exactly!! Come on story point lovers make a comment I dare you! 👍