Christian Torreblanca

Scrum Masters: How can you effectively lead change? Remember, you can’t make anyone Agile. But you can inspire them to become it. As Scrum Masters and Agile Coaches, we often feel the pressure to “drive change.” But here’s a truth I’ve learned (and re-learned): You’re a mirror, not a maker. People don’t change because we tell them to. They change when they’re ready to see their own potential. This shifted everything for me: → I stopped pushing frameworks and started reflecting values. → I traded control for curiosity and listening. → I realized that change isn’t an event, it’s a dialogue. Here are 3 reminders that hit home: 1/ Change happens from within 🗣️  Your role is to guide, not compel. 2/ Communication is a marathon 🗣️  Repetition isn’t a flaw; it’s the strategy. 3/ Listening is your superpower 🗣️  The real transformation starts when people feel heard. If you're navigating resistance, remember this: You’re not alone. Every great change agent has walked through this fire. 🔁 Keep showing up. 🔁 Keep listening. 🔁 Keep reflecting their best selves back to them. Which of these insights resonates most with your current coaching challenge? 👇 Let’s talk in the comments. Repost to help an agile practitioner. DM me if you need coaching to land your next agile role.

83

19 comentarios

Why AI Needs Scrum Masters, Project Managers & Program Managers More Than Ever ? AI is evolving faster than organizations can manage. Every week, there’s: ▪️ A new model ▪️ A new tool ▪️ A new big promise But here’s the truth → AI success isn’t about algorithms alone. It’s about people, processes, and decisions that shape the future. And that’s where roles like Scrum Masters, Technical Project Managers, and Program Managers step in: ▪️ Ensuring the right data flows into the right models ▪️ Aligning researchers, engineers, and business leaders (who often speak different “languages”) ▪️ Spotting risks that won’t show up in any Jira board ▪️ Asking the hard questions: - Should we build this? - What’s the impact if this fails? - Do we have the right guardrails in place? Without us → AI projects turn into silos of smart people running in different directions. With us → AI becomes strategic, ethical, and scalable innovation. In a world where speed without direction is chaos, we make sure AI actually lands where it needs to go—safely, purposefully, and with impact. The future isn’t just AI. It’s AI + Scrum Masters + TPMs + PMs who know how to guide it. What’s the one skill you think will define these roles in the AI era? Checkout the AI toolkit here - https://lnkd.in/gpS_qQ8r

246

26 comentarios

Stop preaching the Agile Manifesto to your clients. Yes, I love it. It's brilliant. But using it as your primary coaching tool is lazy – and sometimes even dangerous. Here's why:  The Agile Manifesto was written to describe what works in agile teams. It was never meant as a blueprint to transform corporations. The Manifesto assumes a certain culture. A certain view of people. A leadership style that creates trust and psychological safety. In that soil, its values and principles make perfect sense. But drop the same Manifesto into a Tayloristic culture – with rigid hierarchies, performance rankings, annual budgets, risk aversion… – and what happens?  👉 It gets ignored as "hippie talk"  👉 Or worse: it gets deliberately misunderstood and weaponized So if you're an agile coach pointing to the Manifesto as *the* solution, you're skipping the real work. You have to help leaders unlearn their old assumptions about people and management first. You have to build the cultural foundation.  Only then does the Agile Manifesto stop being "hippie stuff" – and start becoming a powerful guide. The Manifesto is not the beginning of the journey. It's the destination. #agile #leadership #AgileCoaching #AgileTransformation #culture

163

18 comentarios

What is the RACI tool? Why use it? RACI is a simple tool that clarifies who does what in a team, who owns decisions, who gives input, and who needs updates. One of the most common challenges Scrum Masters face? 👉 Lack of clarity on who does what. That’s where RACI comes in, a lightweight tool to clarify roles and avoid confusion. What RACI Stands For: •  R – Responsible → Does the work •  A – Accountable → Owns the outcome •  C – Consulted → Gives input before decisions •  I – Informed → Gets updates after decisions Why Scrum Teams Need It: ☑︎ Removes guesswork about who to involve ☑︎ Speeds up decision-making ☑︎ Avoids duplication of work ☑︎ Improves communication with stakeholders When to Use RACI: ✅ During team onboarding, set clear expectations ✅ When teams are cross-functional or distributed ✅ When there’s confusion about ownership of ceremonies or deliverables ✅ During scaling (multiple teams, multiple stakeholders) ✅ When creating your Team Working Agreement, draft it together and get buy-in so everyone agrees on roles and responsibilities Tips for Scrum Masters: ☑︎ Keep it lightweight, don’t turn it into bureaucracy ☑︎ Review it when team members or responsibilities change ☑︎ Use it as a conversation starter, not a rulebook ☑︎ Share it openly so everyone sees the same picture This simple chart by Shikha Prasad is a great example of how to apply RACI without overcomplicating things. Good Scrum thrives on autonomy, but autonomy needs clarity. What about you? Do you include RACI in your team’s working agreement? #Repost if you found this helpful

90

37 comentarios