Guillaume Odie

Understand Scrum in 5 minutes Scrum is simple to understand… but hard to master. Most teams say they “do Scrum,” but few actually live it. Scrum ≠ Process. It’s a framework for focused delivery, built on collaboration, iteration, and improvement. Scrum gives you: ✅ Structure without rigidity ✅ Flexibility without chaos ✅ Accountability without micromanagement ☑︎ Agile vs Scrum, the truth: Agile is the mindset. Scrum is an execution engine (Framework) Agile says “be adaptable.” Scrum shows how. ☑︎ The Scrum DNA 1. Timeboxed Sprints (2–4 weeks) 2. Clear Roles and events 3. Transparent Artifacts 4. Relentless Improvement ☑︎ The 5 Scrum Values Commitment. Courage. Focus. Openness. Respect. If your team doesn’t live these, you’re just pretending to be Agile. Scrum isn’t daily stand-ups and sticky notes. It’s a culture of accountability, focus, and delivery. If your Scrum Master isn’t protecting that, they’re part of the problem. ☑︎ Your turn: ↓ What’s the most misunderstood part of Scrum in your team? Share with us in the comments - Sharing is learning #Repost to help others gain more clarity #Follow Stanley for more Agile-related posts 🖼 Credit @shraddha sahu

135

23 commentaires

The four key gateways in BPMN allow you to model complex business processes elegantly and accurately. However, many business analysts confuse their usage, resulting in unclear diagrams and miscommunication with developers and stakeholders. Here’s a quick visual guide: ✅ Exclusive Gateway (XOR) – only one path is taken based on conditions (e.g., bug vs change request). ✅ Parallel Gateway – runs multiple tasks at the same time (e.g., developer writes code while QA prepares tests). ✅ Inclusive Gateway – allows one or more branches to run in parallel depending on conditions (e.g., frontend and/or backend changes). ✅ Event-Based Gateway – waits for an event to decide the path (e.g., feedback received vs auto-approval according to schedule). 💡 Which gateway do you see most often misused in projects? Share your experience in the comments! ‼️If you want to improve your modelling skills, Art of Business Analysis can help you! #BusinessAnalysis #BPMN #RequirementsEngineering #ProcessModeling #ArtOfBA #artofbusinessanalysis

605

27 commentaires

Scrum Masters — if your metrics don't reflect customer reality, you're not measuring progress. You're optimizing the illusion of it. Scrum teams don't get paid to move tickets. They get paid to move the needle. Yet most Scrum Masters still obsess over: 📊 Stories Planned vs. Stories Delivered 📈 Velocity trends 🏁 Burndown charts All of which tell us how busy we are. But not whether we made anything better. 🛑 Velocity target: 100 — met. 🛑 Dashboard: glowing green. 🛑 Team: feeling accomplished. 🛑 Users: Still stuck. So, your team didn't fail the sprint. But the sprint failed the customer. Here's how I think about it instead: ✅ Output = Features shipped, code deployed, hours logged ✅ Outcome = A real user can now do something they couldn't before ✅ Impact = The organization gains when that outcome drives satisfaction, loyalty, or revenue Here's the difference: 🚫 "We completed 48 story points this sprint." (Output) ✅ "80% of users now complete onboarding in under 2 minutes." (Outcome) 📈 "Conversion rates for new users increased by 12%." (Impact) 🚫 "We released 6 new dashboard widgets." (Output) ✅ "Customers are now identifying spending anomalies 40% faster." (Outcome) 📈 "This reduced churn in premium accounts by 18%." (Impact) Scrum without outcome thinking is just sophisticated busyness. 👉 Shift your sprint goals from "story done" to "delivered value." 👉 Measure what users gain, not what you give. 👉 Track progress based on real change not performance theater. Busy teams burn out.
Value-focused teams win. #ReTHINKscrum #ScrumMastery Agilemania Agilemania Malaysia

57

7 commentaires

You are just getting started with BPMN? Watch this ⤵️​ Most beginners think BPMN is only for experts or technical teams, but the truth is, it’s designed to make business processes clear for everyone. Here’s the good news: you don't need to master all the BPMN standard before starting. You only need a few building blocks to start creating powerful process diagrams: - Events: the “moments” that start, end, or change your process - Activities: the concrete steps, like “verify order” or “send invoice” - Gateways: the decision points that guide the flow - Flows: arrows that connect it all together - Lanes: showing who does what in your organization With just these basics, you can map processes like order handling, approvals, or project workflows, and make them instantly understandable for managers, teams, and stakeholders. PS: Download my FREE ebook and master the core concepts of BPMN process automation with Camunda (link in my profile).

44

1 commentaire

