You are here


Scaling Scrum (3-4 teams) (Part 1)

Scaling Scrum is easy, have a look at the Scrum guide at . You have a number of teams that each operate as normal and a member from each of the team attends an additional daily scrum. Yes, it all makes sense, but it is a lot easier to say than do, even on a small scale. There are a few practical things that newer teams and organisations need to think about and do other things will descend into a state of anarchy.

By and large there are two sets of circumstances where you need to scale.

Terminating a sprint

Terminating a sprint is essentially throwing away unaccepted work in the sprint the sprint and starting a new sprint instead. This is not a decision that should be taken lightly as it costs. It costs time, it costs effort and it costs money. It will also ruffle more than a few feathers. It is however cheaper that continuing with a sprint that is invalid, will provide no business benefit and not be delivered.

On what day should your iteration start and end?

Surely start on a Monday and end on a Friday. Nope, unfortunately it is not as easy as that!
Never end on a Friday is a good maxim, well not unless it takes all weekend to deploy. Why not end on a Friday then it give us the entire weekend as a safety net if things go wrong?

Subscribe to RSS - iteration