by Stefan Wolpers|FeaturedAgile and ScrumAgile Transition
TL; DR: Scrum-to-POM Is Not About Frameworks
Two weeks ago, I asked my audience whether they wanted a short course on moving from Scrum to a Product Operating Model, and 22 answered. That was not the Scrum-to-POM dataset I hoped for, but it was valuable for the conversations. Interestingly, one pattern ran through more than a quarter of the responses: The people writing back were not asking about transformation practices or operating models. They were asking what was about to happen to their jobs.
Let me paraphrase some of their replies: One Agile Coach wrote that their role had already been made redundant, and the internal training their employer offered was not enough. Another asked a blunt question: “What will happen to my role?” A third described leadership, saying they wanted this shift, while their behavior remained inconsistent. A fourth reported confusion about what a product coach actually is. A fifth dismissed the whole discourse as high-level fluff, transformational buzzwords, zero accountability, and vague systems thinking with no teeth.
My takeaway: While the organizational design debate appears to be the surface, the ongoing role repositioning is what the people on the ground are living through.
Agile teams face ethical challenges. However, there is a path to ethical AI in Agile by establishing four pragmatic guardrails: Data Privacy (information classification), Human Value Preservation (defining AI vs. human roles), Output Validation (verification protocols), and Transparent Attribution (contribution tracking).
This lightweight framework integrates with existing practices, protecting sensitive data and human expertise while enabling teams to confidently realize AI benefits without creating separate bureaucratic processes.
Can you rely on pure Scrum to transform your organization and deliver value? Not always. While Scrum excels in simplicity and flexibility, applying it “out of the box” often falls short in corporate contexts due to limitations in product discovery, scaling, and portfolio management.
This article explores the conditions under which pure Scrum thrives, the organizational DNA required to support it, and practical scenarios where it works best—along with a candid look at where it struggles. Discover whether pure Scrum is a realistic approach for your team and how thoughtful adaptation can unlock its true potential.
No other role in Scrum can contribute to mediocre outcomes like the Product Owner—garbage in, garbage out—and it does not matter whether that’s due to incompetence, neglect, disinterest, or failure to collaborate. Moreover, no Product Owner is the “Mini-CEO” of the product, entitled to make lone decisions. Scrum is a team sport; there are no loners in a successful Scrum Team where collaboration and alignment are prerequisites for success.
A Product Owner prone to making lone decisions is in danger of loving their solution over the customers’ problems. Consequently, collaborating and aligning with their teammates on the Product Goal and the Product Backlog is a proven risk-mitigation strategy for Product Owners. This is a testament to Scrum’s built-in checks and balances, particularly now that the product operating model receives more attention.
The Meta-Retrospective is an excellent exercise to foster collaboration within the extended team, create a shared understanding of the big picture, and immediately create valuable action items. It comprises team members of one or several product teams—or a representative from those—and stakeholders. Participants from the stakeholder side are people from the business as well as customers. Meta-Retrospectives are useful both as a regular event, say once a quarter, or after achieving a particular milestone, for example, a specific release of the product.
This post on Scrum team failure addresses three categories from the Scrum anti-patterns taxonomy that are closely aligned: Planning and process breakdown, conflict avoidance and miscommunication, and inattention to quality and commitment, often resulting in a Scrum team performing significantly below its potential.
Learn how these Scrum anti-patterns categories manifest themselves and how they affect value creation for customers and the organization’s long-term sustainability.
This is the third of three articles analyzing the 183 anti-patterns from the upcoming Scrum Anti-Patterns Guide book. The other two articles, see below, address adhering to legacy systems, processes, practices, and communication and collaboration issues.