✅ Join our 𝐖𝐡𝐚𝐭𝐬𝐀𝐩𝐩 𝐠𝐫𝐨𝐮𝐩 for daily Scrum & Agile insights 🔗 https://lnkd.in/d2CTUCnu 🔸 𝐍𝐞𝐞𝐝 𝟏:𝟏 𝐜𝐨𝐚𝐜𝐡𝐢𝐧𝐠, 𝐢𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰 𝐩𝐫𝐞𝐩, 𝐨𝐫 𝐀𝐠𝐢𝐥𝐞 𝐠𝐮𝐢𝐝𝐚𝐧𝐜𝐞? 📞 Call/WhatsApp: 9137275692 ✅ 𝐖𝐡𝐚𝐭 𝐢𝐬 𝐊𝐓𝐋𝐎 𝐢𝐧 𝐒𝐜𝐫𝐮𝐦—𝐚𝐧𝐝 𝐖𝐡𝐲 𝐈𝐭 𝐌𝐚𝐭𝐭𝐞𝐫𝐬 If you’ve ever wondered why your team’s Sprint capacity seems tight even before development starts, the answer might be KTLO. 1️⃣ 𝐖𝐡𝐚𝐭 𝐢𝐬 𝐊𝐓𝐋𝐎? 🔸 KTLO stands for "Keep the Lights On"—essential maintenance work that ensures systems continue to function smoothly. 🔸 These are not roadmap features but are critical for operational stability. ✅𝐄𝐱𝐚𝐦𝐩𝐥𝐞𝐬 𝐨𝐟 𝐊𝐓𝐋𝐎 𝐓𝐚𝐬𝐤𝐬: 🔸Bug fixes 🔸Server patching 🔸Security updates 🔸Incident response 🔸Routine backups 🔸System monitoring 2️⃣ Why KTLO Matters in Scrum KTLO tasks can be unpredictable and recurring. If left unmanaged, they consume team bandwidth and quietly derail feature delivery. ✅𝐈𝐦𝐩𝐚𝐜𝐭 𝐨𝐧 𝐒𝐜𝐫𝐮𝐦 𝐓𝐞𝐚𝐦𝐬: 🔸Reduces availability for Sprint Goals 🔸Adds unplanned work mid-Sprint 🔸Affects velocity and stakeholder expectations 3️⃣ 𝐇𝐨𝐰 𝐭𝐨 𝐌𝐚𝐧𝐚𝐠𝐞 𝐊𝐓𝐋𝐎 𝐢𝐧 𝐒𝐜𝐫𝐮𝐦: ✅ 𝐂𝐚𝐩𝐚𝐜𝐢𝐭𝐲 𝐁𝐮𝐟𝐟𝐞𝐫𝐢𝐧𝐠 🔹 Reserve 10–30% of Sprint capacity based on past KTLO load. ✅ 𝐓𝐫𝐚𝐜𝐤 𝐚𝐧𝐝 𝐌𝐞𝐚𝐬𝐮𝐫𝐞 🔹 Log KTLO tasks in JIRA (or similar tools) to review impact and patterns. ✅ 𝐈𝐧𝐜𝐥𝐮𝐝𝐞 𝐢𝐧 𝐒𝐩𝐫𝐢𝐧𝐭 𝐏𝐥𝐚𝐧𝐧𝐢𝐧𝐠 🔹 Raise known KTLO work upfront to adjust commitments realistically. ✅ 𝐁𝐚𝐜𝐤𝐥𝐨𝐠 𝐏𝐫𝐢𝐨𝐫𝐢𝐭𝐢𝐳𝐚𝐭𝐢𝐨𝐧 🔹 If a KTLO task is known in advance (e.g., planned upgrade), treat it like any other Product Backlog Item. ✅ 𝐔𝐬𝐞 𝐒𝐜𝐫𝐮𝐦𝐛𝐚𝐧 (𝐢𝐟 𝐧𝐞𝐞𝐝𝐞𝐝) 🔹 In teams with high KTLO demand, a Scrumban approach allows more flexibility in managing flow. ✅𝐄𝐱𝐚𝐦𝐩𝐥𝐞 𝐒𝐜𝐞𝐧𝐚𝐫𝐢𝐨: A team working on a public sector healthcare portal may have to: 🔸Respond to a sudden server downtime 🔸Apply critical patches from a new security bulletin 🔸Monitor system load and troubleshoot urgent performance drops 🔸None of these are “features,” but without them, nothing runs. ✅Takeaway: If you’re a Scrum Master or Product Owner, acknowledging and planning for KTLO is essential to protect your Sprint Goals and maintain transparency with stakeholders. ✅ Have KTLO tasks ever derailed your Sprint plan? How did your team handle it? Drop your thoughts in the comments—I’d love to learn from you! 👇 ✅ Follow Chandan Kumar for hands-on Scrum strategies, Agile leadership lessons, and field-tested team guidance.

48

3 commentaires

