Viewing entries tagged
Mirko Kleiner

Why Scrum is that successful - Another perspective

4 Comments

Why Scrum is that successful - Another perspective

I recently talked with a Scrum Newby about why scrum is that successful and what makes the difference. I explained him that based at an instrument he knew, the task force.A task force is a temporary grouping of best resources for the accomplishment of a specific objective within shortest possible time. In IT it’s usually to solve a business critical incident.

4844707562_e22e72af2d

If we compare a scrum team with a Task Force I see a lot of overlappings. We put together a multi-funtional team, containing of best resources each to accomplish fastest possible our objectives. While this process the scrum team has full management attention with direct communication to. Outcome has to fulfill highest business value, otherwise company looses time-to-market and it will become a problem. Only difference is that a Task Force will be disband after incident is solved. In other words we also could say:

"Scrum Teams are ongoing Task Forces"
Mirko Kleiner, 11/2013

Interesting point thinking about Task Forces is, that this is not new -but used very rarely- and just in extreme situations. Question is why, it’s approved and one of multiple reasons why Scrum is that successful.

4 Comments

1 Comment

When we have a distributed Scrum?

I'd like to present you my personal definition of "Distributed Scrum". Do not take it too serious. But on the other hand it's not so wrong too. In discussions with newbie's about distributed scrum I often notice, that they put it in relation with nearshore/offshore teams. This gave me reason for finding a simple definition, that makes sense for business people too :-).

2013-10-17_09-35-40

It's a fact that a lot of informal talks but also social integration are important topics during a coffee break. Thinking about this I came up with idea, that

TO BE ONE TEAM IT "HAS" TO USE SAME COFFEE MACHINE.

Mirko Kleiner, 10/2013

If they don't do, they are distributed and should organize themselves as distributed scrum teams do. I often saw on customer side, that those teams are not aware of being a distributed teams. In other words companies with multiple offices, even in same street/city/country have distributed teams and should be aware of that while implementing scrum.

1 Comment