We’re Not Paid to Practice Scrum, but Answer 5 Product Questions

TL;DR: Cheap Code Makes 5 Product Questions Expensive to Skip

Thesis: This article explains five product questions that become more consequential when AI makes software implementation cheap, why falling AI costs increase the volume of work those questions must filter, and how teams set working principles during early AI adoption.

📺 Watch the article’s video: We’re Not Paid to Practice Scrum — Answer These 5 Product Questions Instead.

For decades, the cost of building software rationed what an organization could start: nobody could afford to build everything, so somebody had to choose, however crudely. AI has weakened that rationing; the frontier labs need your organization to use more AI with every model generation, and the product operating model promises to fix what Agile supposedly broke. None of this guarantees that anyone asks whether the work solves a customer problem, nor whether solving it was worth the cost. You need to address these product questions yourself.

These product questions become more expensive to skip when starting work gets cheap: which problem is worth solving, whether the work is the best use of the team’s time, whether it is good enough for the people who will see it, whether it solved the problem, and whether the team’s way of working still fits. AI agents can prepare evidence under the A3 Framework’s Assist category, where the agent analyzes and people decide, while explicit standards for AI-assisted work, such as the AI Definition of Done, and recurring inspections, such as the AI Delegation Audit, keep the answers honest. Whether you call any of this Scrum is the least interesting question of all.

We're Not Paid to Practice Scrum, but Answer 5 Product Questions: When AI makes software implementation cheap - Age-of-Product.com
Continue reading We’re Not Paid to Practice Scrum, but Answer 5 Product Questions

Should We Change Scrum?

TL; DR: Can We Or Should We Change Scrum?

Can we or should we change Scrum, or is it a sacrilege to tweak the ‘immutable’ framework to accommodate our teams’ and organizations’ needs?

Not so fast; don’t just dismiss augmenting Scrum as leaving the path, contributing to the numerous Scrumbut mutations, giving Scrum a bad name. However, in our rapidly evolving business landscape, sticking rigidly to traditional Scrum by the book could be a straightjacket stifling innovation, user focus, and adaptability.

From ensuring cultural compatibility to facing technical debt challenges and emerging technologies, discover ten compelling reasons why augmenting Scrum isn’t just okay—it’s necessary for modern teams.

Read on to discover when and how to adapt Scrum responsibly without diluting its essence.

Should We Change Scrum? Age-of-Product.com
Continue reading Should We Change Scrum?

Retrospective Facilitation: A Simple Hack to Go from Good to Great

TL; DR: Retrospective Facilitation — Going from Good to 🦄 Great

The magic technique to turn a boring Retrospective into an outstanding Retrospective is the rotation of the facilitator role equally among all team members. Check out the following ten benefits of this Retrospective facilitation practice, from boosting learning and skill development to ensuring continuity to encouraging ownership.

Retrospective Facilitation: A Simple Hack to Go from Good to Great — Age-of-Product.com
Continue reading Retrospective Facilitation: A Simple Hack to Go from Good to Great

The Three Daily Scrum Questions Won’t Die — Making Your Scrum Work (29)

TL; DR: The Three Daily Scrum Questions Won’t Die

The Daily Scrum serves a single purpose: inspecting the progress toward the Sprint Goal by reflecting on yesterday’s learning. Then, if the need should arise, the Developers adapt their plan to accomplish the Sprint Goal. While the theory may be generally accepted, applying the idea to the practice is more challenging. One of the recurring issues is the continued popularity of the “three Daily Scrum questions” from the Scrum Guide 2017.

Let’s reflect on why answering these obsolete Daily Scrum questions negatively influences the Scrum team.

The Three Daily Scrum Questions Won’t Die — Making Your Scrum Work (29) — Age-of-Product.com
Continue reading The Three Daily Scrum Questions Won’t Die — Making Your Scrum Work (29)

Your Unfit Product Goal and the Product Goal Canvas — Making Your Scrum Work (28)

TL; DR: Your Unfit Product Goal and the Product Goal Canvas

We plan a lot in Scrum: There is a daily plan when the Developers think about progressing toward the Sprint Goal during the Daily Scrum. Of course, the Sprint Goal reflects an intermediate target the Scrum team considers valuable to solve their customers’ problems. Moreover, there is the Product Goal, a mid- or long-term objective of the Scrum team.

The problem is that when Scrum teams already struggle with embracing the concept of the Sprint Goal—first, you agree on the objective of the Sprint, then you pick the work you consider necessary to accomplish it—they most likely also struggle with proper Product Goals.

Let’s check three critical issues Scrum teams have with Product Goals and a practical tool that helps you avoid the mess.

Your Unfit Product Goal and the Product Goal Canvas — Making Your Scrum Work (28) — Age-of-Product.com
Continue reading Your Unfit Product Goal and the Product Goal Canvas — Making Your Scrum Work (28)

Agile Micromanagement — Seriously? Making Your Scrum Work #27

TL; DR: Agile Micromanagement

There are plenty of failure possibilities with Scrum. Indeed, given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. For example, the Scrum Guide clearly states the importance of self-management at the Scrum team level. Nevertheless, the prevailing cause of many messed-up attempts to use Scrum result from what I call agile micromanagement, a pseudo-commitment to agile principles only to be overridden whenever it seems beneficial from a stakeholder’s or manager’s perspective.

Join me and delve into the importance of self-managing Scrum teams in less than two minutes.

Agile Micromanagement — Making Your Scrum Work #27 — Age-of-Product.com
Continue reading Agile Micromanagement — Seriously? Making Your Scrum Work #27