An Interesting post by Chris Sterling on deriving the user stories from the product vision…
If you have ever worked on a project which used Scrum then you may have run into the “blank backlog” issue. Where do we start? Since there are no perfect answers we will need to work this out through experience. I have been using a “Product Backlog filler” exercise with customers which has been refined through these experiences.
When starting a Scrum project it is recommended we begin with a vision. A high level plan of what the product will do from which we can derive a Product Backlog from. I have found that this vision does not have to be written in “stone” (or paper if that is what you use…) but it should be in a form that can be communicated effectively (pictorially on a white board potentially…). A vision is usually followed quite closely by a list of value statements for the consumer of the product. If we can identify the value for our consumers then we have a nice foundation to start driving out user stories from.
Worth Reading it….