Stefan Heil

Will we see Two-Member Scrum Teams in the near future?!   I myself believe the answer is yes. We will see it as a new norm soon.   At my company, ScrumSchool.org, we are already operating this way.   Our team consists of just two people: me as the Product Owner and my knowledgeable colleague, Pooya Sabramooz, as the sole Developer.   → Our secret? We leverage AI aggressively across every aspect of our work.   Let's set aside bias and look at the facts.   Every business, from startups to large enterprises, is constantly seeking ways to optimize and reduce costs.   AI has emerged as the most powerful tool to help us achieve it.   The time that we are in now is like the first days of the internet. That was amazing, but the effective usage was not in place yet.   After a while, people and businesses learned to leverage the internet to expand their market and work more effectively.   ✓ Today, AI is often used for generating fancy things, but we are quickly learning to integrate it into our core operations to work smarter and deliver value more efficiently.   Now, let’s check the Scrum Team story.   We know that the Scrum Team has three accountabilities: Product Owner, Scrum Master, and Developers.   Crucially, it does not mandate that these must be three separate individuals.   When you can delegate most of the work to AI, why should we ignore this huge opportunity?!   In this new paradigm, human roles are evolving from hands-on executors to strategic orchestrators.   We define goals, select and configure AI agents, and then carefully review and manage their outputs to ensure a seamless flow of value.   ✓ The Product Owner will still be in contact with customers and stakeholders and make strategic decisions.   ✓ The Developer architects the system, sets up and monitors AI tools, and ensures the quality of the delivered product.    ✓ The Scrum Master’s accountability is shared between the two members, as the team is too small for a dedicated role. They jointly facilitate continuous improvement and uphold Scrum rules and practices.   Although we are seeing that AI can do a lot of good things today, the main question still is how to integrate them into our workflows, where AI has taken over much of our day-to-day work.   What do you think? Will we see Two-Member Scrum Teams soon, or not? Let's discuss.   Share your perspective in the comments.   🎇 If this post receives 30 comments with "Possible," I will create an article or video breaking down our exact operating model—how we delegate work to AI and make this two-member team structure not just possible, but highly effective.   ♻️ Repost to trigger the debate in your network. ➕ Follow Mehdi Hoseini for more.   #scrum #agile #ai #scrum_team #ai_agent #ai_scrum_team   Scrum.org Pooya Sabramooz

80

199 Kommentare

Your company is not a collection of individual performances. Yet most organizations measure people that way – hours logged, tasks completed, individual goals checked off. The result? 🙄 People optimize for themselves, not the team. 🙄 Colleagues start competing instead of collaborating. 🙄 Customers get forgotten in the noise. In complex work, one person’s “high performance” can actually reduce the system’s performance. That’s local optimization. Teams win together, or they don’t win at all. 😖 Stop setting individual goals 🙄 Stop judging performance in isolation 🙈 Stop mistaking activity for value 👉 Measure outcomes, not hours 👉 Reward collaboration, not ego 👉 Focus on the customer, not the clock If you want agility, measure flow – not individuals. #agile #leadership #teamwork #ValueStreams

78

8 Kommentare

Think becoming a Scrum Master in 2025 is just about memorizing roles and running daily standups? Think again. The path to becoming a great Scrum Master goes way deeper, from mastering facilitation and servant leadership, to guiding retrospectives that actually spark change, to staying sharp with the latest Agile trends and tools like AI assistants and automated metrics. It’s not just about theory; it’s about real-world practice that makes teams thrive. This roadmap breaks down exactly how you can grow step by step, whether you’re just starting or aiming to specialize in areas like SAFe, DevOps culture, or remote teams. The future of Scrum needs leaders who can balance people, process, and technology. So, are you ready to stop “doing Scrum” and start living Scrum in 2025 Which step in this roadmap do you think is the toughest and why? 🔗 Learn in detail about how to become scrum master - https://lnkd.in/dwFs7cei Agilemania Malaysia Scaled Agile (SAFe®) Training by Agilemania Naveen Kumar Singh Satyajit Gantayat Sumeet Madan Piyush Rahate Anil Malik #scrum #agile #scrummaster #agilemania #scrumteam #leadership #agilecoach

