Myths, Legends & Monsters<br />The Quest for the Grail of Enterprise Agility<br />François Bachmann, SPRiNTiT<br />
Who’stalking<br />François Bachmann<br /><ul><li>« The UrbanTraffic Parable »
« The Art of the Retrospective » (Agile-Alchemist.com)
Organisational DevelopmentCoach since 2004
Interests:SystemicThinking, Complex Adaptive Systems (like a Jam Session @AgileEE)</li></li></ul><li>What You ShouldGet<b...
Your initial situation<br />Pilot project « success » <br />Request/need to scalethissuccess<br />Existingcompany<br />]Ou...
Warnings(1)<br />Scalingisalwayscomplex<br />
Warnings (2)<br />Agile is a mindset, an attitude plan lots of time for full-fledged adoption<br />
Starter: A customermyth<br />« Normal Change » at a Swissbank<br />Source: http://itsm.certification.info/normalchg.html<b...
Myth<br />A traditional or legendary storythatcancontain a moral lesson<br />Built on ArchetypesGods, animals, angels, dem...
Myths: projectchoice / dimension<br />« Let’s do Agile within a fixed-pricecontract »<br />« Weapply Agile but only to Dev...
Myths: Roles<br />ScrumMaster:  Thor / Superman / <br />James Bond / Chuck Norris<br />« ThreeRolesisenough for anycompany...
Myths: transition<br />« Just use Scrum of Scrumsand everythingwillbe fine»		<br />« Trust me, in thiscompanyweknowwhat ch...
Summary: Myths<br />Main purpose: federate<br />Used for justification of status quo <br />Usuallyinvolvesuperhumans<br /...
Legend(lat. legenda = to beread)<br />Official shape of the rumourspreadduring coffee breaks<br />« I know someonewho… »<b...
Legend: Company Culture<br />	« My cousin tried to introduce Agile in hiscompany: itdidn’tworkat all! Now I agreethatthey ...
Customer Legends: Company Culture<br />Mediterranean: mix of nationalities<br />Web company: resource allocation > flow<br />
Legends: Organisation<br />« It seemsthatthiswon’tworkin an outsourcing context… »<br />« Another team in our division use...
Legends: Transition<br />« A well-planned transition is the cornerstoneof success: plan the work, work the plan»<br />« Le...
Legend: Tool<br />« Company X boughttool Y whentheymoved to Agile and the wholeenterpriseisnowusingit. But how can I convi...
Summary: Legends<br />Purpose: Institutionalized Learning<br />« Whathasn’tworked in the past and whatwere the consequence...
Monster (lat. monstrum:wildbeast)<br />Impersonatesresistance<br />Gatekeeper<br />Requires the hero to go beyond the norm...
Monsters: Middle Management<br />« I’llbe the Scrum Master for all teams  »<br />« I can replace the Product Owner, if nee...
Monster: Project/Process Office<br />Distinguishing marks: once theyunderstand Agile is not goingaway, theywilltry to gove...
Monster: Saboteur<br />Definition: Person whoisinvolvedbut has a hidden agenda (subversion, obstruction, disruption, or de...
Monster: AgileGuru<br />Pretends to sell the One And Only Agile <br />Distinguishing marks: elitist, likes to fight(he/she...
Summary: Monsters<br />Strongholds, Gatekeepers<br />Have power & reputation<br />Ofteneasier to « turnaround » than to ov...
Summary<br />
Upcoming SlideShare
Loading in...5
×

Myths, legends and monsters: The Quest for the Grail of Enterprise Agility

578

Published on

A different view of the obstacles facing the Agile Warrior trying to spread the good news to more than his team (eg. the department, the division, the company). Includes advice on how to deal with obstacles and how to use existing Company Culture.

Published in: Business, Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
578
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Myths, legends and monsters: The Quest for the Grail of Enterprise Agility

  1. 1. Myths, Legends & Monsters<br />The Quest for the Grail of Enterprise Agility<br />François Bachmann, SPRiNTiT<br />
  2. 2. Who’stalking<br />François Bachmann<br /><ul><li>« The UrbanTraffic Parable »
  3. 3. « The Art of the Retrospective » (Agile-Alchemist.com)
  4. 4. Organisational DevelopmentCoach since 2004
  5. 5. Interests:SystemicThinking, Complex Adaptive Systems (like a Jam Session @AgileEE)</li></li></ul><li>What You ShouldGet<br />
  6. 6. Your initial situation<br />Pilot project « success » <br />Request/need to scalethissuccess<br />Existingcompany<br />]Out of Scope[<br />Introduction to Agile, Lean, Scrum, XP, …<br />Growing an agile company<br />
  7. 7. Warnings(1)<br />Scalingisalwayscomplex<br />
  8. 8. Warnings (2)<br />Agile is a mindset, an attitude plan lots of time for full-fledged adoption<br />
  9. 9. Starter: A customermyth<br />« Normal Change » at a Swissbank<br />Source: http://itsm.certification.info/normalchg.html<br />
  10. 10. Myth<br />A traditional or legendary storythatcancontain a moral lesson<br />Built on ArchetypesGods, animals, angels, demons, otherworlds<br />Used to justify a social institutionand itsway of viewing the world<br />Toldatceremonies(start, transformation, end)<br />Principal purpose: federate<br />Source: dictionary.reference.com<br />
  11. 11. Myths: projectchoice / dimension<br />« Let’s do Agile within a fixed-pricecontract »<br />« Weapply Agile but only to Development »<br />« We do ALL ourprojectswith Agile»<br />
  12. 12. Myths: Roles<br />ScrumMaster: Thor / Superman / <br />James Bond / Chuck Norris<br />« ThreeRolesisenough for anycompany »  Scrumdamentalism (H.Kniberg)<br />« In ourcompany, we’re all like a bigfamily»<br />
  13. 13. Myths: transition<br />« Just use Scrum of Scrumsand everythingwillbe fine» <br />« Trust me, in thiscompanyweknowwhat change management is! »<br />« To reallybecome Agile, you have to destroy & rebuild from scratch»<br />
  14. 14. Summary: Myths<br />Main purpose: federate<br />Used for justification of status quo <br />Usuallyinvolvesuperhumans<br />Reveal values of the company<br />
  15. 15. Legend(lat. legenda = to beread)<br />Official shape of the rumourspreadduring coffee breaks<br />« I know someonewho… »<br />UrbanLegend<br />Can end bothways<br />Finisheswith a lesson to learn<br />Principal purpose: education<br />
  16. 16. Legend: Company Culture<br /> « My cousin tried to introduce Agile in hiscompany: itdidn’tworkat all! Now I agreethatthey have a veryspecialcompany culture….»<br /> « Actually, ourcompany culture has always been agile; let’sjust change the terminology and we’llbe fine»<br />
  17. 17. Customer Legends: Company Culture<br />Mediterranean: mix of nationalities<br />Web company: resource allocation > flow<br />
  18. 18. Legends: Organisation<br />« It seemsthatthiswon’tworkin an outsourcing context… »<br />« Another team in our division useditduringa few months, theirproductivitydropped… and theyswitched back afterwards»<br />« What about mycareer plan? »<br />
  19. 19. Legends: Transition<br />« A well-planned transition is the cornerstoneof success: plan the work, work the plan»<br />« Let’sjustestablish a matrixbetween the old and the new roles»<br />
  20. 20. Legend: Tool<br />« Company X boughttool Y whentheymoved to Agile and the wholeenterpriseisnowusingit. But how can I convincemy management?  »<br />
  21. 21. Summary: Legends<br />Purpose: Institutionalized Learning<br />« Whathasn’tworked in the past and whatwere the consequences »<br />Advice: are a very efficient communication tool: « Worst Practices » or NotHow-Transfer©<br />
  22. 22. Monster (lat. monstrum:wildbeast)<br />Impersonatesresistance<br />Gatekeeper<br />Requires the hero to go beyond the normal plan<br />
  23. 23. Monsters: Middle Management<br />« I’llbe the Scrum Master for all teams  »<br />« I can replace the Product Owner, if needed »<br />« Well, someone has to assign the developers to projects, no?!  »<br />Strengths: network, relationships<br />Weaknesses: conflictingpriorities,overestimateshispotential influence<br />Fights for: his position and his « power »  Approach: givehim a catalystrole,activelyinclude in information exchange<br />
  24. 24. Monster: Project/Process Office<br />Distinguishing marks: once theyunderstand Agile is not goingaway, theywilltry to governit and createrules<br />Strength: power to standardize<br />Weakness: mechanistic world view<br />Fights for: being the process masterand force theirrules on developers<br /> Approach: 1) producetheir artefacts and2) when the right time comes: question the value ofthese artefacts (not of the Project Office!)<br />
  25. 25. Monster: Saboteur<br />Definition: Person whoisinvolvedbut has a hidden agenda (subversion, obstruction, disruption, or destruction)<br />Strength: internalknowledge<br />Weakness: bottleneck<br />Fights for: « unofficial » priorities<br /> Approach: makeresponsibilities explicit, confront one-on-one if necessary<br />
  26. 26. Monster: AgileGuru<br />Pretends to sell the One And Only Agile <br />Distinguishing marks: elitist, likes to fight(he/sheusuallywins)<br />Strength: *very* convinced by his Agile flavor<br />Weakness: exclusive, tends to workalone<br />Fights for: hisTruth (destroyingothers)<br />Approach: recall Agile values, let him show how hisflavorbringsthemforward<br />
  27. 27. Summary: Monsters<br />Strongholds, Gatekeepers<br />Have power & reputation<br />Ofteneasier to « turnaround » than to overpower<br />Advice: don’tplay on theirterritory!<br />
  28. 28. Summary<br />
  29. 29. Enjoy the Quest, brave knights!<br />
  30. 30. Thanks!<br />© Pixar Technologies, Inc.<br />f.bachmann@sprint-it.ch<br />FrBachmann<br />

×