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?

  • 2
    Hi, welcome to PMSE, the site for expert and enthusiast PM's. Consider giving more detail in your question so that it targets your unique situation. Scrum is oftentimes handled quite differently from organization to organization, and having specifics will make sure that you don't get plain, vanilla, academic answers that can be found on Google. :)
    – jmort253
    Mar 11, 2012 at 21:11
  • Thanks for your reply, when the Product owner get the project what artifact he uses to develop the vision? he write a document on doc file? the problem is when talk about vision I think in vision document used in RUP.
    – Meth0d
    Mar 11, 2012 at 21:25
  • Again, I personally think it depends on the details of your situation. If you're looking for pure academic answers you can probably find them on Google, but if you have a specific project you're referencing, you're likely to get better answers if you edit your question with more detail about your situation. :) Also, we're not a product-recommending site, but we do have some historical questions where people asked for book recommendations: pm.stackexchange.com/questions/2114/resources-for-scrum
    – jmort253
    Mar 11, 2012 at 21:28
  • scaledagileframework.com/vision is a good place to start. Jun 10, 2014 at 19:04

3 Answers 3


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/

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.