In this episode of Agile Driven Impact, hosts Diane H. Leonard, GPC, RST and Erich Leonard bring you back into the "Agile Garage" to discuss the art of getting feedback from your team and your project's stakeholders. They explore the importance of working product over contract negotiation. Learn how to invite candid, meaningful feedback about whatever type of work product your team is creating. Listen to the new episode - https://lnkd.in/gSSCcQek #AgileDrivenImpact #AgileForChangemakers #AgileInNonprofits #AgileValues

Comrades! 😆 During my time as an internal coach, I’ve often been asked: “Do you really think that team will get better? It’s too toxic. The issues are too deep. The challenges are too complex. Is it even possible? Maybe don’t bother.” My answer is always the same: yes - but every team’s journey is different. In my latest blog post I explore how teams are complex adaptive systems, how transformation happens, and what I love about coaching teams. Whilst writing it I wanted to add a bit about applying an agile mindset to team coaching and that has become a whole blog post of its own! So stay tuned, i'll let you know when its ready. Blog Post Here ➡️ https://lnkd.in/dM83ct6P #teamcoach #cynfin #insight

Experimentation turns setbacks into momentum. Mike Grabarek, SPHR, NCC of SS&C Technologies shows a test-and-learn mindset in #LearningAndDevelopment, embracing misfires, scaling wins and turning each attempt into insight with feedback loops, spaced learning and just-in-time coaching. This mindset treats every attempt as data and keeps L&D moving forward consistently. Click the link in the comments for the #LearningLeaderSpotlight episode. #CorporateTraining #TalentDevelopment #LeadershipTraining #WeAreTrainingPros

*** Micro-Retrospective*** Micro-Retrospectives: The 10-Minute Habit That Transforms Team Culture In most teams, retrospectives happen once every sprint — but what if learning became a daily rhythm? 💡 Enter Micro-Retrospectives — quick 10-minute reflections after major meetings, client calls, or deliverables. They help teams: 🔹 Catch small issues before they snowball. 🔹 Build a habit of open feedback. 🔹 Celebrate micro-wins instead of waiting till sprint end. 📍 Example: A support operations team started ending each shift with a “3-3-3” retro: 3 things that worked, 3 blockers, 3 improvements for tomorrow. Within weeks, response time dropped by 18%. Sometimes, it’s not big frameworks — it’s small, consistent habits that build agile culture. 💬 Do you use micro-retros or quick team check-ins? How do they shape your team’s mindset? #AgileMindset #ScrumMaster #ContinuousImprovement #TeamCulture #AgileLeadership #CorporateAgility #ScrumPractices

Breakthrough happens at the edge of chaos. In Episode 11 of the First Principles in Scrum discussion series, Jeff Sutherland and guest Paolo Sammicheli unpack powerful insights from chapter 9. “The whole human brain functions optimally at the edge of chaos. You’re most aware, you’re most creative, you’re most productive.” This is not just theory. It’s a core pattern in complex adaptive systems; one that plays out at every level of Scrum. Teams operating at the edge of chaos aren’t in disarray. They’re tuned for innovation. They’re sensing, adapting, evolving. This is where breakthroughs happen, and where sustainable speed becomes possible. Watch the full episode available now in your ScrumLab for Registered Scrum™ Professionals! #FirstPrinciplesInScrum #EdgeOfChaos #SystemsThinking

Scrum is the base foundation of AI. If you can’t Scrum, you can’t AI. And if you can’t Scrum at Scale, you can’t unlock AI at scale. Good stories matters, good AI is trained from your good stories better:-) #Scrum #ScrumAtScale #AgileLeadership #AI #DigitalTransformation #FutureReady #Breakthroughs 🌈 #AgileMagic ✨ #FutureOfWork 🚀

🎥 Tuesdays Value Added – Episode 4: Trust in Delivery Teams don’t lose trust because of missed deadlines, they lose it because of misalignment. Every time someone says “yes” without checking alignment, Predictability takes the hit. The fix isn’t saying no, it’s saying “let’s measure it.” When we measure the impact before we commit, we protect focus and relationships. That’s how teams stay predictable — and keep trust. 💭 How does your team measure impact before saying yes? #TuesdayValueAdded #AgileDelivery #ProjectManagement #AgileLeadership #ServantLeadership #ContinuousImprovement #ValueDelivery

