Abstract/Description

When people learn about agile they usually learn about Scrum (since it is the most popular flavor of agile). While Scrum is beneficial, it does not have answers to all the challenges of software development. One of the common challenges teams face is that of having an effective Product Owner. From experience, it is not about who is fulfilling the role of the Product owner in your organization but about the definition of the role itself. We have played with many different variations of the PO role, till we ended up with the concept and structure of the Value Team. To keep it simple, the Value Team is responsible for making sure the product is (1) Feasible, (2) Valuable, (3) Useable. After using Value Teams in many corporations (the session will have many real-life examples of this) they seems to be a practical solution to many problems about how agile can work in complex environments where there is no ONE product owner, but rather multiple organizations and people that have a say in what needs to get build and how. This session will present the idea of Value teams and answer questions on how to create them, how they operate, who is in charge, and why they are so critical to the success of the agile delivery team.

You must be a Subscriber to view this post and you are currently not logged in.

You can either log in below or sign up here.