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 week ago
Recent Activities
- reply Rohan Mahalekam replied "Hi Abhigya,Yes, I agree...." on the comment Hello Rohan, I went throu...schedule 1 week ago
- comment Abhigya Pokharel commented "Hello Rohan, I went throu..." on proposal Stop Spilling Over - Ensu...schedule 1 week ago
- assignment Rohan Mahalekam added a new proposal Stop Spilling Over - Ensu...schedule 1 week ago
Call for Proposals 18 days left
Submit before Aug 11 '19 05:29 AM IST
Please note that the proposals need to meet some minimum requirements as listed below to qualify for program committee feedback
- Reasonable Outline/Structure for the session
- Learning Outcomes
- Basic speaker’s profile (LinkedIn or personal website)
- Target Audience
- Links to your previous speaking history (if you have)
We recommend including at least one of:
* Slides
* video (past or 2 mins trailer of the session recorded using a phone, google hangout, etc.)
* mind map
Your goal is to include enough information about what you will present and how you will present it that we can judge your proposal quickly (and positively)!
**Responding to feedback from review team- Please respond to comments from the review team promptly. If it will take you more than a few days to respond, please let the team know that you are working on it and when they expect an answer. Please understand that not responding to comments can be a reason to decline your proposal.
Kindly check your proposal to ensure that you have answered any open comments. Thank you!
Public Feedback
Hello Rohan,
I went through the slides shared by you. Not sure about the content in it. Would it not be bit short for a 45 minutes talk, unless you are giving a number of solutions in depth.