Marc Godin

Which diagram should you actually use as a BA? It's a question I was asked recently... and it got me thinking. There are so many visual tools available... process maps, context diagrams, journey maps, ERDs, prototypes… the list goes on. The trick is: → You don’t need to be a master of every single one. → You just need to know what each is for, and when it makes sense to use it. ... and MOST importantly - the goal isn’t textbook perfection → it’s to create a picture of the work in a way stakeholders can understand. It’s about storytelling and collaboration, not perfect notation... Here’s how I think about it 👇 1️⃣ Core BA tools Process models, journey maps, context diagrams, use case diagrams. These are our bread and butter. 2️⃣ Shared tools ERDs, DFDs, state diagrams. BAs often co-create these with data or solution team members. 3️⃣ Specialist tools Sequence diagrams, wireframes. Not always BA-owned, but we’re often involved. That’s why I pulled this cheat sheet together (see carousel). Save it for later 🔖 Which one do you lean on the most in your projects? If you found this helpful, give me a follow Matthew Thomas Holliday and ♻️ reshare. If you wanna learn more on each of these, or want my templates - I go deeper in my community (link in bio). #businessanalyst #ba #agile

525

32 Comments

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 Comments

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 Comments

Scrum vs Kanban • Which framework truly drives success? • Why does this debate still haunt teams years later? If you’ve ever faced constant delays or miscommunication, this might be why. The choice between Scrum and Kanban is more than just process - it shapes how your team thinks, adapts, and delivers. → Scrum: The Sprint Architect • Time-boxed sprints build rhythm and predictability. • Roles like Product Owner & Scrum Master create strong accountability. • Frequent ceremonies enable reflection and continuous improvement. • Best for projects with evolving but somewhat defined goals. → Kanban: The Flow Master • Continuous delivery without fixed iterations encourages flexibility. • Visual boards highlight bottlenecks instantly. • Limiting work in progress maximizes focus and throughput. • Ideal for ongoing maintenance or unpredictable work streams. Follow Carlos Shoji for more insights on project management

350

27 Comments