I think that having all the team participating to the estimation process is the largest benefit of the planning poker by discussing stories one by one and giving having each member point of view about the work to be done. Doing so will certainly minimize risks a posterior along the project.
I reckon the biggest value that PP brings to the table is for the team to learn how to properly estimate, both on their own and around each other. Great video!
The biggest benefit is Mitigating risk: By involving the entire team in the estimation process, planning poker helps identify and address potential risks early on. Team members may uncover different aspects of a task that could impact its complexity or duration.
In my view the biggest benefit of using planning poker for estimating story points is that it allows all members of the team to have their say in how a task or story is estimated. This helps ensure that the estimation process is unbiased and accurate. Additionally, I believe that this technique typically results in more accurate estimates as team members understand the underlying complexities of each story and are better able to agree on a realistic value rather than a team leader providing a a generalized estimate on behalf of the team based on assumptions as rightly pointed out in the video.
In my opinion the biggest benefit of Planning Poker is that it enables collaboration and transparency within the Scrum Team as all the team members actively participate in this relative estimation exercise based on their shared understanding of the user story to ultimately reach a consensus on the amount of effort in story points that will go into delivering that user story.
@@AxisAgileApps should the QA/QC/BA also give their story point or just Developers only? The question is: why the QC/QA/BA can give estimation, they dont do the Developer' job, then how do they know. ? Thanks
Hi@@jaypham3371, great question. The Story Point estimation should include anyone who is involved in both development and testing. I.e. both developers and Quality Assurance (QA). This is because the Story Point value represents the effort for the work to be completely done (i.e. meets the teams Definition of Done), and this should include testing as it's only after this is done can we release our product. Also,don't forget the Story Point value is a relative estimate, so when comparing one Product Backlog item to another we are comparing the combined effort of both development and testing. With regards to Business Analysts (BA), they typically do not give input into the Story Points unless they are involved in either the development and testing. If they are only involved in the refinement of the Product Backlog then their involvement at the Planning Poker session is similar to the Product Owner, and providing clarity around the requirements. Hope that makes sense, but if not please don't hesitate to reply to this comment with more questions :) Thanks! Richard
Awesome video! That was my next question... how to incorporate planning poker points in Jira. So there you ended the video with information on Velocity. Thank you 🙂
I think the greatest benefit of using the poker cards for point estimation is that it gets full team buy-in to the estimation value based on greater understanding and creates individual responsibility to achieve the decided result.
Hi @davidbird1606, you are one of our lucky winners! Please contact me at richard@axisagile.com so that we can send you a packet of Planning Poker cards :)
Great video. I have 2 questions: - How can everyone in delivery team provide an estimate when they are not expert in every area? For example how can a front-end developer provide story points for a work that includes back-end points as well? Is their estimation valid? - What would be the role of designers in sprint planning session? I assume they are mostly a part of backlog refinement (designing for items) process, but should they be included in sprint plannings too?
In my view, the use of poker cards for agile story point estimation can help standardise the estimation process, improve accuracy, encourage collaboration, and increase the speed of the estimation process.
Hi Clement, congratulations! You are one of our lucky winners for the month of May. If you could get in touch with me by sending an email to richard@axisagile.com we'll arrange for the Planning Poker cards and case to be sent out to you. Thanks! :)
Hi @clementodjo3690, just a reminder that you are one of our lucky winners. Please email me (richard@axisagile.com) or connect with me over LinkedIn (www.linkedin.com/in/richardkaupins/) Thanks!
Hi Sayan, good question. Yes, ideally testers should be involved in the Planning Poker session. Ideally we want those who are involved in the building and testing. You don't necessary need to entire team, just representatives from building and testing, so for example at least one programmer and one tester.
Hey BovineOx, check out my video on Sprint Planning using sub-tasks and time to see how it's done :) Here's the link: th-cam.com/video/94sqZadKOFI/w-d-xo.html
Good question! The process helps with removing bias and anchoring when it comes to estimation. By allowing each person to share how much effort they believe the work is without being influenced by others can lead to better discussions about what's realistically involved. Hope that makes sense and thanks for watching!
Thanks Jodakan, it's certainly not a mandatory approach. If you are working with an Agile team it's important to voice that with your Scrum Master so they know it may not be something the team likes doing and can address it.
Your are so well in explaining things in very short time, but with lots of information !!!! This is amazing... Thank you !!
Thanks Sumith!! Our pleasure :)
I think that having all the team participating to the estimation process is the largest benefit of the planning poker by discussing stories one by one and giving having each member point of view about the work to be done. Doing so will certainly minimize risks a posterior along the project.
Thanks Houcem! Great point, you are in the draw to win a packet of Planning Poker cards :)
Great video, I will be taking part in my first poker planning in a couple of days and this provided the insight on what I should except. Thank you!
Our pleasure John! Glad it helped :)
I reckon the biggest value that PP brings to the table is for the team to learn how to properly estimate, both on their own and around each other.
Great video!
Thanks Jaime, great point! - You are in the draw to win a packet of AxisAgile Planning Poker Cards! :)
The biggest benefit is Mitigating risk: By involving the entire team in the estimation process, planning poker helps identify and address potential risks early on. Team members may uncover different aspects of a task that could impact its complexity or duration.
Nice one Khalid! Spot on
In my view the biggest benefit of using planning poker for estimating story points is that it allows all members of the team to have their say in how a task or story is estimated. This helps ensure that the estimation process is unbiased and accurate. Additionally, I believe that this technique typically results in more accurate estimates as team members understand the underlying complexities of each story and are better able to agree on a realistic value rather than a team leader providing a a generalized estimate on behalf of the team based on assumptions as rightly pointed out in the video.
Completely agree, thanks Swati! You are in the draw to win a packet of Planning Poker cards :)
In my opinion the biggest benefit of Planning Poker is that it enables collaboration and transparency within the Scrum Team as all the team members actively participate in this relative estimation exercise based on their shared understanding of the user story to ultimately reach a consensus on the amount of effort in story points that will go into delivering that user story.
Well said Tanmoy! You are in the draw to win a packet of Planning Poker cards :)
@@AxisAgileApps thanks Richard :)
@@AxisAgileApps should the QA/QC/BA also give their story point or just Developers only? The question is: why the QC/QA/BA can give estimation, they dont do the Developer' job, then how do they know. ? Thanks
Hi@@jaypham3371, great question. The Story Point estimation should include anyone who is involved in both development and testing. I.e. both developers and Quality Assurance (QA). This is because the Story Point value represents the effort for the work to be completely done (i.e. meets the teams Definition of Done), and this should include testing as it's only after this is done can we release our product. Also,don't forget the Story Point value is a relative estimate, so when comparing one Product Backlog item to another we are comparing the combined effort of both development and testing.
With regards to Business Analysts (BA), they typically do not give input into the Story Points unless they are involved in either the development and testing. If they are only involved in the refinement of the Product Backlog then their involvement at the Planning Poker session is similar to the Product Owner, and providing clarity around the requirements.
Hope that makes sense, but if not please don't hesitate to reply to this comment with more questions :)
Thanks!
Richard
Awesome video! That was my next question... how to incorporate planning poker points in Jira. So there you ended the video with information on Velocity. Thank you 🙂
Our pleasure Amudha, glad it was helpful! :)
I think the greatest benefit of using the poker cards for point estimation is that it gets full team buy-in to the estimation value based on greater understanding and creates individual responsibility to achieve the decided result.
Love it, thanks David! You are in the draw to win some Planning Poker cards :)
Hi @davidbird1606, you are one of our lucky winners! Please contact me at richard@axisagile.com so that we can send you a packet of Planning Poker cards :)
Great video. I have 2 questions:
- How can everyone in delivery team provide an estimate when they are not expert in every area? For example how can a front-end developer provide story points for a work that includes back-end points as well? Is their estimation valid?
- What would be the role of designers in sprint planning session? I assume they are mostly a part of backlog refinement (designing for items) process, but should they be included in sprint plannings too?
In my view, the use of poker cards for agile story point estimation can help standardise the estimation process, improve accuracy, encourage collaboration, and increase the speed of the estimation process.
Good points Clement! You are in the draw to win a packet of Planning Poker cards :)
Hi Clement, congratulations! You are one of our lucky winners for the month of May. If you could get in touch with me by sending an email to richard@axisagile.com we'll arrange for the Planning Poker cards and case to be sent out to you. Thanks! :)
Hi @clementodjo3690, just a reminder that you are one of our lucky winners. Please email me (richard@axisagile.com) or connect with me over LinkedIn (www.linkedin.com/in/richardkaupins/)
Thanks!
Biggest benefit is individual view on estimation can be factored rather than single person's view
Thanks @Varaprasad21! You are in the draw to win a packet of Planning Poker cards :)
I have one question, in planning poker does everyone from the scrum team joins? I mean the testers too join?
Hi Sayan, good question. Yes, ideally testers should be involved in the Planning Poker session. Ideally we want those who are involved in the building and testing. You don't necessary need to entire team, just representatives from building and testing, so for example at least one programmer and one tester.
I've never known a team switch to hours during the sprint, interesting 🤔
Hey BovineOx, check out my video on Sprint Planning using sub-tasks and time to see how it's done :) Here's the link: th-cam.com/video/94sqZadKOFI/w-d-xo.html
Why gamify and formalise such a simple activity of discussing and agreeing on something ?
Good question! The process helps with removing bias and anchoring when it comes to estimation. By allowing each person to share how much effort they believe the work is without being influenced by others can lead to better discussions about what's realistically involved. Hope that makes sense and thanks for watching!
This makes sense i just would hate to have this implemented at my workplace
Thanks Jodakan, it's certainly not a mandatory approach. If you are working with an Agile team it's important to voice that with your Scrum Master so they know it may not be something the team likes doing and can address it.
Planning Poker increases the accuracy in estimation
Thanks Keystrata Resources! You are in the draw to win a packet of Planning Poker cards :)