𝗦𝗰𝗿𝘂𝗺 𝗙𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸 𝗩𝗶𝘀𝘂𝗮𝗹𝗶𝘇𝗮𝘁𝗶𝗼𝗻 👇 Scrum has revolutionized product development with its agile approach, emphasizing collaboration and adaptability for faster, customer-centric outcomes. It all begins with the creation and continuous refinement of the 𝗽𝗿𝗼𝗱𝘂𝗰𝘁 𝗯𝗮𝗰𝗸𝗹𝗼𝗴 — A dynamic list of prioritized features and requirements that flexibly adapt to evolving customer needs and project objectives 𝗞𝗲𝘆 𝗣𝗲𝗿𝘀𝗼𝗻𝗮𝘀: 𝟭. 𝗦𝘁𝗮𝗸𝗲𝗵𝗼𝗹𝗱𝗲𝗿𝘀: Shape the product's direction and goals 𝟮. 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗢𝘄𝗻𝗲𝗿: Prioritizes and defines what gets built 𝟯. 𝗦𝗰𝗿𝘂𝗺 𝗠𝗮𝘀𝘁𝗲𝗿: Facilitates team success and removes obstacles 𝟰. 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁 𝗧𝗲𝗮𝗺: Builds the product collaboratively 𝗡𝗲𝘅𝘁, 𝗣𝗹𝗮𝗻 𝘆𝗼𝘂𝗿 𝗦𝗽𝗿𝗶𝗻𝘁: A time-boxed iteration in Scrum focused on delivering a specific set of features or work within a fixed timeframe 𝗞𝗲𝘆 𝗖𝗲𝗿𝗲𝗺𝗼𝗻𝗶𝗲𝘀: 𝟭. 𝗦𝗽𝗿𝗶𝗻𝘁 𝗣𝗹𝗮𝗻𝗻𝗶𝗻𝗴: - Review the product backlog - Discuss and select sprint goals - Choose backlog items for the sprint - Create a sprint backlog 𝟮. 𝗗𝗮𝗶𝗹𝘆 𝗦𝘁𝗮𝗻𝗱𝘂𝗽 (𝗗𝗮𝗶𝗹𝘆 𝗦𝗰𝗿𝘂𝗺): - Share what was done yesterday - Discuss what will be done today - Mention any blockers or impediments 💡 Ensure discussions stay focused to end stand-up calls on time 𝟯. 𝗦𝗽𝗿𝗶𝗻𝘁 𝗥𝗲𝘃𝗶𝗲𝘄: - Demonstrate completed work - Gather feedback from stakeholders - Discuss potential changes to the product backlog 𝟰. 𝗦𝗽𝗿𝗶𝗻𝘁 𝗥𝗲𝘁𝗿𝗼𝘀𝗽𝗲𝗰𝘁𝗶𝘃𝗲: - Reflect on the last sprint's processes and teamwork - Identify what went well and what could be improved - Create action items for improvement in the next sprint 👉 Key take away: To be successful in Scrum, focus on collaboration, iterative progress, and delivering customer value.

36

“I’m a new Scrum Master — what do I actually do every day?” Every new Scrum Master asks this at some point. You’ve passed the certification. You’ve landed the role. And now it’s Monday at 10:15 a.m. — the Daily Scrum just ended — and you’re staring at your laptop wondering: “Okay… now what? What do I actually do for the rest of the week?” Spoiler: the real work of a Scrum Master happens outside the ceremonies. Those 15–60 minute meetings? That’s maybe 10% of your week. The other 90%? That’s the invisible work no one tells you about: 🛠️ The Invisible Work That Matters Most: 👉 Coaching ✅ Coaching the developer who “forgot” (again) to update their story status — and helping them understand why visibility matters. ✅ Helping a Product Owner slice that monster story into smaller stories the team can actually finish within the sprint. 👉 Resolving blockers (including the ones Jira never shows you) ✅ Facilitating the removal of blockers. ✅ Identifying blocker patterns that keep coming back. 👉 Protecting the team’s focus ✅ Saying “no” (politely but firmly) when leadership tries to sneak in “just one quick thing.” ✅ Guarding space so the team can finish work instead of context switching every 24 hours. 👉 Getting to know your team one-on-one ✅ Ask meaningful questions: what excites them about their work? What frustrates them? What does “a good day” look like for them? ✅ Use one-on-ones to uncover hidden tensions — not tasks, but energy, motivation, or confidence barriers. 👉 Observing the dynamics nobody else notices ✅ Who interrupts who in meetings? ✅ Who’s always quiet but might be sitting on the best idea? 👉 Identifying bottlenecks early ✅ Noticing where work always gets stuck in the flow. ✅ Helping the team redesign how work moves so progress doesn’t stall. 👉 Ensuring the team is healthy ✅ Creating a psychologically safe environment where people feel valued, not just measured. ✅ Championing sustainable pace over short-term speed. 👉 Making work human again ✅ Checking in on morale. ✅ Reminding the team they’re not “resources” — they’re people. ✅ Bringing humor, perspective, and relief into high-pressure weeks. 💡 Here’s the truth: Scrum Masters aren’t busy because they’re running ceremonies. They’re busy because they’re removing friction — human, technical, and organizational. Sometimes that looks like coaching. Sometimes it looks like protecting. Sometimes it looks like asking hard questions. And sometimes it looks like just being there so the team feels seen, supported, and safe to do their best work. ⚡ So if you’re a new Scrum Master wondering what you “actually do”? You do the quiet, invisible things that help teams thrive. And that’s the part that makes you indispensable. 👉 If you’re a new Scrum Master, save this post. 👉 If you’re an experienced one, drop in the comments: What do you spend the majority of your week doing outside of ceremonies?

279

59 commentaires