Menu
With Scrum, there is the principal of user stories and these stemming tasks etc etc iterating around to a finished product - which is fine.
But, let's say I have 100 features that need implementing, in the real world I can't put any developer on these until a lot of the normal ancillary stuff has been done - for instance, doing a UI design (surely you need to have an overall idea of functionality for this?), or building the underlying stuff that doesn't necessarily manifest itself as a feature.
So, where does this happen?
355
it's better to reintroduce unfinished items to the backlog and give the team another chance to select their work. it's a good learning experience.
If spillover is a problem for your team, there are a few things you should consider doing. First, you need to break the habit. Encourage the team to plan its next sprint such that they can definitely finish everything. That is, go light and plan the next sprint conservatively.
Sprint items not completed will go back to the Product Backlog. Depending on the prioritization the items may be candidates for next sprint or later sprints to be pulled by the teams into their sprint backlog.
My understanding is that in scrum you only build what is required to implement each user story. Therefore, you build the underlying stuff that is not a feature only when it is required to implement a feature for the user story you are working on.
147
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
