How to deal with Spill Over into the Next Sprint

How many times has it been when the iteration is over but not all User Stories have been done. Spillover is a frown-upon practice, however it is a reality and as a scrum master, you have to deal with it. It is absolutely important to draw patterns from the spillover to identify the root causes and apply the findings to future sprints to avoid its re-occurrence. Causes of Spillover Before diving into ways to avoid spillovers, it’s good to know what are the potential causes of this unfinished work. I have compiled a list of the main categories where majority of unfinished work fall into: Team overestimated what they could complete in one iteration.Team underestimated one or more of the...

Read More

Team members not fully allocated

How many times have you been on an Agile team where there are team members that are not fully allocated to the iteration/Sprint? Has it been frustrating? Do you see it as an impediment? but most importantly, how do you deal with such situation? Every Agile implementation and in every organization you will run into this situation. Certain team members that are either shared across multiple teams, or having to work on support items while in the middle of a sprint/iteration, or there is this person that everyone needs on the team because there is only one of him in the organization - in my situation this is the integration/middle-ware guru. Well, you are not alone. We have all been...

Read More