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.

Mirko Kleiner is a Blogger, Agilist (Agile Evangelist), Vice President Delivery at youngculture AG, Twitterer, Father of 2 beautyful Sons and Partner of a lovely Wife.

Tagged with: , , , , , , , , ,
Veröffentlicht in field experience, scrum
4 comments on “Why Scrum is that successful – Another perspective
  1. Hans-Peter Korn sagt:

    Dieses Bild: „Scrum Team = Task Force“ entspricht tatsächlich etlichen Realsituationen, die von einem pausenlosen von Sprint zu Sprint Gehetze (bestenfalls ein halber Tag Pause zwischen Review und Planning) geprägt sind und von einem Verplanung des Teams zu mehr als 70% seiner Kapazität. Ein paar Wochen lang – wie bei üblichen Task Forces – ist das machbar, nicht aber bei kontinuierlichen Produktentwicklungen, die sich über viele Monate und Jahre erstrecken. Folge davon: Signifikant schlechtere Wartbarkeit und Erweiterbarkeit der Lösungen – wie eine Studie der FH NW-Schweiz aus dem Jahr 2012 zeigt.

  2. mirkokleiner sagt:

    Hallo Hans-Peter
    depends at company culture, but yes I also noticed that. Could you please post the link to that Study?
    cheers Mirko

  3. Hans-Peter Korn sagt:

    You find the link and the details (as a table) on page 118 here: http://www.korn.ch/archiv/publikationen/Neuer-Wein-in-alte-Schlaeuche-oder-Deja-vu.pdf

  4. mirkokleiner sagt:

    super, thx!-Just to give the followers all the facts🙂

Schreibe einen Kommentar

Trage deine Daten unten ein oder klicke ein Icon um dich einzuloggen:

WordPress.com-Logo

Du kommentierst mit Deinem WordPress.com-Konto. Abmelden / Ändern )

Twitter-Bild

Du kommentierst mit Deinem Twitter-Konto. Abmelden / Ändern )

Facebook-Foto

Du kommentierst mit Deinem Facebook-Konto. Abmelden / Ändern )

Google+ Foto

Du kommentierst mit Deinem Google+-Konto. Abmelden / Ändern )

Verbinde mit %s

mirkokleiner

mirkokleiner

Mirko Kleiner is a Blogger, Agilist (Agile Evangelist), Vice President Delivery at youngculture AG, Twitterer, Father of 2 beautyful Sons and Partner of a lovely Wife.

Verifizierte Dienste

Vollständiges Profil anzeigen →

  • When you blame others you give up your power to change. Take responsibility for your future! - Chris Voss #quote 9 hours ago
  • Let us never negotiate out of fear. But let us never fear to negotiate. - John F. Kennedy #quote 12 hours ago
  • Success is the result of good judgement, which is the result of experience, experience is often the result of bad judgement. - Tony Robbins 1 day ago
  • RT @BillGates: Anybody can learn to code. And everyone should give it a try: b-gat.es/2h3cAzd #HourOfCode 1 day ago
  • Do what you can, with what you have, where you are. - Theodore Roosevelt #quote 1 day ago
%d Bloggern gefällt das: