Hello everyone!

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.

Image for post
Image for post

From sunk…


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…


Hello everyone!

Welcome to the 280th edition of the Food for Agile Thought newsletter, shared with 30,344 peers.

This week, we discover almost 50 different personality types you may encounter on software teams while managing complexity; we have a personal view on what success to a Scrum Master means, and we learn about the key takeaways from a development team’s transition from Scrum to Basecamp’s Shape Up.

Image for post
Image for post
Food for Agile Thought #280: Managing Complexity, Difficult People on Software Projects, Moving from Scrum to Shape Up, Taking Innovation too far

We then delve into research outlining characteristics of organizations and tasks best suited to Agile. We also talk about chasing innovation, why it needs to be sustainable and the risks of taking it…


TL; DR: Managing Complexity, Difficult People on Software Projects — Food for Agile Thought #280

Welcome to the 280th edition of the Food for Agile Thought newsletter, shared with 30,344 peers. This week, we discover almost 50 different personality types you may encounter on software teams while managing complexity; we have a personal view on what success to a Scrum Master means, and we learn about the key takeaways from a development team’s transition from Scrum to Basecamp’s Shape Up.

We then delve into research outlining characteristics of organizations and tasks best suited to Agile. We also talk about chasing innovation, why it needs to be sustainable and the risks of taking it too far…


Hello everyone!

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.

Image for post
Image for post

Learn more: How to Make Agile Work in Fast-Growing Startups.

Best,
Stefan


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.

Image for post
Image for post

🗞 Shall I notify you about articles like this one? Awesome! You can sign up here for the ‘Food for Agile Thought’ newsletter and join 30,000-plus other subscribers.


Hello everyone!

Welcome to the 279th edition of the Food for Agile Thought newsletter, shared with 30,267 peers.

This week, we look back 20 years at the origins of the Agile Manifesto, why they came together; we detail the difference between Agile vs. Scrum and typical ‘big mistakes,’ and we check a list of five ‘no’ that might come in handy in challenging discussions.

Image for post
Image for post
Food for Agile Thought #279: Agile Manifesto’s History, Amazon’s Invention Machine, User Research 2021 Report, Guide to Saying No

We then listen to insider tales from Amazon — from the need to slow down to innovate to focus on customers’ needs to build by working backward, and we discuss the first principles of continuous discovery…


TL; DR: Agile Manifesto’s History, Amazon’s Invention Machine — Food for Agile Thought #279

Welcome to the 279th edition of the Food for Agile Thought newsletter, shared with 30,267 peers. This week, we look back 20 years at the origins of the Agile Manifesto, why they came together; we detail the difference between Agile vs. Scrum and typical ‘big mistakes,’ and we check a list of five ‘no’ that might come in handy in challenging discussions.

We then listen to insider tales from Amazon — from the need to slow down to innovate to focus on customers’ needs to build by working backward, and we discuss the first principles of continuous discovery. …


Hello everyone!

Garbage in, garbage out: No matter whether your team chose Scrum for the right purpose — solving complex, adaptive problems. No matter whether your Scrum Team’s product quality is top-notch or whether your teammates embrace self-management to the fullest.

If your Product Backlog is not up to the job, all of these accomplishments will account for little, as your team will provide less value to its customers than possible.

Image for post
Image for post

Here is where the forensic Product Backlog analysis steps in, a light-weight, simple practice to help Product Owners and Scrum Masters unearth anti-patterns that led to your low-value Product…


TL; DR: Forensic Product Backlog Analysis

Garbage in, garbage out: No matter whether your team chose Scrum for the right purpose — solving complex, adaptive problems. No matter whether your Scrum Team’s product quality is top-notch or whether your teammates embrace self-management to the fullest. If your Product Backlog is not up to the job, all of these accomplishments will account for little, as your team will provide less value to its customers than possible.

Here is where the forensic Product Backlog analysis steps in, a light-weight, simple practice to help Product Owners and Scrum Masters unearth anti-patterns that led to your low-value Product Backlog.

Learn…

Stefan Wolpers

I have worked for 14-plus years as an Scrum Master, Product Owner, and agile coach. Professional Scrum Trainer (PST) with Scrum.org.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store