338

11 Kommentare

Comic Agilé no. 204 - The Middle Manager (reshare) Jonathan Byrnes , MIT senior lecturer, wrote in 2005 that the most important thing CEOs can do is build strong Middle Management (VPs, Directors and Managers). While leadership styles have evolved (toward empowerment and servant leadership), his point still holds: “the highest calling in Management is teaching your Managers to manage.” The challenge arises when Executives don’t embrace agile ways of working. Middle Managers are then caught between teams seeking autonomy and Executives demanding total control and detailed oversight The fix: secure an Executive sponsor early, or win one over by showing how agile practices have already improved results and the further potential if leadership truly commits. In an agile organization, Middle Managers (and all leaders) must servant-lead, foster psychological safety, and provide the resources for empowered teams—the atomic unit of the company. Their mission is to expand these teams’ influence relentlessly, even when it takes tough coaching battles to get there. #agile #middlemanager #linemanager #thefrozenmiddle #comicagile

279

5 Kommentare

In 1995 Scrum (or SCRUM) was described as a Development Process, in 1998* as an Extension Pattern Language, and in 2003 as a Methodology. The word "framework" was used in the 1995 paper but as a synonym for method, rather than a description of Scrum itself. The term was also used in the 2003 paper as a synonym for skeleton (an Agile process was described as having a skeleton and a heart). In 2005 I recall very clearly Ken Schwaber informing the attendees at the first Scrum Gathering: "Scrum is not a methodology, it is a pathway". The first reference I can find to Scrum being described purely as a framework is in the 2009 draft Scrum Guide: "Scrum is not a process or a technique for building products; rather, it is a framework within which you can employ various processes and techniques." So, to summarise, Scrum is a process, not-a-process, a pattern language, a skeleton, a method, a methodology, not-a-methodology, a pathway, and finally a framework. Confused? You are not alone :) * I first wrote 1999, but the Beedle paper was actually 1998 (Thanks Brad Appleton for the correction). The papers I reference in this post can all be read from this page: https://lnkd.in/ehVc7Gse #scrum #process #methodology #pattern #framework

213

213 Kommentare

There's 2 ways you can 'use agile' in change management: 1) use agile methods to manage your change work 2) use the agile values and principles to change how you approach change \#1 is easier to start with, so we created a free Minimum Viable Change Framework Miro board here: https://lnkd.in/gy2TfihS #leanchange #agilechange #changemanagement

86

1 Kommentar

𝗘𝗽𝗶𝘀𝗼𝗱𝗲 𝟮𝟲: 𝗦𝗰𝗿𝘂𝗺 𝗦𝗶𝗺𝗽𝗹𝗶𝗳𝗶𝗲𝗱 –  𝗔 𝗩𝗶𝘀𝘂𝗮𝗹 𝗚𝘂𝗶𝗱𝗲 Ever wondered how Agile teams stay focused, adaptive, and aligned? Scrum is more than just sticky notes and stand-ups—it's a structured framework that empowers teams to deliver value iteratively. In this episode, I’ve broken down the essentials of Scrum: ✅ Key roles like Product Owner, Scrum Master & Dev Team ✅ Core events that drive collaboration and reflection ✅ Artifacts that ensure transparency and progress ✅ How Business Analysts add strategic value at every stage Whether you're new to Agile or refining your BA toolkit, this visual guide will help you connect the dots between business goals and technical execution. 🔄 Swipe through the carousel to explore Scrum in action! 💬 Comment below—Which Scrum role resonates most with you? 📌 Follow for more insights on Business Analytics, Agile, and data-driven decision-making. #ScrumExplained #BusinessAnalytics #AgileFramework #BAInAgile #ScrumRoles #AnalyticsMindset #MBAJourney #LinkedInLearning #VisualStorytelling #SwipeToLearn #CareerInTech #RequirementsAnalysis #ProcessOptimization #ThoughtLeadership #ContinuousLearning #BuildInPublic #TechForBusiness #LinkedInCommunity

