Guillaume Thonnard

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

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

A Sprint isn’t just two weeks of coding – here’s what really happens inside it 📅 When Does a Sprint Happen? Immediately after the previous Sprint ends There's no gap — continuous rhythm 🔍 What Happens Inside a Sprint? Sprint Planning (Day 1) — Set what will be done & how it will be done. Define Sprint Goal. Daily Scrums (Every Day) — Inspect progress toward the Sprint Goal, adjust the plan if needed. Refinement (Ongoing) — Clarify upcoming Product Backlog items for future Sprints; it’s informal but continuous. Development Work — Delivering a “Done” Increment. Sprint Review (End of Sprint) — Collaborate with stakeholders, inspect the product, adapt the backlog. Sprint Retrospective (End of Sprint) — Inspect and improve processes. 💡 Why Does It Happen This Way? To ensure focus, adaptability, and continuous delivery of value. Vikas N Harale #ScrumMaster #AgileLeadership #AgileMindset #TeamTransformation #ScrumLife #AgileCoach #AgilePractices #ScrumTeam #AgileWaysOfWorking #LeadershipInAgile #ContinuousImprovement #HighPerformingTeams #AgileTransformation #ServantLeadership #ScrumCulture #Sprintretrospective #scrumcermonies

64

26 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

Adding teams rarely speeds up delivery, it often makes things worse by increasing dependencies and coordination overhead. In this post, PST Cesario Ramos makes the case for why the fix isn’t more teams, it’s smarter organizational design. https://ow.ly/Luug50WtAVa #Agile #OrganizationalDesign

160

11 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

✅ 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

🔍 𝗧𝗗𝗗 𝘃𝘀 𝗕𝗗𝗗 – 𝗦𝗮𝗺𝗲 𝗧𝗵𝗶𝗻𝗴? 𝗡𝗼𝘁 𝗤𝘂𝗶𝘁𝗲! In Agile product development, many teams mix up 𝗧𝗲𝘀𝘁-𝗗𝗿𝗶𝘃𝗲𝗻 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁 (𝗧𝗗𝗗) and 𝗕𝗲𝗵𝗮𝘃𝗶𝗼𝗿-𝗗𝗿𝗶𝘃𝗲𝗻 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁 (𝗕𝗗𝗗). While both improve software quality and reduce rework, they focus on different perspectives. Let’s break it down 👇 ✅ 𝗧𝗲𝘀𝘁-𝗗𝗿𝗶𝘃𝗲𝗻 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁 (𝗧𝗗𝗗) • 𝗪𝗵𝗮𝘁 𝗶𝘁 𝗶𝘀: A developer-focused practice where tests are written before the code. • 𝗣𝘂𝗿𝗽𝗼𝘀𝗲: Ensures code is reliable, clean, and meets technical requirements. • 𝗦𝗰𝗼𝗽𝗲: Unit-level or component-level. • 𝗛𝗼𝘄 𝗶𝘁 𝘄𝗼𝗿𝗸𝘀: 1️⃣ Write a failing test 2️⃣ Write just enough code to pass the test 3️⃣ Refactor the code • 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: Testing if a login function returns true when valid credentials are provided. Think of TDD as 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝘄𝗶𝘁𝗵 𝗴𝘂𝗮𝗿𝗱𝗿𝗮𝗶𝗹𝘀 𝗳𝗿𝗼𝗺 𝘁𝗵𝗲 𝘀𝘁𝗮𝗿𝘁. 📝 𝗕𝗲𝗵𝗮𝘃𝗶𝗼𝗿-𝗗𝗿𝗶𝘃𝗲𝗻 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁 (𝗕𝗗𝗗) • 𝗪𝗵𝗮𝘁 𝗶𝘁 𝗶𝘀: A collaboration-focused practice that defines system behavior in business-friendly language. • 𝗣𝘂𝗿𝗽𝗼𝘀𝗲: Aligns developers, testers, and business stakeholders on expected outcomes. • 𝗦𝗰𝗼𝗽𝗲: Higher-level scenarios and user journeys. • 𝗛𝗼𝘄 𝗶𝘁 𝘄𝗼𝗿𝗸𝘀: Uses 𝗚𝗵𝗲𝗿𝗸𝗶𝗻 𝘀𝘆𝗻𝘁𝗮𝘅 (𝗚𝗶𝘃𝗲𝗻-𝗪𝗵𝗲𝗻-𝗧𝗵𝗲𝗻) to describe behavior. • 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: 1️⃣ Write User Story: "As a WhatsApp user, I want to send a message to my friend" 2️⃣ Write Scenario: "Send message to John"  - Given I'm logged in  - When I send message to John  - Then John receives message 3️⃣ Write Step Definitions: Implement code for each step 4️⃣ Run Scenario: Ensure scenario passes! Think of BDD as 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝘀𝗵𝗮𝗿𝗲𝗱 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 𝗯𝗲𝗳𝗼𝗿𝗲 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝘁𝗵𝗲 𝗰𝗼𝗱𝗲. 💡 𝗞𝗲𝘆 𝗗𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝗰𝗲: • 𝗧𝗗𝗗 = 𝗛𝗼𝘄 𝘁𝗵𝗲 𝘀𝘆𝘀𝘁𝗲𝗺 𝘄𝗼𝗿𝗸𝘀 (𝗰𝗼𝗱𝗲-𝗹𝗲𝘃𝗲𝗹). • 𝗕𝗗𝗗 = 𝗛𝗼𝘄 𝘁𝗵𝗲 𝘀𝘆𝘀𝘁𝗲𝗺 𝘀𝗵𝗼𝘂𝗹𝗱 𝗯𝗲𝗵𝗮𝘃𝗲 (𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀-𝗹𝗲𝘃𝗲𝗹). Both complement each other — TDD ensures robust implementation, while BDD ensures stakeholder alignment and product value. 🚀 💬 𝗤𝘂𝗲𝘀𝘁𝗶𝗼𝗻 𝗳𝗼𝗿 𝘆𝗼𝘂: Has your team tried combining TDD and BDD for maximum impact? If yes, how was the experience? #Agile #Scrum #TDD #BDD #AgileMindset #SoftwareTesting #QualityEngineering #AgileDevelopment #AgilePractices #Collaboration #AgileWithAayush #CountinousImprovement

51

7 commentaires