Tabular Explanation of Being Agile

Simply put, many often believe that if they are performing the “practices or techniques” they are agile.  They are “doing” (column 3) agile.  However, (for debate/discussion), any activities or techniques employed to enable the practice of agile principles (column 2) demonstrate “being agile”.

Lean principlesAgile principles - "Being" AgileAgile practices and/or techniques - "Doing" AgileAgile Architecture (SAFe)Product development flow principles
- Eliminate waste- Close, daily co-operation between business people and developers
- Face-to-face conversation is the best form of communication (co-location)
- Simplicity
- Daily stand-up 15 min mtg (Scrum)
- Co-location
- Visual mgt (Information radiators)
- Build the simplest architecture that can possibly work- Take and economic view
- Amplify learning- Regular adaptation to changing circumstances- Demos- When in doubt, code, or model it out- Get feedback as fast as possible
- Decide as late as possible- Welcome changing requirements, even late in development- Prototyping with planned refactoring to standards
- Deliver as fast as possible- Customer satisfaction by rapid delivery of useful software
- Working software is delivered frequently (weeks rather than months)
Sustainable development, able to maintain a constant pace (cadence)
- Sprints (iterations) and releases
- Kanban "flow" mgt with WIP limits
- Actively manage queues
- Reduce batch sizes
- Empower the team- Projects are built around motivated individuals, who should be trusted
- Self-organizing teams
- Self directed teams accountable for outcomes
- Retrospectives
- There is no monopoly on innovation- Decentralize control
- Build integrity in- Continuous attention to technical excellence and good design- User acceptance driven development
- Test driven development
- Architecture engagement
- They build it, they test it
- Design emerges
- Architecture is a collaboration
- Apply WIP constraints
- See the whole- Working software is the principal measure of progress- Portfolio (epics) --> Program (features) --> Sprints or iterations (stories)
- TCO lens applied to scope (definition of "done")
- Sustainable support incorporated into planning
- The bigger the system, the longer the runway
- Implement architectural flow
- Control flow under uncertainty: Cadence and synchronization
- Understand and exploit varaibility


Leave a Reply

Your email address will not be published. Required fields are marked *