Read More

Time for a Change in Principles?

As Agilists, our principles and values underpin the way we work and decisions we make. A good principle should be timeless and non-prescriptive enough to be valid across many contexts, but specific enough to add practical value and help us make decisions.

 

I feel that one Agile Manifesto principle in particular has frustratingly failed to stand the test of time:

 


“Working software is the primary measure of progress”


 

I disagree strongly. Working software is only a measure that more software exists, which is not the same thing as progress!

A Scrum Product Owner checklist

After my last post on the role of the Scrum Master I have been asked if I could write a similar role description for the Scrum Product Owner. 

Here’s my view of the role: 
 

The Product Owner

 
The product owner is a visionary who can envision the final product and communicate the vision. 
 
The product owner is also the person who sees the vision through to completion. This includes describing features, collaborating and communicating with the delivery team, accepting or rejecting work results, and steering the project by tracking and forecasting its progress. 
 
The Product Owner points the team at the right target, the Scrum Master helps the team get to the target as efficiently as possible. In other words: The product owner is the what-person, the Scrum team are the how-people.
 

In general the Product Owner …

 

  • is responsible for that the team builds the right product
  • manages ROI and makes sure to deliver business benefits