Agile Development How it Works Damon Poole Damon

  • Slides: 34
Download presentation
Agile Development: How it Works Damon Poole

Agile Development: How it Works Damon Poole

Damon Poole q Founder/CTO of Accu. Rev, the leader in Agile SCM. q Focused

Damon Poole q Founder/CTO of Accu. Rev, the leader in Agile SCM. q Focused on methodology for 17 years q Designer/architect of award-winning software q Creator of Hyper Agile methodology q Most recent product, Accu. Workflow, developed using Hyper Agile q Author of various articles on Agile development Proprietary and Confidential 2/29 21: 43

Problems with Traditional Development q Poor usability q Slow to respond to customer/market demand

Problems with Traditional Development q Poor usability q Slow to respond to customer/market demand q Extremely difficult to accurately predict q Questionable quality q Lots of inefficiencies from rework and cancelled or shelved work q Hard to see the root cause of problems q “This time we’ll do it right!” q Burnout, job dissatisfaction Proprietary and Confidential 3/29 21: 43

Problems with Agile Development q Exact benefits are often poorly articulated q The exact

Problems with Agile Development q Exact benefits are often poorly articulated q The exact relationships between specific practices and specific benefits are poorly articulated q The perception that: m it scales poorly/it is only for small teams m you need to use 3 x 5 cards, collocation, and pair programming m it requires generalists m it requires a team of all senior engineers q Confusion about what exactly to do (“Agile isn’t a methodology, it is a set of principles”) Proprietary and Confidential 4/29 21: 43

Requirements for Mainstream Agile q Clear benefits q Uses existing team members q Independent

Requirements for Mainstream Agile q Clear benefits q Uses existing team members q Independent of application domain q Can be adopted piecemeal q Straightforward implementation q Scaleable q Appropriate for distributed development q How and why it works is obvious to everyone involved Proprietary and Confidential 5/29 21: 43

The Core: How it Works Proprietary and Confidential 6/29 21: 43

The Core: How it Works Proprietary and Confidential 6/29 21: 43

Primary vs Secondary Benefits People Higher Quality Faster ROI More Flexibility Agile Secondary Benefits

Primary vs Secondary Benefits People Higher Quality Faster ROI More Flexibility Agile Secondary Benefits Other People Traditional Same as last release Other Proprietary and Confidential 7/29 21: 43

Primary vs Secondary Benefits People Short Iterations TDD 3 x 5 Cards Refactoring Continuous

Primary vs Secondary Benefits People Short Iterations TDD 3 x 5 Cards Refactoring Continuous Int Higher Quality Faster ROI More Flexibility Secondary Benefits Other People Long Iterations Same as last release Other Proprietary and Confidential 8/29 21: 43

Primary vs Secondary Benefits People Short Iterations TDD 3 x 5 Cards Refactoring Continuous

Primary vs Secondary Benefits People Short Iterations TDD 3 x 5 Cards Refactoring Continuous Int Higher Quality Faster ROI More Flexibility Secondary Benefits Other People Long Iterations TDD Refactoring Continuous Int Same as last release Secondary Benefits Other Proprietary and Confidential 9/29 21: 43

Primary vs Secondary Benefits People Short Iterations TDD 3 x 5 Cards Refactoring Continuous

Primary vs Secondary Benefits People Short Iterations TDD 3 x 5 Cards Refactoring Continuous Int Higher Quality Faster ROI More Flexibility Secondary Benefits Other People Short Iterations TDD Refactoring Continuous Int Higher Quality Faster ROI More Flexibility Secondary Benefits Other Proprietary and Confidential 10/29 21: 43

More ROI… Faster Features by ROI Traditional $$ plan Agile $ $$ Proprietary and

More ROI… Faster Features by ROI Traditional $$ plan Agile $ $$ Proprietary and Confidential $$$ 11/29 21: 43

Rescheduling Effort Traditional Testing bottleneck Deliver to customer prepare code write tests test debug

Rescheduling Effort Traditional Testing bottleneck Deliver to customer prepare code write tests test debug final qualification testing Agile (optional) Proprietary and Confidential 12/29 21: 43

Complexity n=4 O(n 2) ~16 potential entanglements Traditional 60 3, 600 Agile 10 10

Complexity n=4 O(n 2) ~16 potential entanglements Traditional 60 3, 600 Agile 10 10 10 60 100 100 100 600 Proprietary and Confidential 13/29 21: 43

One Piece Flow Potential work items Existing Incoming Business value and ROI calculator Requirements

One Piece Flow Potential work items Existing Incoming Business value and ROI calculator Requirements Design Write all tests Code Unit Test Demo Integrate System Test Deliverable Proprietary and Confidential 14/29 21: 43

Better Framework Traditional Agile m problems (waste) are immediately apparent m the success/failure of

Better Framework Traditional Agile m problems (waste) are immediately apparent m the success/failure of corrective actions are immediately apparent m good behavior is encouraged and bad behavior is discouraged m existing management skills are much better leveraged Proprietary and Confidential 15/29 21: 43

Enabling Practices Proprietary and Confidential 16/29 21: 43

