Agile: from Principles to Practice

An overview of the 12 Agile Principles and a variety of practices that map to those principles.

Transcript

1. Nayan Hajratwala : @nhajratw nayan@chikli.com agileshrugged.com KCPCSPCSDCSMCJP
4. A Bit of History
7. “I believe in this concept, but the implementation described above is risky and invites failure.”
8. “I believe in this concept, but the implementation described above is risky and invites failure.” STEP 5: INVOLVE THE CUSTOMER! For some reason what a software design is going to do is subject to wide interpretation even after previous agreement.
10. Feature Driven Development Scrum Extreme Programming Crystal Rational Unified Process Pragmatic Programming DSDM
12. Agile Manifesto We are uncovering better ways of developing
 software by doing it and helping others do it.
 Through this work we have come to value: Individuals and interactions over processes and tools
 Working software over comprehensive documentation
 Customer collaboration over contract negotiation
 Responding to change over following a plan That is, while there is value in the items on
 the right, we value the items on the left more.
15. Kanban Method Principles • Start with what you do now • Agree to pursue incremental, evolutionary change • Respect the current process, roles, responsibilities and titles • Leadership at all levels
16. Kanban Core Practices • Visualize • Limit WIP • Manage flow • Make policies explicit • Implement feedback loops • Improve collaboratively, evolve experimentally
17. Agile Manifesto We are uncovering better ways of developing
 software by doing it and helping others do it.
 Through this work we have come to value: Individuals and interactions over processes and tools
 Working software over comprehensive documentation
 Customer collaboration over contract negotiation
 Responding to change over following a plan That is, while there is value in the items on
 the right, we value the items on the left more.
18. The Agile Manifesto also has 12 Principles
20. The Agile Manifesto also has 12 Principles
21. Our highest priority is to satisfy the customer
 through early and continuous delivery
 of valuable software. 1
22. Our highest priority is to satisfy the customer
 through early and continuous delivery
 of valuable software. 1
23. Our highest priority is to satisfy the customer
 through early and continuous delivery
 of valuable software. 1 • Facebook - once / day
24. Our highest priority is to satisfy the customer
 through early and continuous delivery
 of valuable software. 1 • Facebook - once / day • IMVU - 50 / day
25. Our highest priority is to satisfy the customer
 through early and continuous delivery
 of valuable software. 1 • Facebook - once / day • IMVU - 50 / day • Github 100 / day
26. Our highest priority is to satisfy the customer
 through early and continuous delivery
 of valuable software. 1 • Facebook - once / day • IMVU - 50 / day • Github 100 / day • Netflix - 100s / day
28. Source Control
29. Build Artifacts + Isolation Tests (xUnit) Source Control
30. Build Artifacts + Isolation Tests (xUnit) Automated Acceptance Tests! (Cucumber, Selenium) Source Control
31. Build Artifacts + Isolation Tests (xUnit) Automated Acceptance Tests! (Cucumber, Selenium) Source Control Build Environment! (Chef, Puppet)
32. Build Artifacts + Isolation Tests (xUnit) Automated Acceptance Tests! (Cucumber, Selenium) Deploy A/B Source Control Build Environment! (Chef, Puppet)
33. Build Artifacts + Isolation Tests (xUnit) Automated Acceptance Tests! (Cucumber, Selenium) Deploy A/B Smoke Test Source Control Build Environment! (Chef, Puppet)
34. Build Artifacts + Isolation Tests (xUnit) Automated Acceptance Tests! (Cucumber, Selenium) Deploy A/B Smoke Test Source Control Production Build Environment! (Chef, Puppet)
35. Welcome changing requirements, even late in 
 development. Agile processes harness change for 
 the customer's competitive advantage. 2
38. Simplicity--the art of maximizing the amount 
 of work not done--is essential. 3
39. Simplicity--the art of maximizing the amount 
 of work not done--is essential. 3
40. 4 Rules of Simple Design 1. Runs all the Tests 2. Contains No duplication (DRY) 3. Expresses all ideas you want to express 4. Minimize classes and methods.
41. Business people and developers must work 
 together daily throughout the project. 4
