While a team can rollback a code push that didn’t go well, refactor a feature that didn’t hit the mark, the one thing they can never recover is lost time. Use this retrospective technique to expose the thieves of time pestering your team,
Has the team’s daily stand-up lost a bit of freshness? How might you know? See if you can detect any of the following indicators:
No one seems to be listening to anyone else
Someone is giving waaaaaay too much detail
People are just reporting status: “I’ve been doing my job”
Lack of peer accountability
General dearth of energy
Ever heard of bikeshedding? Coined by C. Northcote Parkinson, it highlights our tendency to obsess over minor issues while ignoring major ones. In software development, it’s procrastination. Next time, just say “No” to endless discussions and focus on shipping! 🚀 #Bikeshedding
This is an open invitation to participate in an Agile Uprising (soon to be established) tradition of closing out each year with a series. In 2017 we released the 12 Days of Agile – a dozen podcasts, each chatting about one of the Agile Manifesto Principles (clever, ay?) Then we ignored the …
Unpack the relationship between Lean and Agile. Lean, rooted in Toyota’s system, emphasizes value, quality, and rapid response to market demand. It’s about eliminating waste, respecting people, and optimizing the whole. Lean and Agile, when combined, expose problems and catalyze continuous improvement. 🔄🚀 #Lean #Agile
