Incorporating Learning and Expected Cost of Change

Incorporating Learning and Expected Cost of Change

Product owners are typically asked to prioritize based on the nebulous term “business value.” But what, exactly, does that mean? As a product owner or agile product manager, you need some straightforward advice to help you balance all the competing needs of your business.

These slides from agile expert and author Mike Cohn introduce three guidelines you can use to help prioritize features. Learn how expected cost of change, useful knowledge, and learning gained from working software influence prioritization on agile projects.

XP Finland 1 hour Download