45. Cucumber - Gherkin Syntax Scenario: Creditor Agencies must have a unique AgencyID Given a creditor agency exists When I add another creditor agency with the same agency id Then there should only be one creditor agency
46. Cucumber - Gherkin Syntax Scenario Outline: Determine Payee Count when an offset is taken ! Given a Payment Record containing a <payee> Payee TIN And a Payment Record containing a <secondary> Secondary TIN When an offset occurs Then the Payee Count should be <count> Examples: |payee |secondary|count| |valid | valid | 2 | |valid | blank | 1 | |valid | zeroes | 1 | |valid | invalid | 2 | |blank | valid | 1 | |zeroes | valid | 1 | |invalid| valid | 2 |
48. Build projects around motivated individuals. 
 Give them the environment and support they need, 
 and trust them to get the job done. 5
51. The most efficient and effective method of 
 conveying information to and within a development 
 team is face-to-face conversation. 6
55. Working software is the primary measure of progress. 7
56. Value Stream Mapping
57. Value Stream Mapping Customer Request Production
58. Value Stream Mapping Approval Prioritization Build Security Review Deployment Customer Request Production
59. Value Stream Mapping Approval Prioritization Build Security Review Deployment Customer Request Production 4 hrs 2 hrs 80 hrs 4 hrs 1 hr
60. Value Stream Mapping Approval Prioritization Build Security Review Deployment Customer Request Production 4 hrs 2 hrs 80 hrs 4 hrs 1 hr 91 hrs
61. Value Stream Mapping Approval Prioritization Build Security Review Deployment Customer Request Production 4 hrs 2 hrs 80 hrs 4 hrs 1 hr 1 week .5 week 2 weeks 1 week 1 day 91 hrs
62. Value Stream Mapping Approval Prioritization Build Security Review Deployment Customer Request Production 4 hrs 2 hrs 80 hrs 4 hrs 1 hr 1 week .5 week 2 weeks 1 week 1 day 91 hrs + 188 hrs
63. Value Stream Mapping Approval Prioritization Build Security Review Deployment Customer Request Production 1 week 4 hrs 2 hrs 80 hrs 4 hrs 1 hr 1 week .5 week 2 weeks 1 week 1 day 91 hrs + 188 hrs
64. Value Stream Mapping Approval Prioritization Build Security Review Deployment Customer Request Production 1 week 8 weeks 4 hrs 2 hrs 80 hrs 4 hrs 1 hr 1 week .5 week 2 weeks 1 week 1 day 91 hrs + 188 hrs
65. Value Stream Mapping Approval Prioritization Build Security Review Deployment Customer Request Production 1 week 8 weeks 2 weeks 4 hrs 2 hrs 80 hrs 4 hrs 1 hr 1 week .5 week 2 weeks 1 week 1 day 91 hrs + 188 hrs
66. Value Stream Mapping Approval Prioritization Build Security Review Deployment Customer Request Production 1 week 8 weeks 2 weeks 10 weeks 4 hrs 2 hrs 80 hrs 4 hrs 1 hr 1 week .5 week 2 weeks 1 week 1 day 91 hrs + 188 hrs
67. Value Stream Mapping Approval Prioritization Build Security Review Deployment Customer Request Production 1 week 8 weeks 2 weeks 10 weeks 1 week 4 hrs 2 hrs 80 hrs 4 hrs 1 hr 1 week .5 week 2 weeks 1 week 1 day 91 hrs + 188 hrs
68. Value Stream Mapping Approval Prioritization Build Security Review Deployment Customer Request Production 1 week 8 weeks 2 weeks 10 weeks 1 week 4 hrs 2 hrs 80 hrs 4 hrs 1 hr 1 week .5 week 2 weeks 1 week 1 day 91 hrs + 188 hrs
69. Value Stream Mapping Approval Prioritization Build Security Review Deployment Customer Request Production 1 week 8 weeks 2 weeks 10 weeks 1 week 4 hrs 2 hrs 80 hrs 4 hrs 1 hr 1 week .5 week 2 weeks 1 week 1 day 91 hrs + 188 hrs 880 hrs
70. Value Stream Mapping Approval Prioritization Build Security Review Deployment Customer Request Production 1 week 8 weeks 2 weeks 10 weeks 1 week 4 hrs 2 hrs 80 hrs 4 hrs 1 hr 1 week .5 week 2 weeks 1 week 1 day 91 hrs + 188 hrs 880 hrs 1068 hrs
71. Value Stream Mapping Approval Prioritization Build Security Review Deployment Customer Request Production 1 week 8 weeks 2 weeks 10 weeks 1 week 4 hrs 2 hrs 80 hrs 4 hrs 1 hr 1 week .5 week 2 weeks 1 week 1 day 91 hrs + 188 hrs 880 hrs 1068 hrs 91 hours of value added time 1068 hrs of cycle time = 8.5% Process Efficiency
72. Value Stream Mapping Approval Prioritization Build Security Review Deployment Customer Request Production 1 week 8 weeks 2 weeks 10 weeks 1 week 4 hrs 2 hrs 80 hrs 4 hrs 1 hr 1 week .5 week 2 weeks 1 week 1 day 91 hrs + 188 hrs 880 hrs What should have taken just over 2 weeks, takes 26! 1068 hrs 91 hours of value added time 1068 hrs of cycle time = 8.5% Process Efficiency
73. Deliver working software frequently, from a 
 couple of weeks to a couple of months, with a 
 preference to the shorter timescale. 8
