Select Page


I’ve written before about not being wedded to one version of Agile or another.

As Scrum Master I think it’s my job to educate the team sufficiently to make their own decisions about how to apply Agile in their context.

According to Captain Barbossa “the (agile) code is more what you’d call ‘guidelines’ than actual rules”.

At the end of the day, success is down to the team, they get the credit for delivery, so if they knowingly bend a few rules, that fine.

There are times I enforce the rules to ensure everyone knows why they’re there. A new team starting out at Stand up. For a start, stand up! Secondly, if you’re going to wander in with coffee (because we’re next to the kitchen), then put it down. Good rules. Rules are enforced; both make the meeting more focused. Once we’re done, feel free to sit down, drink coffee and discuss more detail as you would at your desk.

A team faced with a block that may or may not resolve itself this Sprint. Plan stories to cover both eventualities, knowing that some will be pulled at backlog grooming or simply remain in the backlog at the end of the Sprint. Text book behavior? Not really.

Sprint teams spread across more than one location? Most of the literature out there says, “don’t do it”. There is some that says it can work. This seems to focus on a proportion of the team in one location and a proportion in another with a leader in each. Never one person alone. But then, this is the real world and when you’re putting a team together you make the most of what you’re given.

So my mantra; be flexible…be….what’s the word I’m looking for? Oh, yes, be AGILE.


%d bloggers like this: