Planning Poker | Story Point Estimation in Agile | Agile Estimation Techniques

[@Agilemania]

join, Agile30, our largest agile scrum community around the world, join us for free training, FAQ and quick coaching: agilemania.com/agile-and-scrum-community/

[@diedrenorris8678]

Very helpful! Thank you

[@Agilemania]

You're welcome!

[@user-ys2lv9dt2m]

Superb. Video was very useful.

[@fari3511]

Where’s Jared?

[@angelabaio8553]

Very helpful, thanks!

[@Agilemania]

Thank you for your feedback.

[@nikolaoslitos4828]

Hello and thank you for this great video. I would like to ask you what does the numbering means? for example the meaning is hours per day? Thank you again.

[@Agilemania]

Hi, In planning poker, the numbers used for estimation don't represent hours per day. Instead, they represent relative effort or complexity. Team members assign numbers to user stories based on how they perceive the effort required to complete them, allowing for more accurate forecasting and planning in Agile development. These numbers are typically Fibonacci sequence-based (e.g., 1, 2, 3, 5, 8, 13, etc.) to reflect the uncertainty and non-linearity of effort involved in software development tasks.