74. Deliver working software frequently, from a 
 couple of weeks to a couple of months, with a 
 preference to the shorter timescale. 8 • Teams doing Scrum typically have Sprints of 2 weeks or less.
75. Deliver working software frequently, from a 
 couple of weeks to a couple of months, with a 
 preference to the shorter timescale. 8 • Teams doing Scrum typically have Sprints of 2 weeks or less. • Frequently, teams are moving to Flow- based methods such as Kanban
76. Little’s Law
77. Cycle Time = WIP Throughput Little’s Law
78. • Cycle Time = Time between any two points in a process. (i.e. 10 days) Cycle Time = WIP Throughput Little’s Law
79. • Cycle Time = Time between any two points in a process. (i.e. 10 days) • Throughput = Number of work items completed in a specified period. (5 stories / week) Cycle Time = WIP Throughput Little’s Law
80. • Cycle Time = Time between any two points in a process. (i.e. 10 days) • Throughput = Number of work items completed in a specified period. (5 stories / week) • Work in Process (WIP) = Number of work items currently underway. Cycle Time = WIP Throughput Little’s Law
81. Agile processes promote sustainable development. 
 The sponsors, developers, and users should be able 
 to maintain a constant pace indefinitely. 9
83. Time In Process 0 75 150 225 300 Utilization 10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
84. Time In Process 0 75 150 225 300 Utilization 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% :-|
85. Time In Process 0 75 150 225 300 Utilization 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% :-| :-)
86. Time In Process 0 75 150 225 300 Utilization 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% :-| :-) :-D
87. Time In Process 0 75 150 225 300 Utilization 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% :-| :-) :-D :-(
88. Continuous attention to technical excellence 
 and good design enhances agility. 10
89. The best architectures, requirements, and designs 
 emerge from self-organizing teams. 11
90. The best architectures, requirements, and designs 
 emerge from self-organizing teams. • Ivory Tower Architecture no longer has a place. 11
91. At regular intervals, the team reflects on how 
 to become more effective, then tunes and adjusts 
 its behavior accordingly. 12
92. At regular intervals, the team reflects on how 
 to become more effective, then tunes and adjusts 
 its behavior accordingly. 12 Loved Learned Longed For
93. Agile Manifesto We are uncovering better ways of developing
 software by doing it and helping others do it.
 Through this work we have come to value: Individuals and interactions over processes and tools
 Working software over comprehensive documentation
 Customer collaboration over contract negotiation
 Responding to change over following a plan That is, while there is value in the items on
 the right, we value the items on the left more.
94. Image Credits • Waterfall - http://www.noupe.com/wp-content/uploads/2010/04/Waterfall2.jpg • Evolution - http://cyemae.files.wordpress.com/2010/01/evolution-of-man.png • Healthcare - http://healthcare.gov • Snowbird - http://freeskiing-world-tour-fwt.rmvn.stackablehost.com/wp-content/uploads/ 2011/12/trailmap_snowbird.jpg • Toyota Plant - http://www.thedetroitbureau.com/wp-content/uploads/2011/04/Toyota-Prius- Plant.jpg • Cargo Cult - http://stmatts5pm.files.wordpress.com/2010/07/cargo-cult.jpg • Traffic Jam - http://l.yimg.com/os/924/2012/12/04/paris-lyon-traffic-jam-1980-jpg_133914.jpg • Standup - http://coremediaminds.files.wordpress.com/2012/06/standup-modell1.jpg • Muppet Pairing - http://changearc.files.wordpress.com/2012/09/ muppetspairprogramming.jpg • Panda - http://diasjorge.github.io/pair-programming-slides/img/panda.jpg
95. Nayan Hajratwala : @nhajratw nayan@chikli.com agileshrugged.com KCPCSPCSDCSMCJP