Blog Article
4 Old School Agile Mantras that Change Agents Should Be Stealing
I think it's a good assumption to say that when agile started to become a big business somewhere around 2012-ish, the intention was lost. These are 4 super old mantras many of us, uh, older agile fellows live by that capture the spirit of what agile is along with how you can adapt them to the wonderful work you're doing as a change agent.
This article originally appeared on Linked In. Here's a summary generated by Chat GPT:The article discusses four old mantras from the agile software development world and explains how they can be adapted and applied to the role of a change agent in various contexts:[ml][ol][li indent=0 align=left][color=var(--tw-prose-bold)]YAGNI ("You Ain't Gonna Need It"):[/color][/li][/ol][/ml][ml][ul][ul data=1][li indent=1 align=left]In software development, it advises against adding unnecessary features just because they sound cool or someone suggests they might be needed in the future.[/li][li indent=1 align=left]Encourages simplicity and focusing on what is needed right now.[/li][li indent=1 align=left]Apply it to change by prioritizing important tasks, maintaining a list of next steps, and aligning them with the bigger picture.[/li][/ul][/ul][/ml][ml][ol][li indent=0 align=left][color=var(--tw-prose-bold)]Last Responsible Moment:[/color][/li][/ol][/ml][ml][ul][ul data=1][li indent=1 align=left]Compares decision-making to standing in line at an ice cream parlor, where you delay choices until you have gathered all relevant information.[/li][li indent=1 align=left]Prevents rushing into big decisions prematurely.[/li][li indent=1 align=left]Suggests asking whether a decision needs to be made now or can wait, helping with prioritization in change efforts.[/li][/ul][/ul][/ml][ml][ol][li indent=0 align=left][color=var(--tw-prose-bold)]Firing a Tracer Bullet:[/color][/li][/ol][/ml][ml][ul][ul data=1][li indent=1 align=left]A metaphor from software development that involves creating a feature through the entire tech stack to understand the big picture before full implementation.[/li][li indent=1 align=left]Helps identify design issues early and avoids costly rework.[/li][li indent=1 align=left]For change, it can be applied by breaking down transformation efforts into smaller, manageable cohorts or phases to gain insights and adapt.[/li][/ul][/ul][/ml][ml][ol][li indent=0 align=left][color=var(--tw-prose-bold)]Yesterday's Weather:[/color][/li][/ol][/ml][ml][ul][ul data=1][li indent=1 align=left]In agile, it means using past performance to forecast future outcomes, improving predictability over time.[/li][li indent=1 align=left]For change, it can be used to learn from previous attempts at transformation and adjust the approach based on past experiences.[/li][/ul][/ul][/ml]The article suggests that these four mantras provide valuable insights for approaching change and can be beneficial for those involved in change management, even beyond the realm of software development.