At the start of a project, it’s the responsibility of the Product Owner to work with a group of relevant people to create the Product Vision which outlines the broad goal for the project, and tentative release dates. The Product Vision is required to ensure that everyone involved understands why the project is happening and what the desired outcome is.
The Product Vision is used as a foundation for the product. It’s short – capable of passing the Elevator Test (describing a project to someone within 2 minutes as they travel in an elevator). It describes the critical attributes of the product, who will use or buy it, which customer needs it addresses, the target timeframe and budget. It also gives a comparison to existing products and states the key selling points, but only describes critical information.
The Vision needs to be broad and stable so that it will still be valid as individual requirements change during development, but give a clear goal and focus. This allows people to take a step back at any point and use the Product Vision as a guide to verify that the project has not gone off track by either developing something that doesn’t match the Product Vision, or incorrectly prioritising requirements.
Tags: scrumNo Comments
0 responses so far ↓
There are no comments yet...Kick things off by filling out the form below.