Project Management Stack Exchange is a question and answer site for project managers. It only takes a minute to sign up.
Sign up to join this community
As the Scrum Framework is built interactively, I'd like to know if Scrum offers specific guidelines to define the Vision Document, which is usually defined based on the utmost client need.
How should the Product Owner build up the Vision Document? Is there any defined set of principles to be followed?
Scrum has no rules about how the required documents are created. I've seen mindmaps, vision boards and plain word documents as a basis for the project kickoff.
The PO should consider the audience the document is for. Sometimes it is enough to sketch something on a napkin, other times you might need a full project proposal document.
You might want to read this article (scrumalliance.org) on product vision. It also has a few pointers to some books at the end.
I've found conversations to be most effective. The artifact can be subject to interpretation and later, to debate. Building a relationship and opening a channel for conversation will get the whole process started on the right foot (and keep it there as things change).
I think what people are getting at is there is no one way for a vision document or exercise If you want a vision then it's not just the product owner, it's the whole team to create. Yes the PO will have alot of input but it's a team document.
Johnothan Rasmusson in the Agile Warrior uses the idea of an inception deck. I've used this on previous projects and have to say it's a good way of pulling the team together at the start and really making sure everyone is on the same page.
The article along with a blank inception deck can be found here http://agilewarrior.wordpress.com/2010/11/06/the-agile-inception-deck/
