So, Now You're An Agilist, What's Next?

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

1 comments

Comments 1 - 1 of 1 previous next Post a comment

  • + ziobrando Alberto Brandolini 7 months ago
    I am tempted to say that if the same person is both a ruler and a leader we have a major risk of a dictatorial drift. From indentation to dress code... :-)
Post a comment
Embed Video
Edit your comment Cancel

18 Favorites & 1 Group

So, Now You're An Agilist, What's Next? - Presentation Transcript

  1. Jurgen Appelo [email_address] version 2 So, Now You’re an Agilist... So, Now You’re an Agilist... What’s Next?
    • A. psychological profiles
    • B. leaders vs. rulers
    • C. organization types
    • D. organizational structures
    • E. risk management
    • F. organizational optimization
    • G. adaptive methods
    • H. non-linear improvement
    • J. tuning process dependencies
    • K. classification of methods
    Agile... what’s next? My ideas, taken from complexity science
  2. photo by blumpy disclaimer: this is a... (I sometimes change my opinion)
  3. photo by Randy Son of Robert complexity what is it?
  4. complex systems are self-organized photo by judepics
  5. photo by ClintJCL complex systems show emergent behavior
  6. photo by DavidHR complex systems behave in a non-linear way
  7. photo by Noël Zia Lee (many) complex systems are adaptive
  8. “ For example, an ant colony, the brain, the immune system, a Scrum team, and New York City, are self-organizing systems.” - Ken Schwaber Agile Software Development with Scrum “ At the heart of complex adaptive systems theory’s relevance to software development is the concept of emergence , and the factors leading to emergent results.” - Jim Highsmith Adaptive Software Development
  9. some books I read…
  10. The 12 Laws of Software Development Reduce Risk Measure Performance Evaluate Feedback Acquire Knowledge Manage Uncertainty Evolve Practices Motivate People Empower Teams Align Results Optimize Communication Enforce Discipline Restrain Growth which led me to “discover”…
  11. ? : ? : ? : ? : ? : ? : ? : ? : ? : ? : a complex system ? : Agents Connections Rules
  12. ? : ? : ? : ? : ? : ? : ? : ? : ? : ? : #1: the agents must be active
  13. photo by MikeBlogs
  14. The 1 st Law of Software Development Motivate People
  15. diversity brings robustness and flexibility photo by woodleywonderworks
  16. what motivates one demotivates another
  17.  
  18. Don’t agree? There exists a selection of practices for which the sum of people’s motivational balances is optimal. therefore... “ In a software project the optimal method is a function of the psychological profiles of its team members.” Agreed? A
  19. ? : ? : ? : ? : ? : ? : ? : ? : ? : ? : #2: the system controls itself
  20. photo by Andrew Mason
  21. The 2 nd Law of Software Development Empower Teams photo by Elvire.R .
  22. The Conant-Ashby Theorem: “Every good regulator of a system must have a model of that system.” controller inside the system good model
  23. ? ? ? However... as complexity increases, the models become too simplistic or too big. controller outside the systems bad models
  24. ? : ? : ? : ? : ? : ? : ? : ? : ? : ? : #3: the system is unaligned ? ? ? ?
  25. unaligned self-organization photo by aviplot
  26. aligned self-organization photo by john w
  27. The 3 rd Law of Software Development Align Results photo by The Wandering Angel
  28. self-organization this was the result of… photo by hive
  29. photo by Mike Licht and this too…
  30. photo by WordRidden The Law of Requisite Variety: a system can only be controlled by a more complex system
  31. photo by marcn The Path and the Fence: Lead and Rule
  32. photo by sonictk lead rule managers : find leaders and rulers
  33. Who are the leaders ? Who are the rulers ? “ There should be both leaders and rulers inside and outside the teams.” Don’t agree? Agreed? B
  34. ordered complex chaotic empowerment alignment ordered organizations need empowerment chaotic organizations need alignment The Edge of Chaos
  35. Don’t agree? Agreed? “ How to implement agile depends on whether you come from an ordered or a chaotic situation.” C
  36. ? : ? : ? : ? : ? : ? : ? : ? : ? : ? : #4: the agents communicate
  37. photo by woodleywonderworks
  38. Optimize Communication The 4 th Law of Software Development photo by foxypar4
  39. Optimal communication... Everyone is part of a (small) team All teams are cross-functional All are managed by like-minded manager But... where do we put the manager?
  40. Option 1: Boss in team There are not 3 but 6 levels here! level 1+2 level 3+4 level 5+6
  41. Option 2: Boss not in team Now there are only 3 levels! level 1 level 2 level 3
  42. Option 3: Compromise Only 3 levels, but doesn’t scale well! level 1 level 2 level 3
  43. Don’t agree? Agreed? “ Having the boss not in the team is the best solution for flattening and scaling a hierarchy.” D
  44. ? : ? : ? : ? : ? : ? : ? : ? : ? : ? : #5: the agents stick to rules 1. ----- 2. --- 3. ----- 1. ----- 2. --- 3. ----- 1. ----- 2. --- 3. ----- 1. ----- 2. --- 3. ----- 1. ----- 2. --- 3. ----- 1. ----- 2. --- 3. ----- 1. ----- 2. --- 3. ----- 1. ----- 2. --- 3. ----- 1. ----- 2. --- 3. ----- 1. ----- 2. --- 3. -----
  45. photo by anna pearson
  46. The 5 th Law of Software Development Enforce Discipline photo by kaibara87
  47. photo by mudpig other people’s behavior must be predictable
    • The discipline stack...
    • Self (self-discipline)
    • Coach (teaching from master)
    • Peers (warnings from equals)
    • Signals (steering by infrastructure)
    • Supervisor (a guy walking around)
    • Manager (me, cleaning up the s**t)
    • The higher in this hierarchy discipline is achieved, the better.
  48. ? : ? : ? : ? : ? : ? : ? : ? : ? : ? : #6: the system tends to grow ? : ? : ? : ? : ? : ? : ? : ? : ? :
  49. photo by *Maurice**
  50. The 6 th Law of Software Development Restrain Growth photo by mountainamoeba
  51. photo by daisybush Parkinson’s Law organizations tend to get bigger
  52. Cope’s Rule species tend to get bigger image by Bogdanov
    • Prevent systems from growing...
    • Limit input and output (keep it simple)
    • Make resources scarce (small budgets)
    • Reduce complexity (remove waste)
    • Clean up regularly (refactoring)
  53. ? : ? : ? : ? : ? : ? : ? : ? : ? : ? : #7: the system is exposed to risk
  54. photo by Aaron Escobar
  55. The 7 th Law of Software Development Reduce Risk photo by rednuht
  56. Self-Organized Criticality a critical state of high risk photo by lrargerich
  57. Don’t agree? Agreed? Someone needs to try and reduce the system’s exposure to risk... “ Risk management (mitigating potential impediments) can best be done by stepping outside the system.” E
  58. ? : ? : ? : ? : ? : ? : ? : ? : ? : ? : #8: the system must know how it’s doing +/+ -/-
  59. photo by laffy4k
  60. The 8 th Law of Software Development Measure Performance photo by xmatt
  61. The Tragedy of the Commons: using shared resources photo by ojbyrne
  62. optimize the whole
  63. optimize the whole = manage shared resources
  64. Don’t agree? Agreed? “ Optimize the whole means to optimize to the largest possible span of control, which can mean: don’t optimize the individual software projects.” F
  65. ? : ? : ? : ? : ? : ? : ? : ? : ? : ? : #9: the system responds to the input +/- -/+
  66. photo by makelessnoise
  67. The 9 th Law of Software Development Evaluate Feedback photo by JasonRogers
  68. ? : ? : ? : ? : ? : ? : ? : ? : ? : ? : #10: the system needs ways to learn !
  69.  
  70. The 10 th Law of Software Development Aquire Knowledge photo by procsilas
  71. ? ? : ? : ? : ? : ? : ? : ? : ? : ? : ? : #11: the system must cope with uncertainty
  72. Adaptation to change…
  73. The 11 th Law of Software Development Manage Uncertainty photo by rednuht
  74. The Butterfly Effect small variations, big impact photo by Hamed Saber
  75.  
  76. ? : ? : ? : ? : ? : ? : ? : ? : ? : ? : #12: the system figures out how to change 1. ----- 2. --- 3. ----- 1. ----- 3. --- 4. ----- 1. ----- 2. --- 3. ----- 1. ----- 2. --- 3. ----- 1. ----- 4. --- 5. ----- 1. ----- 2. --- 3. ----- 1. ----- 2. --- 3. ----- 4. ----- 5. --- 6. ----- 2. ----- 3. --- 5. ----- 1. ----- 2. --- 3. -----
  77. photo by Sukanto Debnath genotype (genes) phenotype (body)
  78. The 12 th Law of Software Development Evolve Practices photo by Hulagway
  79. fixed practices = not complex at all
  80. Don’t agree? Agreed? Adaptive phenotype... changing requirements Adaptive genotype... changing environment “ Not just the project, but the method itself must be adaptable too.” G
  81. Fitness Landscapes evaluating performance photo by Hulagway
  82. “ It takes all the running you can do, to keep in the same place.” - Louis Carroll Through the Looking Glass The Red Queen Effect
  83. process improvement Managing -- Metricate Analyze Check 7. Check Measurements -- -- -- Execute Do 6. Execute Processes (implicit) Improving Pilot 5. Implement Improvements Analyzing Improve Choose Act 4. Identify Improvements Plan 3. Define Metrics Targets Target Analyze Set Goals 2. Set Goals Managing Analysis Assess Understand Plan 1. Determine Problems CPI-7 Pr 2 imer AIM QIP PDCA
  84. ? linear improvement stuck on local optimum or walk through the valley (things get worse before they get better)
  85. Crossover photo by Kevin N. Murphy mixing practices from two sources
  86. non-linear improvement find higher peaks by averaging prior high performers
  87. Don’t agree? Agreed? “ Linear improvement works up to a point, but to find the optimal development process you need a non-linear approach.” H
  88. moderately connected system (several optimums) sparsely connected system (one optimum) intensively connected system (no real optimum)
  89. Don’t agree? Agreed? “ Methods are strong when it’s easy to replace individual practices.” J
  90. sudden burst of solutions image by Karl J. Niklas Punctuated Equilibrium
  91. Attractors convergence of forms photo by Okko Pyykkö
  92. Don’t agree? Agreed? “ We now experience a burst of methods and tools, due to environmental change. This could converge into a few main forms with many small variations.” K
  93. The 12 Laws of Software Development Reduce Risk Measure Performance Evaluate Feedback Acquire Knowledge Manage Uncertainty Evolve Practices Motivate People Empower Teams Align Results Optimize Communication Enforce Discipline Restrain Growth ANY creative team project
    • A. psychological profiles
    • B. leaders vs. rulers
    • C. organization types
    • D. organizational structures
    • E. risk management
    • F. organizational optimization
    • G. adaptive methods
    • H. non-linear improvement
    • J. tuning process dependencies
    • K. classification of methods
    Agile... what’s next? Don’t agree? Agreed?
  94. Thanks, I hope to have inspired you! Q & A picture by - bast -
  95. @jurgenappelo
  96.  
    • This presentation was inspired by the works of many people, and I cannot possibly list them all. Though I did my very best to attribute all authors of texts and images, and to recognize any copyrights, if you think that anything in this presentation should be changed, added or removed, please contact me at [email_address] .
    http://creativecommons.org/licenses/by-nd/3.0/

