What (Else) Can Agile Learn From Complexity

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

Post a comment
Embed Video
Edit your comment Cancel

9 Favorites

What (Else) Can Agile Learn From Complexity - Presentation Transcript

  1. Jurgen Appelo [email_address] version 2 image by BotheredByBees Jurgen Appelo [email_address] version 2 What (Else) Can Agile Learn from Complexity? What (Else) Can Agile Learn from Complexity?
  2. QDD (Quote-Driven Discourse) Misquotation is, in fact, the pride and privilege of the learned. A widely-read man never quotes accurately, for the rather obvious reason that he has read too widely. Hesketh Pearson (1934) Common Misquotations http://www.amazon.com/Common-Misquotations-Hesketh-Collected-Pearson/dp/B00128UERS/ “ ”
  3. Let’s start! Let’s start!
  4. Agile Software Development 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 http://www.amazon.com/Agile-Software-Development-Scrum/dp/0130676349/ “ ”
  5. Agile Software Development 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 http://www.amazon.com/Adaptive-Software-Development-Collaborative-Approach/dp/0932633404/ “ ”
  6. Agile Software Development Scrum is not a methodology, a defined process or set of procedures. It's an open development framework. The rules are constraints on behavior that cause a complex adaptive system to self-organize into an intelligent state. Jeff Sutherland Shock Therapy (presentation) “ ”
  7. The Evolution of Complexity Science image by Brian Castellani
  8.  
    • Are software projects complex systems?
    • Can we apply complexity science to management?
    image by practicalowl
  9. Beware!! Abuse of Science
    • To use scientific terminology without bothering much about what the words actually mean .
    • Importing scientific concepts without giving the slightest empirical or conceptual justification .
    • Displaying superficial erudition by shamelessly throwing around terms where they are irrelevant .
    • Exhibiting a veritable intoxication with words, with a superb indifference to their meaning.
    • Sokal, A. and Bricmont, J. (1998)
    • Intellectual Impostures: Postmodern Philosophers’ Abuse of Science
    • http://www.amazon.com/Intellectual-Impostures-Alan-Sokal/dp/1861976313
    “ ”
  10. Complexity vs. Management
    • Not unexpectedly, the complexity gurus are most upset with how complexity science terms are loosely, if not metaphorically, defined and tossed in managerial discourse – one [guru] goes as far as to suggest that the books offer many insights for managers, but one should simply black out all references to complexity science.
    • Maguire, S. and McKelvey, B. (1999) “Complexity and Management: Moving from fad to firm foundations” http://iscepublishing.com/ECO/ECO_papers/Issue1_2_2.pdf
    “ ”
  11. Compromise: Loose Application
    • The word “culture” in business culture was (successfully) borrowed from anthropology .
    • The word “strategy” in business strategy was borrowed from the military . (In fact, the science of game theory borrowed the word for evolutionary stable strategies !)
    • Loose application ( borrowing and bending ) of terminology across disciplines is more than just the invention of metaphores. The terms actually have meaning .
    • Van Uden, J. (2005)
    • “ Using complexity science in organization studies: a case for loose application”
    • http://iscepublishing.com/ECO/ECO_papers/Issue_7_1_8_PH.pdf
  12. Snowden, D. and Stanbridge, P. (2004) “The Landscape of Management: Creating the context for understanding social complexity” http://iscepublishing.com/ECO/ECO_other/Issue_6_1-2_19_FM.pdf
  13. humans involved, not mechanics complex, not ordered Snowden, D. and Stanbridge, P. (2004) “The Landscape of Management: Creating the context for understanding social complexity” http://iscepublishing.com/ECO/ECO_other/Issue_6_1-2_19_FM.pdf
  14. Example: Self-Organization
    • Self-organization is a process of attraction and repulsion in which the internal organization of a system, normally an open system, increases in complexity without being guided or managed by an outside source.
    • Self-Organization
    • http://en.wikipedia.org/wiki/Self-organization
    • Are self-organizing teams really self-organizing?
    “ ”
  15. Example: Emergence
    • Emergence is the arising of novel and coherent structures, patterns and properties during the process of self-organization in complex systems.
    • Corning, P.A. (2002)
    • “ The Emergence of Emergence: Now What?”
    • http://iscepublishing.com/ECO/ECO_papers/Issue4_3_3.pdf
    • Is emergent design really emergent?
    “ ”
  16.  
  17. Software Projects Scope Features Qualities People Tools Resources Parts Artifacts Product
    • Yes, we can apply complexity to management
    • Yes, software projects are complex systems
    image by Peter Kaminsky
  18. Darkness Principle
    • Each element in the system is ignorant of the behavior of the system as a whole [...] If each element ‘knew’ what was happening to the system as a whole, all of the complexity would have to be present in that element.
    • Richardson, K.A. (2002) “Systems theory and complexity: Part 1” http://iscepublishing.com/ECO/ECO_other/Issue_6_3_10_FM.pdf
    “ ”
  19. Traditional Monitoring and Control fails (no project manager can know everything) image by Okko Pyykkö
  20. The Law of Requisite Variety
    • If a system is to be stable the number of states of its control mechanism must be greater than or equal to the number of states in the system being controlled.
    • Variety (Cybernetics) http://en.wikipedia.org/wiki/Variety_%28cybernetics%29
    “ ”
  21. Traditional Management fails (one manager is less complex than a group) image by flattop341
  22. Boundaries and Conditions
    • Self-organization requires that t he system is surrounded by a containing boundary . This condition defines the "self" that will be developed during the self-organizing process.
    • Eoyang, G. and Conway D.J. (1999)
    • “ Conditions That Support Self-Organization in a Complex Adaptive System” http://amauta-international.com/iaf99/Thread1/conway.html
    “ ”
  23. image by Robbie W T Agile Management is a crucial part of Agile (Defining boundaries and conditions)
  24. Hierarchy Principle
    • Complex natural phenomena are organized in hierarchies wherein each level is made up of several integrated systems .
    • Skytner, L. (2001) “General Systems Theory: Ideas and Applications” NJ: World Scientific
    “ ”
  25. Example: Scrum of Scrums image by Mountain Goat Software managed self-organized Hierarchies are not a problem, they are natural Managed (imposed) hierarchies are the problem
  26. Patches
    • Take a conflict-laden task in which many parts interact, and divide it into a quilt of non-overlapping patches . Try to optimize within each patch . As this occurs […] a good solution in one patch will change the problem to be solved in adjacent patches.
    • Kaufman, S. (1995) At Home in the Universe
    • http://www.amazon.com/At-Home-Universe-Self-Organization-Complexity/dp/0195111303/
    “ ”
  27. Example: Patches of Scrums image adapted from Mountain Goat Software An ecosystem of teams instead of a hierarchy
  28. Group Size
    • There is a particular number of decision-makers that stands out from the trend as being truly, spectacularly bad, tending with alarmingly high probability to lead to deadlock: eight .
    • Buchanan, M. (2009) “Explaining the curse of work” http://www.newscientist.com/article/mg20126901.300-explaining-the-curse-of-work.html
    “ ”
  29. image by Jayel Aheram Good team size = 7 +/- 2 ( except 8) (5 might be perfect)
  30. Specialization
    • In more complex organisms – from eukaryotic protists to social mammals – specialization among the parts (or division of labor ) produces many advantages for various wholes.
    • Corning, P.A. (2002) “The Emergence of Emergence: Now What?” http://iscepublishing.com/ECO/ECO_papers/Issue4_3_3.pdf
    “ ”
  31. Specialization is not a problem, it is natural Managed (imposed) specialization is the problem image by Ali
  32. Power Laws
    • Scale-free networks are ubiquitous in nature due to the adaptive properties of robustness and fast communication associated with power-law degree distributions.
    • Mitchell, M. (2009) Complexity: A Guided Tour http://www.amazon.com/Complexity-Guided-Tour-Melanie-Mitchell/dp/0195124413/
    “ ”
  33. Power laws exhibit scale invariance You can’t estimate size of next unknown issue size of issues frequency of issues high chance of small issues low chance of large issues
  34. Prediction of velocity includes an (impossible) estimate of the size of unknown problems image by cod gabriel
  35. Dependence on Context
    • A project cannot be viewed independent of its surrounding context […]. An understanding of the context is in itself not sufficient to prescribe a method […]. Rather, the method to manage the project is embedded in the context and one must allow the emergence of such a method through interaction between the actors and the environment.
    • Pundir, A.K., Ganapathy, L. And Sambandam, N. (2007) “Towards a complexity framework for managing projects” http://iscepublishing.com/ECO/ECO_papers/Issue_9_4_3_AC.pdf
    “ ”
  36. ScrumButs are natural and necessary Management methods must emerge Standard methods must be customized
  37. Fitness Landscapes
    • The environment is not out there, separate from us. We can help to create the environment . […] The Spanish have phrase […]: “My friend, there is no road. You make the road as you walk.”
    • Dent, E.B. (1999) “Complexity Science: A Worldview Shift” http://iscepublishing.com/ECO/ECO_papers/Issue1_4_1.pdf
    “ ”
  38. The environment responds to released software Success can only be known after deployment image by neona
  39. ? linear improvement stuck on local optimum or walk through the valley (linear) retrospectives may stop working
  40. image by Kevin N. Murphy mixing practices from two sources Crossover
  41. non-linear improvement finding higher peaks by mixing prior high performers Switch from linear to non-linear retrospectives (Replace multiple practices at a time)
  42. moderately connected system (several optimums) sparsely connected system (one optimum) intensively connected system (no real optimum)
  43. If you can’t replace a practice, tool, or person, you shouldn’t even add them in the first place image by wilhei55
  44. disturbances enable the system to find deeper valleys (inverted landscape, lower = better) Noise
  45. image by Hamed Saber The Butterfly Effect Small changes, BIG consequences
  46. Incompressibility
    • There is no accurate representation of the system which is simpler than the system itself. In building representations of open systems, we are forced to leave things out, and since the effects of these omissions are nonlinear, we cannot predict their magnitude.
    • Cilliers, P. (2005) “Knowing complex systems”
    • Managing Organizational Complexity: Philosophy, Theory And Application
    • http://www.amazon.com/Managing-Organizational-Complexity-Philosopy-Application/
    “ ”
  47. Because of the butterfly effect, we cannot predict the consequences of leaving something out Consequence: a variety of imperfect methods image by woodleywonderworks
  48. Models
    • All models are wrong , but some are useful .
    • Box, G. and Draper, N. (1969) Evolutionary Operation: A Statistical Method for Process Improvement
    • http://www.amazon.com/Evolutionary-Operation-Statistical-Process-Improvement/dp/B0028H5YDG/
    “ ”
  49. My Book The Software Cultivator Managing Agile Organizations (2010) ? Jurgen Appelo
  50. Disclaimer
    • I might have used scientific terminology without really understanding what the words actually mean .
    • I might have imported scientific concepts without giving sufficient justification .
    • I might have thrown around scientific terms where they are irrelevant .
    • And I might have an intoxication with words...
  51. But I hope to have inspired you... Q & A image by -bast-
  52. @jurgenappelo
    • 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, 3 months ago

custom

2169 views, 9 favs, 4 embeds more stats

How can complexity science be applied to software d more

More info about this document

CC Attribution-NoDerivs LicenseCC Attribution-NoDerivs License

Go to text version

  • Total Views 2169
    • 1944 on SlideShare
    • 225 from embeds
  • Comments 1
  • Favorites 9
  • Downloads 131
Most viewed embeds
  • 216 views on http://www.noop.nl
  • 4 views on http://www.slideshare.net
  • 3 views on http://www.emergentstory.com
  • 2 views on http://www.hanrss.com

more

All embeds
  • 216 views on http://www.noop.nl
  • 4 views on http://www.slideshare.net
  • 3 views on http://www.emergentstory.com
  • 2 views on http://www.hanrss.com

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