You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Over a year ago, we decided to run a retrospective on agile. The insights from around the community were wonderful. Even after we published our findings, I was stuck with a nagging question about what's after agile? It's not so much that we have to leave all those wonderful agile lessons behind. It's more how the agile community seems to be unable to explain the failures of agile beyond categorizing the failures as not agile. Is there something that does explain it?
I think part of the answer comes from Dave Snowden's Cynefin framework because it explains why we can't apply agile as if it were "best practice". Layering on top of that, I think there is a balance between the needs of resilience and efficiency, where there is a narrow band that creates a kind of self-sustaining growth.
At Summit, I got a chance to explain what these ideas mean to me, as someone who has been in the software industry for almost 2 decades: After Agile, DevOps, and Lean IT: Modern Methodology in the Age of Disruption
If you learn something from those ideas, please share!