Retrospective: A structured practice of collectively examining recent experiences to identify opportunities for improvement. It enables amplifying problems, simplifying complex issues through focused analysis, and rewiring the social circuitry towards transparency, alignment, and sustained positive change. Retrospectives foster continuous learning and iterative refinement – essential for high performance.
How many of us look forward to the traditional annual performance review? I mean really, whether you are on the presenting or receiving side of things… it is not the highlight of the year for anyone I know. I believe there’s a better way – Team Roundtable Reviews.
It takes many different mindsets and behaviors to make a team hum. I am appreciating a view of collaborative behaviors developed by David Kantor (as part of his work on Structural Dynamics), and am finding it useful as a way to hold up a mirror to a team that is interested in understanding and improving their communication.
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,
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
Velocity as the Goal – Unraveling the Laws: Delve into the three laws—Hawthorn Effect, Goodhart’s Law, and Friedman’s Thermostat—that influence outcomes when velocity becomes the sole focus. Learn why setting quantitative goals isn’t enough.
