• The Business Case is the chapter that defines why the project is needed.

  • Current Situation

  • Problem

  • Vision

  • Options

  • Benefits

  • The Project Scope is the chapter that defines what the project will produce.

  • Scope

  • Out of Scope

  • Solution

  • People and Roles

  • Quality Criteria

  • Standards

  • Risks

  • The Project Planning is the chapter that defines how/when we intend to do the project.

  • Process

  • Milestones

  • Dependencies

  • Assumptions

  • Change Management

  • To understand the project, every participant needs to understand how things are working now.

  • Make it clear to everyone that you really understand why the project is needed, and what the problem is in the current situation.

  • All stakeholders in the project need to be aligned so that they share the same vision of the future product.

  • Document why a certain direction was chosen, and from which available options.

  • Make sure that everyone has the same idea of business value for the customer.

  • Define, in broad terms, the size of the project by explaining what activities you will perform, and for how long.

  • It’s also very important to mention explicitly what you will not do, so that there will be no misunderstandings.

  • Give the customer an idea of the (sub)systems you will be delivering, without details, on the highest possible level.

  • Name the stakeholders and their roles and responsibilities in the project. Make sure that everyone knows who can take which decisions.

  • Name any quality requirements that are applicable, and assign priorities in case of conflicts among the qualities (like performance vs. security).

  • Name any technological standards and business standards applicable to the product.

  • Be sure to mention any risks, so that any re-planning (when some of the risks turn into real problems) doesn’t come as a surprise later.

  • Mention the process you will apply, either by referring to a defined method (like Scrum) or to a document describing your own custom process.

  • Name any specific dates and (if known at this stage) what you expect to be delivering. Regular iterations/releases might be mentioned here.

  • Name any dependencies, like the involvement of third parties, that are beyond your own direct control.

  • Make any assumptions explicit, like the availability of a customer stakeholder, or the availability of graphic designs.

  • Define how you’re going to cope with changes during the project. This is part of the defined process, but it deserves to be mentioned explicitly.

{"cards":[{"_id":"4f0c4335cd82521589000046","treeId":"4f0c42d9cd82521589000044","seq":1503666,"position":1,"parentId":null,"content":"# Vision and Scope Document"},{"_id":"4f0c650acd82521589000072","treeId":"4f0c42d9cd82521589000044","seq":1503735,"position":1,"parentId":"4f0c4335cd82521589000046","content":"*taken from: http://www.noop.nl/2008/05/how-to-create-a-pre-project-document.html*"},{"_id":"4f0c6aafcd82521589000075","treeId":"4f0c42d9cd82521589000044","seq":1503740,"position":2,"parentId":"4f0c4335cd82521589000046","content":"the notes in *italics* are meant to be deleted."},{"_id":"4f0c4492cd82521589000047","treeId":"4f0c42d9cd82521589000044","seq":1503670,"position":2,"parentId":null,"content":"# Business Case"},{"_id":"4f0c451ccd82521589000048","treeId":"4f0c42d9cd82521589000044","seq":1503671,"position":1,"parentId":"4f0c4492cd82521589000047","content":"*The Business Case is the chapter that defines why the project is needed.*"},{"_id":"4f0c4b4ccd82521589000049","treeId":"4f0c42d9cd82521589000044","seq":1503673,"position":2,"parentId":"4f0c4492cd82521589000047","content":"## Current Situation"},{"_id":"4f0c4baecd8252158900004a","treeId":"4f0c42d9cd82521589000044","seq":1503674,"position":1,"parentId":"4f0c4b4ccd82521589000049","content":"*To understand the project, every participant needs to understand how things are working now.*"},{"_id":"4f0c4c7ccd8252158900004b","treeId":"4f0c42d9cd82521589000044","seq":1503675,"position":3,"parentId":"4f0c4492cd82521589000047","content":"## Problem"},{"_id":"4f0c4cf7cd8252158900004c","treeId":"4f0c42d9cd82521589000044","seq":1503676,"position":1,"parentId":"4f0c4c7ccd8252158900004b","content":"*Make it clear to everyone that you really understand why the project is needed, and what the problem is in the current situation.*"},{"_id":"4f0c4d9dcd8252158900004d","treeId":"4f0c42d9cd82521589000044","seq":1503678,"position":4,"parentId":"4f0c4492cd82521589000047","content":"## Vision"},{"_id":"4f0c4e2fcd8252158900004e","treeId":"4f0c42d9cd82521589000044","seq":1503680,"position":1,"parentId":"4f0c4d9dcd8252158900004d","content":"*All stakeholders in the project need to be aligned so that they share the same vision of the future product.*"},{"_id":"4f0c4eb4cd8252158900004f","treeId":"4f0c42d9cd82521589000044","seq":1503682,"position":5,"parentId":"4f0c4492cd82521589000047","content":"##Options"},{"_id":"4f0c4ee7cd82521589000050","treeId":"4f0c42d9cd82521589000044","seq":1503685,"position":1,"parentId":"4f0c4eb4cd8252158900004f","content":"*Document why a certain direction was chosen, and from which available options.*"},{"_id":"4f0c5005cd82521589000051","treeId":"4f0c42d9cd82521589000044","seq":1503686,"position":6,"parentId":"4f0c4492cd82521589000047","content":"##Benefits"},{"_id":"4f0c5048cd82521589000052","treeId":"4f0c42d9cd82521589000044","seq":1503688,"position":1,"parentId":"4f0c5005cd82521589000051","content":"*Make sure that everyone has the same idea of business value for the customer.*"},{"_id":"4f0c50e5cd82521589000053","treeId":"4f0c42d9cd82521589000044","seq":1503689,"position":3,"parentId":null,"content":"#Project Scope"},{"_id":"4f0c5148cd82521589000054","treeId":"4f0c42d9cd82521589000044","seq":1503691,"position":1,"parentId":"4f0c50e5cd82521589000053","content":"*The Project Scope is the chapter that defines what the project will produce.*"},{"_id":"4f0c51bfcd82521589000055","treeId":"4f0c42d9cd82521589000044","seq":1503692,"position":2,"parentId":"4f0c50e5cd82521589000053","content":"##Scope"},{"_id":"4f0c522acd82521589000056","treeId":"4f0c42d9cd82521589000044","seq":1503694,"position":1,"parentId":"4f0c51bfcd82521589000055","content":"*Define, in broad terms, the size of the project by explaining what activities you will perform, and for how long.*"},{"_id":"4f0c5306cd82521589000057","treeId":"4f0c42d9cd82521589000044","seq":1503696,"position":3,"parentId":"4f0c50e5cd82521589000053","content":"##Out of Scope"},{"_id":"4f0c532ecd82521589000058","treeId":"4f0c42d9cd82521589000044","seq":1503697,"position":1,"parentId":"4f0c5306cd82521589000057","content":"*It's also very important to mention explicitly what you will not do, so that there will be no misunderstandings.*"},{"_id":"4f0c541ecd82521589000059","treeId":"4f0c42d9cd82521589000044","seq":1503698,"position":4,"parentId":"4f0c50e5cd82521589000053","content":"##Solution"},{"_id":"4f0c5466cd8252158900005a","treeId":"4f0c42d9cd82521589000044","seq":1503699,"position":1,"parentId":"4f0c541ecd82521589000059","content":"*Give the customer an idea of the (sub)systems you will be delivering, without details, on the highest possible level.*"},{"_id":"4f0c553ccd8252158900005b","treeId":"4f0c42d9cd82521589000044","seq":1503701,"position":5,"parentId":"4f0c50e5cd82521589000053","content":"##People and Roles"},{"_id":"4f0c5705cd8252158900005c","treeId":"4f0c42d9cd82521589000044","seq":1503702,"position":1,"parentId":"4f0c553ccd8252158900005b","content":"*Name the stakeholders and their roles and responsibilities in the project. Make sure that everyone knows who can take which decisions.*"},{"_id":"4f0c57c6cd8252158900005d","treeId":"4f0c42d9cd82521589000044","seq":1503703,"position":6,"parentId":"4f0c50e5cd82521589000053","content":"##Quality Criteria"},{"_id":"4f0c5833cd8252158900005e","treeId":"4f0c42d9cd82521589000044","seq":1503704,"position":1,"parentId":"4f0c57c6cd8252158900005d","content":"*Name any quality requirements that are applicable, and assign priorities in case of conflicts among the qualities (like performance vs. security).*"},{"_id":"4f0c5955cd82521589000060","treeId":"4f0c42d9cd82521589000044","seq":1503707,"position":7,"parentId":"4f0c50e5cd82521589000053","content":"##Standards"},{"_id":"4f0c59b8cd82521589000061","treeId":"4f0c42d9cd82521589000044","seq":1503709,"position":1,"parentId":"4f0c5955cd82521589000060","content":"*Name any technological standards and business standards applicable to the product.*"},{"_id":"4f0c5a1bcd82521589000062","treeId":"4f0c42d9cd82521589000044","seq":1503710,"position":8,"parentId":"4f0c50e5cd82521589000053","content":"##Risks"},{"_id":"4f0c5a3fcd82521589000063","treeId":"4f0c42d9cd82521589000044","seq":1503711,"position":1,"parentId":"4f0c5a1bcd82521589000062","content":"*Be sure to mention any risks, so that any re-planning (when some of the risks turn into real problems) doesn't come as a surprise later.*"},{"_id":"4f0c5b0bcd82521589000064","treeId":"4f0c42d9cd82521589000044","seq":1503712,"position":4,"parentId":null,"content":"#Project Planning"},{"_id":"4f0c5b2bcd82521589000065","treeId":"4f0c42d9cd82521589000044","seq":1503716,"position":1,"parentId":"4f0c5b0bcd82521589000064","content":"*The Project Planning is the chapter that defines how/when we intend to do the project.*"},{"_id":"4f0c5d2ecd82521589000066","treeId":"4f0c42d9cd82521589000044","seq":1503718,"position":2,"parentId":"4f0c5b0bcd82521589000064","content":"##Process"},{"_id":"4f0c5d9acd82521589000067","treeId":"4f0c42d9cd82521589000044","seq":1503719,"position":1,"parentId":"4f0c5d2ecd82521589000066","content":"*Mention the process you will apply, either by referring to a defined method (like Scrum) or to a document describing your own custom process.*"},{"_id":"4f0c5df9cd82521589000068","treeId":"4f0c42d9cd82521589000044","seq":1503720,"position":3,"parentId":"4f0c5b0bcd82521589000064","content":"##Milestones"},{"_id":"4f0c5e7ccd82521589000069","treeId":"4f0c42d9cd82521589000044","seq":1503722,"position":1,"parentId":"4f0c5df9cd82521589000068","content":"*Name any specific dates and (if known at this stage) what you expect to be delivering. Regular iterations/releases might be mentioned here.*"},{"_id":"4f0c5ee2cd8252158900006a","treeId":"4f0c42d9cd82521589000044","seq":1503723,"position":4,"parentId":"4f0c5b0bcd82521589000064","content":"##Dependencies\n"},{"_id":"4f0c5f2ecd8252158900006b","treeId":"4f0c42d9cd82521589000044","seq":1503724,"position":1,"parentId":"4f0c5ee2cd8252158900006a","content":"*Name any dependencies, like the involvement of third parties, that are beyond your own direct control.*"},{"_id":"4f0c5fa4cd8252158900006c","treeId":"4f0c42d9cd82521589000044","seq":1503726,"position":5,"parentId":"4f0c5b0bcd82521589000064","content":"##Assumptions"},{"_id":"4f0c5fd8cd8252158900006d","treeId":"4f0c42d9cd82521589000044","seq":1503727,"position":1,"parentId":"4f0c5fa4cd8252158900006c","content":"*Make any assumptions explicit, like the availability of a customer stakeholder, or the availability of graphic designs.*"},{"_id":"4f0c6058cd8252158900006e","treeId":"4f0c42d9cd82521589000044","seq":1503728,"position":6,"parentId":"4f0c5b0bcd82521589000064","content":"##Change Management\n"},{"_id":"4f0c60e6cd82521589000070","treeId":"4f0c42d9cd82521589000044","seq":1503731,"position":1,"parentId":"4f0c6058cd8252158900006e","content":"*Define how you're going to cope with changes during the project. This is part of the defined process, but it deserves to be mentioned explicitly.*"}],"tree":{"_id":"4f0c42d9cd82521589000044","name":"Pre-Project Document template","publicUrl":"4f0c42d9cd82521589000044"}}