57

𝐁𝐎𝐀𝐑𝐃𝐑𝐎𝐎𝐌 | 𝐂𝐗𝐎's Leadership 𝐀𝐋𝐄𝐑𝐓: 𝐖𝐇𝐘 𝐈𝐓’𝐒 𝐓𝐈𝐌𝐄 𝐓𝐎 𝐑𝐄𝐈𝐌𝐀𝐆𝐈𝐍𝐄 𝐈𝐓 𝐏𝐑𝐎𝐂𝐔𝐑𝐄𝐌𝐄𝐍𝐓 𝐂𝐡𝐞𝐜𝐤: 𝐀𝐫𝐞 𝐲𝐨𝐮 𝐫𝐮𝐧𝐧𝐢𝐧𝐠 𝐨𝐧 𝐩𝐫𝐨𝐱𝐲 𝐈𝐐 𝐚𝐧𝐝 𝐥𝐨𝐧𝐠 𝐨𝐮𝐭𝐬𝐨𝐮𝐫𝐜𝐢𝐧𝐠 𝐜𝐡𝐚𝐢𝐧𝐬 𝐭𝐡𝐚𝐭 𝐬𝐞𝐞𝐝 𝐝𝐞𝐟𝐞𝐜𝐭𝐬 𝐚𝐧𝐝 𝐫𝐢𝐬𝐤? ❓ 𝐐𝐮𝐞𝐬𝐭𝐢𝐨𝐧: 𝐀𝐫𝐞 𝐰𝐞 𝐚𝐮𝐝𝐢𝐭𝐢𝐧𝐠 𝐬𝐢𝐠𝐧𝐚𝐥𝐬 𝐨𝐫 𝐚𝐝𝐦𝐢𝐫𝐢𝐧𝐠 𝐬𝐥𝐢𝐝𝐞𝐬? Last week over 100 thought leaders agreed: accountability cannot be outsourced forever. Technology isn’t a black box when leadership builds real digital competence. Too many transformations stall because we reward polish over proof. 𝐖𝐡𝐚𝐭 𝐓𝐨 𝐌𝐞𝐚𝐬𝐮𝐫𝐞 ↳  Delivery lineage - who shipped what, when, with commit or ticket IDs ↳  On-call logs - who fixed incidents, Mean Time To Recovery, change fail rate ↳  Team signals - subcontract depth, substitution events, business outcomes A decade of preferred vendor lists to cut costs is backfiring. Too many “preferred” vendors resell through layers. Each layer adds distance, delay, and diluted accountability. By the time you reach the real builder, visibility is gone. Outsourcing depth ≠ digital depth. This is governance failure, not a technology limit. 𝐑𝐞𝐢𝐦𝐚𝐠𝐢𝐧𝐞 𝐏𝐫𝐨𝐜𝐮𝐫𝐞𝐦𝐞𝐧𝐭 ↳ Make delivery lineage mandatory ↳ Tie payment to incident resolution and business outcomes ↳ Cap subcontract depth at one layer ↳ Run live task tests before contract Make one habit non-negotiable: "𝘐 𝘥𝘰 𝘯𝘰𝘵 𝘴𝘪𝘨𝘯 𝘰𝘧𝘧 𝘸𝘪𝘵𝘩𝘰𝘶𝘵 𝘵𝘳𝘪𝘢𝘯𝘨𝘶𝘭𝘢𝘵𝘪𝘯𝘨 𝘭𝘪𝘯𝘦𝘢𝘨𝘦, 𝘭𝘰𝘨𝘴, 𝘢𝘯𝘥 𝘭𝘦𝘢𝘳𝘯𝘪𝘯𝘨𝘴." Which metric will you put on the wall this quarter to keep accountability close to the people who build? Like | Comment | Repost | Follow Babita Evans Kumar MBA #Leadership #DigitalTransformation #TrustCode

227

71 Kommentare