(Or is agile just another way of hiding it away?)

Imagine the following scenario

Fred is a senior developer. The team is doing Scrum for about 10 sprints now, and the ceremonies are kind-of getting into a routine. The team is committing for work to do, and delivering more-or-less what they promised. And yet, Fred is not a happy chappy.

The team is coming to their third release, and there are talks that regression period must be on time, on track this time.

In his frustration, Fred talks to his Scrum Master, expressing his concern that developers must do regression testing yet again in the upcoming regression period. Clearly developers should do coding, and testers should do the testing.

Joe, the Scrum Master reminds Fred that regression is for the entire team, not just for testers, and that they are all in the same boat, and that by coding away during regression they are merely adding more technical debt to an already potentially unstable release.

Fred walks back to his desk, muttering "right; and my testing skills are so good, that all bugs will be uncovered. Such a good tester I am".

What just happened here?

Add a comment

For some reason, for many the essence of the Scrum Master role boils down to: “remove impediments for the team” or “is responsible for the Scrum process”.

Others declare that “the Scrum Master is a kind of a PMO”, or “a facilitator for the team”. Not that it is not part of the Scrum Master role – but it certainly is not the essence.

Furthermore, such statements are demeaning, in my view. Strong word, and yet, making statements such as the above, to me, indicates that the speaker may not yet understand what agility really means.

 

And please don’t get me wrong – it’s not that I think that facilitation is something to look down at. On the contrary – facilitators can save a conference from failing miserably. Similar arguments can be made on PMOs.

Add a comment

One of the key elements in planning in Scrum is basing your forecast on Velocity. In contrast to cars’ performance, the Velocity used in Scrum is not a performance-indicator. Rather, it is a parameter used towards calculating a forecast for a team’s or a project’s short, medium and long term.

Add a comment

What makes a good Scrummer? Well, if I knew an exact formula, I would be too busy selling it to Scrum-wannabees than writing tips about Scrum ;-)

On a more serious note, the differences between organizations is so great, that any ten tips will never be good enough for all.

Nonetheless, I’ve gathered some of the things I found helpful in early stages of Scrum adaptations.

Add a comment

Some people refer to sprints as mini-waterfalls. Well, that’s a mistake, sprint are not that.  But a mistake or not, doing a Mini-Waterfalls still seem to be a natural step for some people when they start with their Agile transformation. 
So how do you create a mini-waterfall?
Well its not very hard like anything else when you create a mini-X you start by taking the X for example:
And then you do the same thing just smaller. Like this:

Add a comment