How does this work with Kanban teams? We have 5+ Kanban teams that are all doing technical (support/infrastructure) work (not product work) how would release planning work to align them?
It is unlikely that support/infra teams are required to do any releases. Are these teams delivering new features/product versions or supporting the day to day business operations?
So as you described we can have quarterly cycles of releases where we have near about 4-6 sprints in a quarter, when would release be actually happening? at the end of quarter or at the end of each sprint? There won't be quarterly releases if we are delivering after every sprint. I am little unclear, please guide.
Check out more Schedule Management videos here goo.gl/sKpxmP
I'm using the Agile lifecycle and specifically the Scrum framework.
Thanks for sharing 🙌
Thanks very helpful. We use agile methodology
Glad you liked it Menaka 😊👍
Nice video, so easy to understand. Welldone !
Glad it was helpful! :)
How does this work with Kanban teams? We have 5+ Kanban teams that are all doing technical (support/infrastructure) work (not product work) how would release planning work to align them?
It is unlikely that support/infra teams are required to do any releases. Are these teams delivering new features/product versions or supporting the day to day business operations?
So as you described we can have quarterly cycles of releases where we have near about 4-6 sprints in a quarter, when would release be actually happening? at the end of quarter or at the end of each sprint? There won't be quarterly releases if we are delivering after every sprint. I am little unclear, please guide.
Release happens as per the business requirements. There can be a release after every sprint or after 4 sprints
What is different between release planning and sprint planning sir
Would definitely create a video on this 👍
But to answer your question, a release can involve more than one sprints.
can you provide your contact details, very informative video