Agile Anti-Pattern=> Final wrap up
The most popular Agile Antipatterns conversations of the last 5 months were about:
- Agile Theatre
- Agile Transformations
- Agile Playbook
- Agile Maturity Models
While other Agile Antipatterns are still found very very frequently in many orgs.
So far all of them seem fit into one of the 7 categories listed in the image below. Or there is more?
Agile Anti-Pattern => Agile Imposition
It is when the adoption and practice of Agile are prescribed in a top-down way. What is your experience with Agile Imposition?
See an Agile alternative, Invitation over Imposition: http://p2.fed.wiki/view/welcome-visitors/view/invitation-over-imposition
With Invitation instead one can be Agile in adopting Agile, and Invitation becomes necessary when dealing with novelty, unknowns, uncertainty, and unforeseen change.
Agile Anti-Pattern => Traditional Roadmaps
Traditional Roadmaps are typically created by applying the iron triangle with a predictive approach. The efforts to minimise the friction between fixed commitments and evolving circumstances are typically inadequate.
See an Agile alternative: http://p2.fed.wiki/view/welcome-visitors/view/options-over-roadmap
What's your experience?
Thanks for the inputs from @mostalive Marc Evers and Rob Westgeest at QWAN
#AgileAntipatterns #Agile #Roadmap #IronTriangle #ProjectFunding #ResourceEfficiency
Agile Anti-Pattern => North Star
A North Star often intended as fixed reference point to navigate toward a desired destination set before the journey begins.
Not for exploring uncharted territories.
See the alternative: http://p2.fed.wiki/view/welcome-visitors/view/flashlight-over-north-star
<<Whatever inspiration is, it's born from a continuous I don't know>> Wisława Szymborska
What's your experience within Agile using a North Star? Did it help when dealing with novelty, unknowns and uncertainties?
Agile Anti-Pattern => Agile Maturity Models
There are many things wrong with Agile Maturity Models, they are all explained here with the better alternative, namely Agile self-assessments, with the key differences explained: http://p2.fed.wiki/view/welcome-visitors/view/self-assessment-over-maturity-model
With more content from @johncutlefish - Barry O'Reilly - Chris McDermott
Agile Anti-Pattern=>Agile Playbook
The alternative to this anti-pattern described here promotes contributions & continuous updates: http://p2.fed.wiki/view/welcome-visitors/view/wiki-over-playbook
Does your company have an Agile Playbook? How often is it updated? Who contributes to the content?
How do you feel about its readers-authors separation, "best" practice thinking and its unilateral views?
UPDATED to list other wiki-like forms of living documentation
#Agile #AgileAntipatterns #Playbook #AgilePlaybook #Unilateralism #Wiki
I'm going to steal this sentence and use it the next time management jumps on the cargo cult plane: "This is a level one service desk. We just answer phones."
https://teddit.hostux.net/r/sysadmin/comments/11asl50/agile_scrums_for_f_sake/j9utf2t/
UPDATE: I have updated the CoE anti-pattern page here => http://p2.fed.wiki/view/welcome-visitors/view/decentralised-excellence-over-centre-of-excellence by
1) linking and highlighting the articles from Sriram Narayan, Anthony Mersino + Thomas Cagley and Ove Herbert Holmberg.
2) including in the CoE anti-pattern page comments about CoEs that really are something else, thanks to the insights from Chris Combe.
Centralisation, Imposition, Imitation, Standardisation, Planification, Commoditization, Pretending
The 7 mistakes of bad Agile adoptions & transformations
Posting under #AgileAntipatterns
Agile Anti-Pattern => Agile Centre of Excellence
The alternative to this is a Decentralised or even Distributed Excellence: http://p2.fed.wiki/view/welcome-visitors/view/decentralised-excellence-over-centre-of-excellence (see also the articles linked, by Ove Herbert Holmberg and Thomas Cagley)
Does your company have one? Where did that come from? How is it working? Have you tried any alternative (e.g. Agile CoP)?
How do you feel about its doer-thinker separation, top-down flavour, and "best" practice thinking?
Agile Anti-Pattern => Agile as Canned solution & Standard recipes
The Anti-Pattern alternative: http://p2.fed.wiki/view/welcome-visitors/view/ideas-over-solutions
Since becoming mainstream Agile services tend to be closed proprietary commercial all-inclusive template solutions promising to work for all present and foreseeable situations.
Have you observed this anti-pattern in the wild? What's your experience? Which alternatives have you seen working well?
Agile Anti-Pattern => Agile Coaches/Transformation team like a golden-plated Functional Silo
The anti-pattern is documented here: (Agile Coaches Federation Over Agile Transformation Team) http://p2.fed.wiki/view/welcome-visitors/view/agile-coaches-federation-over-agile-transformation-team
Paradoxically most Agile Transformation Teams or teams of Agile Coaches are one more functional silo.
Have you seen it? What is your experience? Which alternatives have you seen working well?
#Agile #AgileAntipatterns #AgileTransformationTeam #AgileCoachesTeam #FunctionalSilos
Agile Anti-Pattern => Agile Transformation like a large Waterfall Programme
Agile Transformations often are large Waterfall Programme in disguise that are unfit for dealing with the inherent complexity of such an endeavour.
That's why so often they fail.
Instead Agile is better adopted in an Agile way that is iterative-incremental-empirical & more. That succeeds more often.
This anti-pattern's details here: http://p2.fed.wiki/view/welcome-visitors/view/agile-adoption-over-agile-transformation
Do you also have the feeling that when Agile entered the mainstream, a lot of things that made it work and succeed had been lost in translation?
That would explain the mixed results we see.
This list below is ironic and true at the same time...
