Don't go Agile unless you know why

623 views

Published on

As presented at AgileTour Toronto 2013

Published in: Technology
1 Comment
3 Likes
Statistics
Notes
No Downloads
Views
Total views
623
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
0
Comments
1
Likes
3
Embeds 0
No embeds

No notes for slide

Don't go Agile unless you know why

  1. 1. Don't go Agile ... unless you know why Gino Marckx! Agile Competency Center cba Lodge Pan with Sausage and Potatoes - Joshua Tree, CA by Marshall Astor
  2. 2. 1 Goal © © Google Earth
  3. 3. cbn Raise your hands by Stina Jonsson
  4. 4. 1946 2001 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 Software Engineering That is, while there is value in the items on the right, we value the items on the left more. Kent Beck Mike Beedle Arie van Bennekum Alistair Cockburn Ward Cunningham Martin Fowler James Grenning Jim Highsmith Andrew Hunt Ron Jeffries Jon Kern Brian Marick Robert C. Martin Steve Mellor Ken Schwaber Jeff Sutherland Dave Thomas © 2001, the above authors this declaration may be freely copied in any form, but only in its entirety through this notice. Agile Manufacturing Individual Mastery Team Dynamics Collaboration
  5. 5. “ to satisfy the customer through early and continuous ! delivery of ! valuable software ” First Principle of Manifesto for Agile Software Development - www.agilemanifesto.org
  6. 6. What is the goal of Agile on your team? cbn Group work by Eldan
  7. 7. Debrief cbn Group work by Eldan
  8. 8. 2 Context cb On the Long and Winding Road by Paul Funderburg
  9. 9. Capacity to Change while still delivering…
  10. 10. Requirements Product Vision / Vision Statement Product Backlog User Stories Use Cases Usage Scenarios Personas Planning Poker Requirement Prioritization ! Design Architectural Spikes / Spike Solutions Domain Driven Design Emergent Design / Evolutionary Design CRC Cards Design by Contract System Metaphor ! Construction Coding Style / Coding Guidelines / Coding Standard Test Driven Development Behavior Driven Development Pair-Programming / Pairing Refactoring Collective Code Ownership Daily Builds / Automated Builds / Ten-Minute Builds Continuous Integration Code Reviews / Peer Reviews Software Metrics / Code Metrics & Analysis Source Control / Version Control Issue Tracking / Bug Tracking Configuration Management Frequent Delivery / Frequent Releases ! ! ! Jurgen Appelo - http://www.noop.nl/2009/04/the-big-list-of-agile-practices.html Testing Unit Testing Smoke Testing / Build Verification Test Integration Testing System Testing Exploratory Testing Test Automation Storytesting / Acceptance Criteria / Acceptance Testing ! Process Timeboxing / Fixed Sprints / Fixed Iteration Length Release Planning Iteration Planning / Planning Game / Sprint Planning Sprint Backlog Task Board Definition of Done / Done Done Daily Stand-up Meeting / Daily Scrum Velocity Sprint Review / Iteration Demo Value Stream Mapping Root Cause Analysis / 5 Whys Burn Down Charts / Burn Up Charts Big Visible Charts / Information Radiators Retrospective / Reflection Workshop ! Organization Small Team Cross-Functional Team Self-Organizing Team / Scrum Team Colocated Team / Sitting Together / Common Workspace On-Site Customer / Product Owner Scrum Master Sustainable Pace Move People Around Scrum of Scrums
  11. 11. Test Driven Development + Increases test coverage! Prevents regression bugs! Finds errors sooner - Depends on other practices! Need highly testable code base! Requires automated testing expertise! Disciplined practices across team members Increase Quality
  12. 12. Which practices help achieve that goal?! What are the challenges? cbn Group work by Eldan
  13. 13. Debrief cbn Group work by Eldan
  14. 14. 3 Feedback cb City of Baltimore Topographical Survey, c. 1894 by Matthew Petroff
  15. 15. What problem are we trying to solve?! How can we use the technology to solve that problem?! How will users respond to our solution?! What will the solution be?
  16. 16. Cynefin Effect < Cause Complex Chaos Effect ? Cause Cause >> Effect Complicated Simple Cause > Effect
  17. 17. “ Design as a knowledge acquisition framework ” Alistair Cockburn
  18. 18. How will we introduce practices to get most feedback? cbn Group work by Eldan
  19. 19. Debrief cbn Group work by Eldan
  20. 20. • Always 1 constraint! • End to end throughput! • Continuous Improvement
  21. 21. Goal © © Google Earth Context cb On the Long and Winding Road by Paul Funderburg Feedback cb City of Baltimore Topographical Survey, c. 1894 by Matthew Petroff
  22. 22. Thank you! Gino Marckx! Agile Competency Centre cba Lodge Pan with Sausage and Potatoes - Joshua Tree, CA by Marshall Astor

×