The Developers Code Fallacy — Making Your Scrum Work #9

TL; DR: The Developers Code Fallacy — They Should Talk to Customers, Too, Though

There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. The Developers Code Fallacy starts with the idea that Developers are rare and expensive and should focus on creating code. Business analysts or customer care agents can talk to customers instead. However, in practice, it has a diminishing effect on a Scrum team’s productivity and creativity. It is a sign for an organization still profoundly stuck in industrial paradigm thinking.

Join me and explore the reasons and the consequences of this Scrum anti-pattern in 110 seconds.

The Developers Code Fallacy — Making Your Scrum Work #9 — Age-of-Product.com
Continue reading The Developers Code Fallacy — Making Your Scrum Work #9

Three Wide-Spread Product Owner Failures in 6:09 Minutes—Making Your Scrum Work #5

TL; DR: Three Wide-Spread Product Owner Failures

There are plenty of Product Owner failures. Given that Scrum is a framework with a precise and concise yet short “manual,” this effect should not surprise anyone.

Explore with me three widespread examples of how Product Owners fail their team in three short video clips, totaling 6 minutes and 9 seconds.

Three Wide-Spread Product Owner Failures in 6:09 Minutes—Making Your Scrum Work #5 — Age-of-Product.com
Continue reading Three Wide-Spread Product Owner Failures in 6:09 Minutes—Making Your Scrum Work #5

Product Discovery Anti-Patterns Leading to Failure

TL; DR: Product Discovery Anti-Patterns

Scrum has proven to be an effective product delivery framework for all sorts of products. However, Scrum is equally well suited to build the wrong product efficiently as its Achilles heel has always been the product discovery part. What product discovery part, you may think now. And this is precisely the point: The Product Owner miraculously identifies what is the best way to proceed as a Scrum Team by managing the Product Backlog. How that is supposed to happen is nowhere described in the Scrum Guide. Consequently, when everyone is for themselves, product discovery anti-patterns emerge.

From sunk costs, HIPPO-ism, my-budget-my-features to self-fulfilling prophecies — learn more about the numerous product discovery anti-patterns that can manifest themselves when you try to fill Scrum’s product discovery void.

Product Discovery Anti-Patterns Leading to Failure — Age-of-Product.com
Continue reading Product Discovery Anti-Patterns Leading to Failure

How to Make Agile Work in Fast-Growing Startups

TL; DR: How to Make Agile Work in Fast-Growing Startups

For years, I worked in several Berlin-based, fast-growing startups in my capacity as Scrum Master, agile coach, and Product Owner. These are my lessons learned on making ‘agile’ — including Scrum as a framework — work in a fast-growing startup. Also, let me introduce you to the anti-patterns agile startups shall avoid at all costs.

How to Make Agile Work in Fast-Growing Startups — Age-of-Product.com
Continue reading How to Make Agile Work in Fast-Growing Startups

Cargo Cult Agile — A Checklist to Open the Discussion

TL; DR: The Cargo Cult Agile Checklist for Download

Do you want to know the state of agility in your organization? Here we go: Download the checklist, distribute it generously among your colleagues, and run a quick poll. It will only take 5 minutes of their time–and then analyze their feedback. If the average number of checkboxes marked is higher than nine, then you are probably practicing cargo cult agile in one form or another.

If running the cargo cult agile survey is the ‘inspection,’ then consider adapting your approach to being agile by kicking-off a discussion among the stakeholders of your organization’s endeavor.

The State of Agile: the cargo cult agile checklist for your organization by Age of Product
Continue reading Cargo Cult Agile — A Checklist to Open the Discussion

Why Agile Turns into Micromanagement

TL;DR: Why Agile Turns into Micromanagement

Agile turns into micromanagement as a result of the middle management’s resistance to change. Despite better knowledge, changing an organization into a learning one that embraces experimentation and failure is not in everybody’s best interest. Self-organizing, empowered teams often conflict with the middle management’s drive to execute personal agendas, self-preservation being one of them.

You guessed right: it is time for a rant and short “checklist” to get the discussion going in your organization.

Agile micromanagement: autonomy, mastery and purpose
Continue reading Why Agile Turns into Micromanagement