Thank you for checking and commenting on our video, we do run an agile coaching program to assist scrum masters taking the next role, you can find more information on our agile coaching program here: www.izenbridge.com/certified-agile-coach-icp-acc/virtual/
DoR is not standard as per Scrum, and it is more used in backlog refinement meeting to ensure we are ready with coming requirements, In sprint planning we take the ready stories, if some stories are not ready? can we still take them in Sprint Planning, the answer is YES, it will have more risks, we may not be able to predict it well, but as a team we may want to work and see,
Your sessions are too good and informative. I am a student of Project Management, new in this field of Scrum and Agile. Watch your videos regularly' need help in a few areas' 1. Kindly reply to the scenario Grish has explained. Me too facing a bit problem in having pack-to-pack sessions. Teams get annoyed that how can they work if they have too many sessions. 2. Please have a session on the smart way of backlog refinement'
Sprint Planning meeting is done when any Sprint starts. PI planning is done once in 8 to 12 weeks for four sprints together. Sprint Planning is done within a single scrum team whereas PI Planning is done across all the teams
Hi Sir, Very informative video... I have some queries regarding the event which we plan in our project.. 1) We have every alternate day PB refinement sessions where PO and team discuss about upcoming PB items which PO Has added in Sprint backlog.. Sprint backlog is ready for atlast next 2 sprints... On the last week of current sprint when dev team is bit free, team closely looks into stories.. Further breaks it down and provide estimates in terms of effort as well as story points... We also prepare team capacity sheet based on holiday and leave plans.. At the time of sprint planning meeting which is one hour TEAMs call, we represent efforts as well as capacity so that PO can add or remove any item from SB... Is it correct way to do it.. Please suggest.. 2) As scrum emphasize on story point estimation, my team and even PO is more inclined towards hrs estimates as they want commitment if all will get Delievered or not... Is that approach OK..?
If you are not facing any issue and things are working good that this is good, Scrum officially does not mandates doing story point estimations many find it doing useful. The only possible challenge I can see here is you may not be able to do some long term forecast , say what can get done in next 3 months, since you do not have velocity and story size. But if that is not needed or you have some alternative way of doing it, I do not see any issue.
You are GOD send. Thank you so much, Your way of presenting is clearing things in one go.Tons of thank you
Thank you for your kind words
Thank you very support.
Happy to know you liked this video, we have many such. Thank you for watching.
Hi Saket, Thanks for the video which explains clear picture of Sprint Planning.
Happy to Kiran you liked the video. Keep exploring iZenBridge UA-cam Channel.
Great detail and practical examples
Glad you liked it
very good thanks for posting
Thank you for checking and commenting on our video, we do run an agile coaching program to assist scrum masters taking the next role, you can find more information on our agile coaching program here:
www.izenbridge.com/certified-agile-coach-icp-acc/virtual/
Thankyou so much sir..GBU
Thankyou sir for the very valuable information..
So nice of you
In the inputs, shouldn't we add Definition of Ready (DoR) also to ensure that the story we are taking in sprint satisifes the DoR criteria? Le
DoR is not standard as per Scrum, and it is more used in backlog refinement meeting to ensure we are ready with coming requirements, In sprint planning we take the ready stories, if some stories are not ready? can we still take them in Sprint Planning, the answer is YES, it will have more risks, we may not be able to predict it well, but as a team we may want to work and see,
Your sessions are too good and informative. I am a student of Project Management, new in this field of Scrum and Agile. Watch your videos regularly' need help in a few areas'
1. Kindly reply to the scenario Grish has explained. Me too facing a bit problem in having pack-to-pack sessions. Teams get annoyed that how can they work if they have too many sessions.
2. Please have a session on the smart way of backlog refinement'
Very very helpful tips for a beginner like myself
Glad, you liked it. To know more about Saket training courses, please visit -www.izenbridge.com/landing/youtube/Saket-Bansal/
Good content 😊
Thanks 😁
Very very useful
Thanks a lot
Please explain the relation and difference between the PI planning and Sprint Planning
Sprint Planning meeting is done when any Sprint starts.
PI planning is done once in 8 to 12 weeks for four sprints together. Sprint Planning is done within a single scrum team whereas PI Planning is done across all the teams
@@izenbridge Thanks alot... Best Explanations always👍
Hi Sir, Very informative video... I have some queries regarding the event which we plan in our project..
1) We have every alternate day PB refinement sessions where PO and team discuss about upcoming PB items which PO Has added in Sprint backlog.. Sprint backlog is ready for atlast next 2 sprints... On the last week of current sprint when dev team is bit free, team closely looks into stories.. Further breaks it down and provide estimates in terms of effort as well as story points... We also prepare team capacity sheet based on holiday and leave plans.. At the time of sprint planning meeting which is one hour TEAMs call, we represent efforts as well as capacity so that PO can add or remove any item from SB... Is it correct way to do it.. Please suggest..
2) As scrum emphasize on story point estimation, my team and even PO is more inclined towards hrs estimates as they want commitment if all will get Delievered or not... Is that approach OK..?
If you are not facing any issue and things are working good that this is good, Scrum officially does not mandates doing story point estimations many find it doing useful.
The only possible challenge I can see here is you may not be able to do some long term forecast , say what can get done in next 3 months, since you do not have velocity and story size. But if that is not needed or you have some alternative way of doing it, I do not see any issue.
How to maintain transperancy in team
By bringing structures like Kanban Board and Daily Scrum.
This video looks so cool! :)