Most teams think they’re learning. They run retrospectives, conduct customer interviews, and run experiments… and six months later, nothing has changed. Because reflection isn’t learning. Documentation isn’t learning. Discussion isn’t learning. Learning is what changes afterwards. I have written about the difference between the Learning Loop Illusion and Real Learning, the gaps that quietly kill progress, and how to close them. This one’s for the product and delivery teams who already “do agile,” but suspect the system isn’t learning fast enough to matter. 👉 Why Teams Don’t Learn (And How to Fix It) (Link in comments) #ProductManagement #LearningCulture #Leadership #ContinuousImprovement

🔹 𝐂𝐚𝐬𝐞 𝐒𝐭𝐮𝐝𝐲: 𝐖𝐡𝐞𝐧 𝐑𝐞𝐭𝐫𝐨𝐬𝐩𝐞𝐜𝐭𝐢𝐯𝐞𝐬 𝐓𝐮𝐫𝐧𝐞𝐝 𝐢𝐧𝐭𝐨 “𝐒𝐚𝐦𝐞 𝐎𝐥𝐝, 𝐒𝐚𝐦𝐞 𝐎𝐥𝐝” One team I coached had retrospectives that felt like a broken record. ➡️ Every sprint, the same issues came up: “𝘣𝘦𝘵𝘵𝘦𝘳 𝘤𝘰𝘮𝘮𝘶𝘯𝘪𝘤𝘢𝘵𝘪𝘰𝘯,” “𝘧𝘦𝘸𝘦𝘳 𝘭𝘢𝘴𝘵-𝘮𝘪𝘯𝘶𝘵𝘦 𝘤𝘩𝘢𝘯𝘨𝘦𝘴.” No energy, no ownership — and after a while, people stopped showing up mentally. 💡 𝐖𝐡𝐚𝐭 𝐈 𝐝𝐢𝐝: • Switched the format: used activities like “Start–Stop–Continue” and “Sailboat” to shake things up. • Limited discussion to the top 2 𝘢𝘤𝘵𝘪𝘰𝘯𝘢𝘣𝘭𝘦 𝘪𝘵𝘦𝘮𝘴 instead of a laundry list. • Introduced a visible “Retro Action Board” on the team wall — every item tracked, every sprint. 📈 𝐎𝐮𝐭𝐜𝐨𝐦𝐞: • Energy in retros improved — people actually looked forward to the change in format. • The team closed 80% of their retro actions within 3 sprints. • Morale lifted because improvements were 𝘷𝘪𝘴𝘪𝘣𝘭𝘦 and 𝘰𝘸𝘯𝘦𝘥 by the team. ✨ 𝐓𝐚𝐤𝐞𝐚𝐰𝐚𝐲: A retro without action is just group therapy. The magic happens when teams see real change carried forward. 👉 What’s the most creative retro format you’ve tried that actually worked? #ScrumMaster #Agile #CaseStudy #AgileCoaching

💡 The One Thing I Learned from Every Failed Sprint Retrospective 🌀 I’ve been part of dozens of retrospectives over the years some great | some forgettable | some that I walked out of thinking… 💭 “We’ll be having the same conversation two sprints later.” It took me years to realise the truth: 👉 A failed retrospective isn’t about the ceremony - it’s about the honesty we never reached. We often walk in with sticky notes, templates, and formats… But behind the colourful walls and virtual boards lie three silent blockers: 😶 Fear of conflict. 😐 Lack of trust. 😔 A culture where improvement feels optional. Retrospectives fail not because teams don’t care, but because psychological safety and accountability aren’t built into a meeting. They’re built into how we respond when things go wrong between meetings. 💭 The real progress happens when: 😶 People stop defending their point and start understanding others’. ⚙️ Teams discuss systems instead of blaming individuals. 👂 Leaders listen more than they talk. Now, when a retro doesn’t go as planned, I no longer see it as wasted time. I see it as data 📊 data about the culture, 🌱 data about the maturity, 💬 data about the emotional health of the team. Because retrospectives aren’t a tool for fixing processes. They’re a mirror that shows how well we fix ourselves. 🔥 The best retros aren’t about what we did wrong, they’re about what we’re ready to own. What’s the hardest pattern you’ve noticed in retros that’s tough to change? #AgileLeadership #TeamCulture #EngineeringLeadership #PsychologicalSafety #ScrumMastery #AgileCoaching #ContinuousImprovement #LeadershipDevelopment #TeamDynamics #SoftwareEngineering