Stop Spilling Over - Ensure Shipable product in Every Sprint
Most of the IT projects which are executed in agile methodology, are always having the problem of "User stories getting spilled over to next sprint", in other words "Commitment is not met" in the sprint. Main reason for this is identified as "Activities which has dependent tasks are backloaded to the latter part of the sprint, e.g. QA work is always backloaded in the sprint due to delay of Grooming, Code development, Developer testing, etc.
This can be managed by having agreed ceremonies, gates in the sprint execution. Ceremonies ensure activities are completed during agreed dates and gates ensure exit and entry criteria are met.
Outline/Structure of the Talk
Introduction
Problem Statement
Example
Solution
Q&A
Learning Outcome
How to Manage the Spill-overs
How to ensure Sprint Deliverables
Target Audience
IT Agile Project Managers, IT Agile Project Development Teams, Anyone related to IT Agile software development
Prerequisites for Attendees
Knowledge on Agile Scrum Practices
Experience in agile scrum usage in IT Projects
Links
https://drive.google.com/open?id=1dUPUMQvVrIE5tvXg8Mak5Q8N1UW2fS1Z
schedule Submitted 1 year ago
Recent Activities
- reply Rohan Mahalekam replied "Hi Abhigya, Appreciate yo..." on the comment Hi Abhigya,Yes, I agree....schedule 1 year ago
- reply Rohan Mahalekam replied "Hi Abhigya,Yes, I agree...." on the comment Hello Rohan, I went throu...schedule 1 year ago
- comment Abhigya Pokharel commented "Hello Rohan, I went throu..." on proposal Stop Spilling Over - Ensu...schedule 1 year ago
Public Feedback