+ Jurgen AppeloJurgen Appelo, 7 months ago

custom

3028 views, 18 favs, 14 embeds more stats

Doing projects better doesn't stop at agile. In thi more

More info about this document

CC Attribution-NoDerivs LicenseCC Attribution-NoDerivs License

Go to text version

  • Total Views 3028
    • 2265 on SlideShare
    • 763 from embeds
  • Comments 1
  • Favorites 18
  • Downloads 242
Most viewed embeds
  • 411 views on http://www.noop.nl
  • 194 views on http://www.marketingfacts.nl
  • 81 views on http://agileee.org
  • 34 views on http://team.custis.ru
  • 12 views on http://agilemusings.com

more

All embeds
  • 411 views on http://www.noop.nl
  • 194 views on http://www.marketingfacts.nl
  • 81 views on http://agileee.org
  • 34 views on http://team.custis.ru
  • 12 views on http://agilemusings.com
  • 9 views on http://www.denao.com.br
  • 9 views on http://agileee.com
  • 5 views on http://static.slideshare.net
  • 3 views on http://bodhuin.blogspot.com
  • 1 views on http://www.agileee.com
  • 1 views on https://thesource.shoplocal.com:8443
  • 1 views on http://presentations.tumblr.com
  • 1 views on http://nooperation.typepad.com
  • 1 views on http://xss.yandex.net

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories

Groups / Events