🚀 I help Scrum Masters, Product Owners and Product Managers Grow w/ Books, Classes, Courses, and Community. 📖 Author of the ”Scrum Anti-Patterns Guide;” 🏅Trainer at Scrum.org ⬇️ Book a 1-on-1 to discuss opportunities!
#TeamMetrics can be game-changers—but do you track the right ones? 🧐 If you take Kaizen seriously, read on. 💡 Agile teams thrive on continuous improvement and adaptability. Self-assessment isn’t just a measuring tool but a compass guiding teams toward their potential. It enables teams to understand their strengths, identify areas of improvement, and delve deeper into work dynamics beyond mere output. The true essence of self-assessment in Agile is fostering transparency, collaboration, and relentless improvement. It’s not an audit; it’s a mirror reflecting a better version of your Agile team. This article comprises well-known self-assessment tools; use them or have them inspire you to create your own assessment. 👇 Join the conversation and enlighten us with your approach to improve continuously. Useful? Like / Follow / Repost 👉 You have not yet enrolled in the free email course on Scrum anti-patterns? Don’t miss out; hundreds already did: https://lnkd.in/d2BYdCqK
But… without psychological safety what are we looking at? I think part of the key is team metrics need to be metrics that the team sees value in and safe (for team eyes only unless agreed)
Great post! I completely agree that tracking the right metrics is crucial for Agile teams to drive continuous improvement and reach their full potential. Self-assessment plays a vital role in this process, as it provides teams with valuable insights into their strengths and areas for improvement. By fostering transparency, collaboration, and a culture of relentless improvement, self-assessment helps Agile teams become more self-aware and better equipped to make informed decisions. It's indeed not an audit but a mirror that reflects a better version of the team. I would encourage teams to explore the well-known self-assessment tools mentioned in the article or even create their own customized assessments that align with their specific goals and context. The key is to regularly engage in self-reflection and use the insights gained to drive continuous growth and development. Keep up the great work in embracing the Agile mindset and striving for continuous improvement! 🚀💪
Any thoughts about the Gallup Q12?
While I see the value in doing surveys or assessment from consultant perspective, as a team member, I loathed recurring surveys, and those done at the end of every Sprint were the worst drudgery. Which metrics for teams can we capture that are useful without repeatedly asking the same questions?
Value is an ultimate measure of teams health, and Evidence based management metrics are best way to establish teams fitness. Other surveys can be run only if developers themselves want it. Otherwise is antipattern and waste of time, can also become an impediment and reason for resistance.
Interestingly, we have in AgilityHealth many general and customized radars to assess different agile and business agility metrics
While I can see the benefit of surveys and when used well they can help the team explore what is going on for them. One pitfall I have seen is when the survey is used to confirm what you think you are seeing rather than what is actually happening for the people in the system. Some sort of confirmation bias could be at play...
nice!
Business Agility Coach | Author | Technology Strategist | Gentle Instigator
2moI have some strong opinions about this :) So much so I've started building my own assessment. Lots of teams really dislike the survey process, assigning a score to their happiness, or otherwise doing a tedious self-reflective process over and over. My theory is that if you want to work on continuous improvement (real process and behavior changes) you should - only inspect quarterly with a different kind of retro - do a fairly deep dive, but one that still doesn't take a lot of time - no scores, just consensus building + discussion on where to focus - and most importantly, it should be actually based on *behaviors* and nothing to do with frameworks or scaling approach. Focus on Agile Mindset based behaviors. Things like iterative thinking, agile basics and collaboration, xp values, lean techniques, devops approach, being product driven, customer-centric and empirical, having a culture of learning and experimentation, and psychological safety both inside and outside the team. I have a very early MVP put together and would love to invite feedback from anyone interested in being an early adopter. Learn more at MeasureTheMindset.com