Reusable StrategyNear identical implementationsSimple to understandWell socializedTalked about a lotEasy to replicate
Sometime elusiveAdoption Rate Vs. Success Rate: 75% of Scrum adoptions have failed.
PhilosophyCommunication“Agile teams cannot exist with occasional communication.”Knowledge ManagementWikis and meetings are job aides; no more, no lessProcessCollocatedDisciplinary self-sustainedStory WritingContinuous IntegrationTest Driven DevelopmentBest PracticesCommunities of Practices (COP)
Corporate policies, e.g. multiple projects or rotation programs Strong identity, e.g. we are a metrics company Command andControl (In nobody we trust) Homework in Iteration Planning – Iteration planning is an activity and not an event Behaviors that block acceptance (e.g. perfectionist)Neuro-linguistic tendencies (e.g. generalizations, etc.)
It all revolves around ‘Communication’ in Agile teams; “Agile teams cannot exist with occasional communication”. This communication is not just human to human but machine to human as well. That’s the motivation behind CI, TDD, and Story Writing.
Behaviors are fairly predictable. It doesn’t help to blame people, RajeevOMG! Did he say “Pathologies”?
Is Agile: The best way to run a project? ORThe way best people choose to run a project?
People are more valuable, butother things are more valuable
ORGANIZATIONStrengths that sometimes become their weaknessesMANAGEMENTLack of courage it often demonstratesTEAMStruggles they constantly have but do very little aboutINDIVIDUALProblems people often don’t know of and ignore
ORGANIZATION• Instant Agile • Corporate Policies and Structures• Strong IdentityMANAGEMENT• Squirrel Agile • Misguided Command and Control• Lack of Team Design • Struggle with New Metrics• Cherry-Pick Agile • Agile without AgilityTEAM• Issues repeat in Retrospectives • Regular Hangovers• Increase Iteration Length • Extending Iterations• Homework in Iteration Planning • Incorrect Accounting of VelocityINDIVIDUALS• Uninterested in ‘Why’ of Agile • Behaviors that Block Acceptance• Estimation Scales • Lone Wolf Syndrome• Neuro-linguistic Tendencies • Broken Window Syndrome
On the Surface Minimal Frequent and Planning Game Daily StandupDocumentation Small Releases In the MiddleCollective Coding Continuous Sustainable AdaptiveOwnership Standards Integration Pace Planning Deep Down Pair TDD Refactoring Simple Design Programming
Process FanaticsUnsatisfied and demotivated people Weak at addressing people issues Is Agile: Best way? OR Best people?