Breaking the spint
They all talk about it: when the sprint objectives are less important than other tasks, then the sprint should be broken. So, we broke the sprint. Then what? Who is responsible now? Do we have a mini-sprint? Do we have daily scrums? I dunno. Googled the thing but only got rugby hits. It's devestating for the morale. But it's only a week left and th important thing now is to get everything ready for the July sprint. What about the problem we were supposed to fix? Well, that we fixed the day after we broke the sprint. Ever since, we've also focused on fixing other, not as crucial but in the long term devestating, bugs.
And an update on my head: I actually went to see a doctor. He said the bumb in the back of the head was pretty large and that is probably why I'm stuck with headaches for now. Im running some tests next week but he wasn't too worried.
Labels: team
posted by Anna Forss @ 3:32 PM
3 Comments:
When you break a Sprint you start over and begins a new sprint after a renewed sprint startup and sprint planning. This should be done as soon as possible.
Don't stick to your pre planned sprint schedule that is just not agile. Get going ASAP and get back into the rhythm.
Well, then the coming sprint should have been planned, and that has not been done yet.
Well if there is some thinks to do on the product backlog at all those items should be put into the sprint planning meeting.
In my opinion there is nothing that would stop you from adding non coding tasks like feature planning and architecture spikes and alike as a sprint task.
If there isn’t enough work for a regular sprint length then commit to a shorter one. The important part is to keep moving on forward with a committed team.
Post a Comment
Subscribe to Post Comments [Atom]
<< Home