In agile development, the term vision is often used. A vision can be said to be the starting point, the motive and the goals that must be achieved when a project is completed and the result from the project delivers full benefit.
But wait, is not this what is usually called effect goals in projects? Both yes and no. The project's vision can, according to ProjektStegen to be added, be said to be an overall and broad description of the current situation, needs, solution ideas expressed at the operational level and what needs are to be met and who has the needs.
The effect goals quantify the effects the business is to achieve by using the project's deliveries. The effect goals must be concrete, measurable and each desired effect goal must have a target value that is followed up and evaluated. The effect goals together must be in line with the vision.
Short & hearty
A vision must be concise and concise, at the same time it must be simply designed so that everyone involved really understands the motive and the expected result when implementing the project.
There are different ways to describe a vision. Sometimes the concept is linked elevator message (English elevator pitch) together with how a vision should be expressed. This means that the vision should be able to explain the project in a short period of time, such as a one-minute elevator ride. The starting point is that whoever gets the vision presented to them gets answers to the questions why? to whom? how? benefits?
Watch a short film that shows five parts and dimensions that a vision can contain:
Your project is vision
We have saved the best in the end, namely that there is no standard or uniform way of describing a vision. It can be said to be in line with agile development in general, ie that there may be guidelines for how this part of the project can be done, but it is up to each project to choose how the guidelines are to be used in a way that suits the individual project. The principle that the vision must be positive, visionary and contain challenging goals and expectations is often mentioned. We support that principle at ProjektStegen, but at the same time want to emphasize that unrealistic goals can lead to increased risks of disappointment and negative stress.
Needs in focus
Another thing to keep in mind when designing a vision is that it is the needs that should be in focus, not functions and requirements. A vision can contain ideas for solutions, but then they must be on an overall level without details. The vision is a document that the business designs.
Do you have tips, ideas or thoughts on how a vision can be designed? Do you agree with our description of a vision or do you have other experiences of how the vision can be designed to be a good start to a project? Feel free to comment!