Enabling Practices Proprietary and Confidential 16/29 21: 43

Recommended Enabling Practices q Chunking/Multiple Parallel Iterations q Development Hierarchy q Quality quotient q

Recommended Enabling Practices q Chunking/Multiple Parallel Iterations q Development Hierarchy q Quality quotient q Test Driven Development q Continuous Integration q Refactoring q Component based development Proprietary and Confidential 17/29 21: 43

Other Common Agile Practices q Stand up meetings q Pair programming q Co-location q

Other Common Agile Practices q Stand up meetings q Pair programming q Co-location q Self-managing teams q Customer on-site q Shared code ownership q Stacking teams with senior developers q 3 x 5 cards (!? ) Proprietary and Confidential 18/29 21: 43

Coding Bucket Sizes: Before coding 1 day 2 days 1 week 2 weeks Proprietary

Coding Bucket Sizes: Before coding 1 day 2 days 1 week 2 weeks Proprietary and Confidential 1 month > 1 month 19/29 21: 43

Coding Bucket Sizes: After 1 day 2 days 1 week 2 weeks Proprietary and

Coding Bucket Sizes: After 1 day 2 days 1 week 2 weeks Proprietary and Confidential 1 month > 1 month 20/29 21: 43

Parallel Iterations Exceptions Majority of work 1 2 3 4 Months Proprietary and Confidential

Parallel Iterations Exceptions Majority of work 1 2 3 4 Months Proprietary and Confidential 21/29 21: 43

Everyone interdependent via mainline Proprietary and Confidential 22/29 21: 43

Everyone interdependent via mainline Proprietary and Confidential 22/29 21: 43

Developer Changes vs. Check-ins Proprietary and Confidential 23/29 21: 43

Developer Changes vs. Check-ins Proprietary and Confidential 23/29 21: 43

Development Hierarchy Stability/Maturity Devs Teams q Integration QA Always shippable Proprietary and Confidential Other

Development Hierarchy Stability/Maturity Devs Teams q Integration QA Always shippable Proprietary and Confidential Other potential elements m Major features m Smoke test passed m Needs tests m Continuous Integration passed m Code review m Demo m Ready for QA 24/29 21: 43

One Piece Flow Devs Teams Integration QA Always shippable Proprietary and Confidential 25/29 21:

One Piece Flow Devs Teams Integration QA Always shippable Proprietary and Confidential 25/29 21: 43

Getting Started with Agile Proprietary and Confidential 26/29 21: 43

Getting Started with Agile Proprietary and Confidential 26/29 21: 43

Resources q http: //damonpoole. blogspot. com q http: //agilealliance. com q Agile Software Development

Resources q http: //damonpoole. blogspot. com q http: //agilealliance. com q Agile Software Development with Scrum, Ken Schwaber & Mike Beedle q Extreme Programming Explained - 2 nd Edition, Kent Beck q Lean Software Development, Mary Poppendieck and Tom Poppendieck q “How Agile Works”, Free 1 -hour on-site seminar, Damon Poole Proprietary and Confidential 27/29 21: 43

Agile POC Program q Try Agile in your organization for 6 months q You

Agile POC Program q Try Agile in your organization for 6 months q You supply the people and the project q Accu. Rev supplies: m Complete Agile tool stack with installation and training m Agile coach Proprietary and Confidential 28/29 21: 43

Contact info Damon Poole Accu. Rev damon@accurev. com http: //damonpoole. blogspot. com Proprietary and

Contact info Damon Poole Accu. Rev [email protected] com http: //damonpoole. blogspot. com Proprietary and Confidential 29/29 21: 43

End Proprietary and Confidential 30/29 21: 43

End Proprietary and Confidential 30/29 21: 43

Accu. Rev’s Support for Agile q Development hierarchy m Private branches m Parallel iterations

Accu. Rev’s Support for Agile q Development hierarchy m Private branches m Parallel iterations m Drag and drop issues anywhere in hierarchy m Drag and drop process changes q Leading edge refactoring support q Performance via WAN removes integration delays q Integration with Cruise Control, Anthill, etc. q Integrated with the 8 leading issue tracking systems and also built-in issue tracking Proprietary and Confidential 31/29 21: 43

Accu. Rev: Best-of-Breed Agile Dev Tool q Fastest growing SCM company in the world

Accu. Rev: Best-of-Breed Agile Dev Tool q Fastest growing SCM company in the world q Only SCM product to win 2 Jolt Product Excellence awards q Committed to Agile Development “As a result of merger and acquisition activity, a move toward more Agile processes and offshore development, Accu. Rev was the optimal solution to manage this increasingly parallel development model efficiently. ” Rick Hoff, CTO, Tyler Technologies Proprietary and Confidential 32/29 21: 43

Some of our 400+ customers Proprietary and Confidential 33/29 21: 43

Some of our 400+ customers Proprietary and Confidential 33/29 21: 43

Accu. Rev for Agile Proprietary and Confidential 34/29 21: 43

Accu. Rev for Agile Proprietary and Confidential 34/29 21: 43