Successfully reported this slideshow.

Agile Application Lifecycle Management (ALM)



Loading in …3
1 of 94
1 of 94

More Related Content

Agile Application Lifecycle Management (ALM)

  1. 1. Agile ALM Application Lifecycle Management Dealing with Complexity Jurgen Appelo Version 3
  2. 2. Jurgen Appelo writer, speaker, entrepreneur...
  3. 3. Can Application Lifecycle Management (ALM) work in an environment that grows ever more complex? And how does this relate to the first Agile principle, which promotes “people over processes and tools?” ALM: Dealing with Complexity
  4. 4. Typical software development
  5. 5. One small change
  6. 6.
  7. 7.
  8. 8.
  9. 9. Or to say STOP! We won’t change this.
  10. 10. The result is a big entangled mess
  11. 11.
  12. 12. Quasimodo software heart of gold, broken body Image via Google Search
  13. 13. And it doesn’t get easier…
  14. 14. Increasing number of technologies
  15. 15. Increasing levels of globalization
  16. 16. Increasing amount of customization
  17. 17. Lehman’s Laws of Software Evolution
  18. 18. Continuing Change Lehman’s 1st Law “A system must be continually adapted or else it becomes progressively less capable of satisfying its users.”'s_laws_of_software_evolution
  19. 19. Increasing Complexity Lehman’s 2nd Law “As a system evolves its complexity increases unless work is done to reduce it.”'s_laws_of_software_evolution
  20. 20. Self-Regulation Lehman’s 3rd Law “The system evolution process is self-regulating with product and process measures closely following a normal distribution.”'s_laws_of_software_evolution
  21. 21. Organizational Stability Lehman’s 4th Law “The average activity rate (maintenance) in an evolving system is invariant over its lifetime.”'s_laws_of_software_evolution
  22. 22. Conservation of Familiarity Lehman’s 5th Law “As a system evolves all people involved with it must maintain mastery of its content and behavior to achieve satisfactory evolution.”'s_laws_of_software_evolution
  23. 23. Continuing Growth Lehman’s 6th Law “The functional content of a system must be continually increased to maintain user satisfaction over its lifetime.”'s_laws_of_software_evolution
  24. 24. Declining Quality Lehman’s 7th Law “The quality of a system will decline unless it is rigorously maintained and adapted to operational environment changes.”'s_laws_of_software_evolution
  25. 25. Feedback System Lehman’s 8th Law “Evolution processes constitute complex feedback systems and must be treated as such to achieve significant improvement over any reasonable base.”'s_laws_of_software_evolution
  26. 26. How can we ever deal with all this change?
  27. 27. Application Lifecycle Management (ALM)
  28. 28. “Application Lifecycle Management (ALM) is a continuous process of managing the life of an application through governance, development and maintenance.” Definition(s) Wikipedia
  29. 29. “ALM is a set of disciplines that together govern the process of turning business ideas into software.” Definition(s) “ALM changing to meet development organizations' needs”
  30. 30. “Any tools, technologies, or techniques that attempt to connect and maintain connections between activities over the life of a piece of software – from the first glint in the glimmer of an executive's eye, through system retirement.” Definition(s) “Just-enough application lifecycle management (ALM)”,294698,sid92_gci1396258,00.html
  31. 31. ALM visualized in models, from bad…
  32. 32.,289142,sid92_gci1259517_mem1,00.html …to absolutely terrible.
  33. 33. “Organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations.” Conway’s Law's_Law
  34. 34. ALM 1.0 Separated disciplines Silos of information Fragile integration
  35. 35. ALM 2.0 Single repository Roles and connections “One truth”
  36. 36.
  37. 37. Complex Systems “A complex system is a system composed of interconnected parts that as a whole exhibit one or more properties (behavior) not obvious from the properties of the individual parts.” Sometimes called the sciences of complexity (plural)
  38. 38. General Systems Theory Autopoiesis (how a system constructs itself) Identity (how a system is identifiable) Homeostatis (how a system remains stable) Permeability (how a system interacts with its environment) Ludwig von Bertalanffy (biologist) 1901-1972 Study of relationships between elements
  39. 39. Cybernetics Goals (the intention of achieving a desired state) Acting (having an effect on the environment) Sensing (checking the response of the environment) Evaluating (comparing current state with system’s goal) Norbert Wiener (mathematician) 1894-1964 Study of regulatory systems
  40. 40. Dynamical Systems Theory Stability (stable states versus unstable states) Attractors (systems getting sucked into stable states) Study of system behavior
  41. 41. Game Theory Competition versus cooperation Zero sum games versus non-zero sum games Strategies (including evolutionary stable strategies) John von Neumann (mathematician) 1903-1957 Study of co-adapting systems
  42. 42. Evolutionary Theory Population (more than one instance) Replication (mechanism of making new instances) Variation (differences between instances) Heredity (differences copied from existing instances) Selection (environment imposes selective pressure) Charles Darwin (naturalist) 1809-1882 Study of evolving systems
  43. 43. Chaos Theory Strange attractors (chaotic behavior) Sensitivity to initial conditions (butterfly effect) Fractals (scale-invariance) Edward Lorenz (meteorologist) 1917-2008 Study of unpredictable systems
  44. 44. And more... Dissipative systems (spontaneous pattern-forming) Cellular automata (complex behavior from simple rules) Genetic algorithms (adaptive learning) Social network analysis (propagation of information) Study of all kinds of systems
  45. 45. The Body of Knowledge of Systems Complex systems theory is the study of complex systems using multiple system theories
  46. 46. Simplicity: A New Model Simple = structure is easily understandable Complicated = structure is very hard to understand Ordered = behavior is fully predictable Complex = behavior is somewhat predictable Chaotic = behavior is very unpredictable Simplification = making something better understandable Linearization = making something more predictable
  47. 47. Structure-Behavior Model Complex and complicated seen as different dimensions
  48. 48. 9 lessons from complexity thinking
  49. 49. Focus on people motivation competence
  50. 50. communication collaboration
  51. 51. Expect change resilience robustness
  52. 52. Support self-organization growth alignment
  53. 53. Embrace emergence no constructionism no predictions
  54. 54. Embrace diversity adaptability innovation
  55. 55. Support decentralization delegation empowerment
  56. 56. unpredictability, unknowns
  57. 57. Heed “incompressibility” All models are wrong, some are useful
  58. 58. People Relationships Change Self-organization Emergence Diversity Decentralization Non-linearity Incompressibility One approach to bind them all…
  59. 59. Agile Software Development
  60. 60. “An iterative and incremental (evolutionary) approach to software development which is performed in a highly collaborative manner by self-organizing teams within an effective governance framework with "just enough" ceremony that produces high quality solutions in a cost effective and timely manner which meets the changing needs of its stakeholders.” Definition Agile Modeling
  61. 61. Let’s start with the good old Iron Triangle
  62. 62. Then add some modifications... Split Cost (Resources) in People and Tools Split Scope in Functionality and Quality (suggestion: Scott Ambler) Add a dimension for Process (suggestion: Alistair Cockburn) Add a dimension for (Business) Value (suggestion: Jim Highsmith)
  63. 63. 1. People 2. Functionality 3. Quality 4. Tools 5. Time 6. Value 7. Process And we get... the 7 dimensions of software projects
  64. 64. People interaction collaborationsmall teams cross-functional colocation self-organization trust accountability respect
  65. 65. Functionality customer involvement backlogs user stories acceptance criteria minimal marketable features user demos “inch-deep, mile-wide”
  66. 66. Quality technical excellence test-driven development pair programming definition of done refactoring emergent design simplicity
  67. 67. Tools daily builds continuous integration automated testing open offices task boards burn charts version control
  68. 68. Time timeboxes iterations sprints potentially shippable products rolling wave planning sustainable pace release planning
  69. 69. Value embracing change feedback frequent delivery value streams value mappingprioritization increments
  70. 70. Process stand-up meetings planning poker velocity spikes collective code ownership retrospectives sprint planning
  71. 71.
  72. 72.
  73. 73.
  74. 74. Agile + ALM similarities information sharing better collaboration increased quality higher productivity
  75. 75. Agile vs. ALM: differences people vs. tools practices vs. techniques
  76. 76. Agile ALM the best of both, using complexity thinking
  77. 77. “The typical project is a collection of ideas held in the minds of the people on the project. […] A project is not the sum of all of its documents or even its code. A great deal of the context of a project lies in its participants.” - Matt Heusser “Just-enough application lifecycle management (ALM)”,294698,sid92_gci1396258,00.html
  78. 78. 7 tips for Agile ALM
  79. 79. ALM tools should support high-bandwidth communication, and should not needlessly replace person-person communication with person-tool communication. Example: facilitation and storage of photos, audio, video. 1. High-Bandwidth Communication
  80. 80. ALM tools must natively support all common Agile practices. Example: user stories, acceptance testing, iterative planning, continuous flow, unit testing, refactoring, automated builds, continuous integration, etc… 2. Agile Best Practices
  81. 81. The ALM infrastructure must be selected, built and maintained by the team(s) themselves. Nothing should be mandated by those who don’t have to work with it. Example: a team can select its own favorite automatic build system or Agile planning tools. 3. Bottom-Up Infrastructure
  82. 82. A healthy ALM strategy will allow for multiple vendors of tools. The benefits of specialization (of tools) often outweighs the cost of integration. There is no “single truth”. Example: use Visual Studio Team System except source control. 4. Multi-Vendor Approach
  83. 83. ALM tools should aim for accessibility. The goal is collaboration, not centralization. Information should be radiated, not concentrated. Example: status updates on whiteboard and in task tracking tool. 5. Distributed Information
  84. 84. Modeling of processes is a form of prediction, and thus unreliable. Allow for emergent design of the ALM infrastructure. Grow it in an Agile way. Example: use a continuous improvement backlog for the ALM infrastructure. 6. Agile Improvement
  85. 85. ALM tools must be extensible, customizable and adaptable, so that they can grow together with the project. Example: open API’s, web services, plug-ins, widgets, macros, etc. 7. Adaptable Tools
  86. 86. Agile ALM High1. -Bandwidth Communication Agile Best Practices2. Bottom3. -up Infrastructure Multi4. -Vendor Approach Distributed Information5. Agile Improvement6. Adaptable Tools7.
  87. 87. Application lifecycle management (Wikipedia) Mea culpa, ALM toolmakers say (SD Times) ALM changing to meet development organizations' needs (SearchSoftwareQuality),289142,sid92_gci1259517_mem1, ml Application Lifecycle Management Gets Agile (ITBusinessEdge) agile/?cs=39865 What is Agile ALM? (Ezine Articles) Agile ALM – Opposites Attract (CM Crossroads) What is the definition of Application Lifecycle Management (ALM)? (IT Knowledge Exchange) lifecycle-management-alm/ Sources
  88. 88. Just-enough application lifecycle management (ALM) (SearchSoftwareQuality),294698,sid92_gci1396258,00.html ALM and Agile (RedMonk) Top 7 Key Requirements of an Agile ALM Platform (Top7Business) Does Application Lifecycle Management (ALM) add Value or Hinder the Adoption of Agile-Lean Product Development? (AgileJournal) management-alm-add-value-or-hinder-the-adoption-of-agile-lean-product-development What exactly is an ALM tool (SearchSoftwareQuality),289625,sid92_gci1523 524,00.html Getting Started with Agile ALM (Manning) Sources
  89. 89.
  90. 90. @jurgenappelo
  91. 91. 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