Product Owner: Knows what the product is supposed to do. They have the product vision,
and are responsible for communicating this clearly to the Team.
In Scrum this vision is represented as a Product Backlog
This is a prioritized list of User Stories (= Features = Requirements)
that they would like to see in the system.
Example Product Backlog
Product Backlog (Maintained/Updated by Product Owner)
Priority User Story
-------- ----------
1 story 7
2 story 9
3 story 3
4 story 12
5 story 2
A User Story is essentially an atomic feature from the perspective
of a user. It usually captures a single interaction with the system.
Basically, a User Story is a requirement written in the language of the users. Users
should be able to test it to say whether the feature is implemented in the system
or not. This leads to User Acceptance Testing. In Scrum, the template looks like:
Story Name: GIVEN BY PRODUCT OWNER
Priority: GIVEN BY PRODUCT OWNER
Estimate: GIVEN BY TEAM
As a : TYPE OF USER,
I want : TO PERFORM SOME TASK
So that : I CAN ACHIEVE SOME GOAL/BENEFIT/VALUE.