Adopt Before You Adapt: Learning Principles through Practice


Published on

Although agile principles sound simple, adopting agile is often extremely difficult. Some teams adopting agile start by making changes and tweaks to prescribed processes—bad! Steve Berczuk explains how following the recommended practices of your chosen agile method for a time will help you internalize the process and leverage the experiences of those who developed the method. Through experience, Steve has discovered that premature customization can lead to more problems and eventually to failure. After discussing the common reasons teams customize methods and tools prematurely and the problems this can cause, he offers guidance about how and when to change an agile process and explains which practices are essential to retain the values and principles that make agile development what it is meant to be. Take back a new appreciation of how following proven agile practices before you adapt them leads to the profound understanding and internalization of the principles that agile requires.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Adopt Before You Adapt: Learning Principles through Practice

  1. 1. AW7 Concurrent Session 11/13/2013 2:15 PM "Adopt Before You Adapt: Learning Principles through Practice" Presented by: Steve Berczuk Fitbit, Inc. Brought to you by: 340 Corporate Way, Suite 300, Orange Park, FL 32073 888 268 8770 904 278 0524
  2. 2. Steve Berczuk Fitbit, Inc. Steve Berczuk is an agile software developer and agile SCM expert with more than twenty-five years of experience building systems and helping teams work together effectively. Most of his experience has been working in startup environments, including many teams trying to adopt Scrum and agile engineering techniques. Steve is coauthor of Software Configuration Management Patterns: Effective Teamwork, Practical Integration; a regular contributor to; and a member of the Scrum Alliance, IEEE, and ACM. Find his articles and blog at and follow him on Twitter @sberczuk.
  3. 3. Adopt Before You Adapt: ! Learning Principles through Practice! Steve Berczuk! Fitbit, Inc. Agile is Simple... Plan Execute Review Adapt © 2013 Steve Berczuk
  4. 4. ... Similar to Waterfall ... Requirements Design Implementation Verification Maintenance © 2013 Steve Berczuk ... But for the Details Integrate Test Limit WIP "Done" Daily Standup Roadblocks Execute Plan Product Owner Planning Meetings Prioritization Definition of Done Limit Changes Review Mtg Retrospective Feedback Review Change Adapt © 2013 Steve Berczuk
  5. 5. “Agile” and Agile © 2013 Steve Berczuk The Agile Manifesto • • • • Individuals and interactions over processes and tools! Working software over comprehensive documentation! Customer collaboration over contract negotiation! Responding to change over following a plan © 2013 Steve Berczuk
  6. 6. Simple Rules • Structure! • Tool for Change! • Discipline © 2013 Steve Berczuk Collaboration • Cross Functional! • Shared Ownership! • Trust © 2013 Steve Berczuk
  7. 7. Feedback © 2013 Steve Berczuk Goal © 2013 Steve Berczuk
  8. 8. Risk Management “How does a project get to be a year late? ... One day at a time.”
 p153 1975 © 2013 Steve Berczuk Waterfall and Risk © 2013 Steve Berczuk
  9. 9. Agile Risk Management © 2013 Steve Berczuk Impediments • Knowledge! • Resources! • Organizational Culture! • Comfort © 2013 Steve Berczuk
  10. 10. The Problem © 2013 Steve Berczuk The Other Problem © 2013 Steve Berczuk
  11. 11. Data! Observe, Adjust © 2013 Steve Berczuk Practices © 2013 Steve Berczuk Learning Values
  12. 12. Practice and Values © 2013 Steve Berczuk Why do you want to adopt agile? “To Be Agile” © 2013 Steve Berczuk To Deliver Value
  13. 13. Not Everyone Needs To Be Agile © 2013 Steve Berczuk Change is Hard © 2013 Steve Berczuk
  14. 14. Resisting Change • The Unknown! • Failure! • “Survival” Rules © 2013 Steve Berczuk “Survival rules are not stupid; they are simply over-generalizations of rules we once needed for survival. We don’t want to simply throw them away…” Jerry Weinberg © 2013 Steve Berczuk
  15. 15. “…Survival rules can be transformed into less powerful forms, so that we can still use their wisdom without becoming incongruent.” Jerry Weinberg © 2013 Steve Berczuk Performance Satir Change Model Late Status Quo Chaos Integration and Practice Time Foreign Element © 2013 Steve Berczuk New Status Quo
  16. 16. Scrum Overview Product Backlog Increment Product Owner Sprint Planning Scrum Master Sprint Backlog Process Improvements Dev Team Daily Scrum Daily Scrum Sprint Review Daily Scrum Daily Scrum Retrospective The Sprint © 2013 Steve Berczuk Scrum Engineering Continuous Integration ? TDD Code Test Daily Scrum Commit Daily Scrum Build Integrate Sprint Review Daily Scrum Daily Scrum Retrospective The Sprint XP © 2013 Steve Berczuk Automation
  17. 17. Effects © 2013 Steve Berczuk Diagram of Effects Measurable Quantity Direct Relationship Measurable Quantity 3 Inverse Relationship Measurable Quantity 2 © 2013 Steve Berczuk
  18. 18. Diagram of Effects Steps Progress towards Goal Nagging from Friends © 2013 Steve Berczuk Scrum Processes Team Estimation Accuracy Achievability of Sprint Goal Modular Code Retrospective Feedback Refactoring Ability Working Code Unit Testing Continuous Integration Review Feedback Review Meeting Retrospective Meeting Trust © 2013 Steve Berczuk
  19. 19. Cascade Effects Team Estimation Accuracy X Achievability of Sprint Goal Working Code Modular Code X Retrospective Feedback Unit Testing Continuous Integration Refactoring Ability Review Feedback X Review Meeting Retrospective Meeting Trust © 2013 Steve Berczuk Cascade Effects Achievability of Sprint Goal X Modular Code Working Code X Unit Testing X X X X Refactoring Ability © 2013 Steve Berczuk Continuous Integration
  20. 20. Don’t Not Adapt © 2013 Steve Berczuk Adapt (What) • Estimation and Planning! • Engineering Execution! • Task Flow/Assignment! • Feedback (Review and Retrospective) © 2013 Steve Berczuk
  21. 21. Adapt (When & How) • After Retrospective / Gather Data © 2013 Steve Berczuk Don’t Call It Agile if it is Not! © 2013 Steve Berczuk
  22. 22. Trust © 2013 Steve Berczuk Recap • Practice and Learn! • Review and Retrospect! • Adapt, Measure, and Adapt! • Be Willing to Fail © 2013 Steve Berczuk
  23. 23. My Book © 2013 Steve Berczuk Contact Me email:! twitter: @sberczuk! ADN: @spb! LinkedIn:!! ! © 2013 Steve Berczuk
  24. 24. © 2013 Steve Berczuk