Tag archive for "complexity"

The Highlander Principle

If you grew up as a teenager in the 1980s like me, you are probably familiar with the quote “There can only be one” from the first Highlander movie. Interestingly, this statement is also true for product owners: There should only be one product owner per product. But don’t worry: You don’t have to become an immortal warrior to understand the Highlander principle. Reading this blog post will do the trick.

Read More

Choosing the Right Agile Pilot Project

Fri 1st April 2011

“Which project is best suited to pilot Agile?” is a question I get regularly asked. This blog post discusses the following six criteria that help you select the right agile pilot project: small, important, independent, collocated, software only, and new product development.

Read More

The Definition of Ready in Scrum

Thu 16th December 2010

High-priority product backlog items must be ready to be transformed into working software. Find out what does “ready” means and benefit from Yoda’s advice.
.

Read More



Scaling the Product Owner

The product owner is the person in charge of the product. For products of modest complexity and small projects, it may be feasible to have one individual playing the product owner role. But how do we deal with product ownership on large Scrum projects that develop complex products?This post discusses scaling the product owner role and describes the chief product owner.

Read More