PST Piyush Rahate shares some insights about story points and estimations based on his experiences in this blog post: https://lnkd.in/eY_mwfDh #agile
Thanks you for the inspiring thoughts. What I found most helpful in using story points was the discussion around it that you also mentioned. The moment when every team member places their estimates on the table, extremely helpful discussion can get started when looking into the reasons the people have in mind for making different - technical - assessments. Especially when you are using a new technology or if you trying out new combinations of technology, having everyone involved providing estimates will bring up the swarm intelligence. The numbers themselves weren't what matters in the nd.
Story points are also very useful for quickly understanding the complexity of a task during sprint planning, without having to systematically reanalyze the implied work.
Very informative
Very helpful! Thank you
Insightful points
Certified Scrum Master CSM® | Manager Scrum | Agile Practitioner | MS (Project Management)
1moThat's really helpful and inspiring. Quick question: can we use something other than story points for task estimations? For example, we estimate tasks based on the required hours of work, which reflects the task's complexity. This approach helps us understand how many tasks we can handle each sprint and has also motivated our team to complete a minimum number of tasks with story points. What are your thoughts on this?