A vision is essential, because it helps the team focus on a common goal. This common objective is easily lost once individuals work on lower level details such as requirements, code, and so on.
Every project should have a vision statement that each stakeholder can understand. The vision statement is helpful to clarify the core values of the project. It should state why a customer or end user will want the solution the project team is building. The shorter the vision statement is, the better it is. A sign of a successful vision statement is that everyone on the project team can relate to it and connect their daily work to it.
Key questions to consider include:
•Why are we building this solution?
•Does the team understand the vision?
•Does the team work on things that contribute to the vision?
Explain that one way to think about vision statements is to consider whether your project is a Strategic project or an Adaptive project.
•Strategic projects involve significant investments based on a plan to improve appreciably over their predecessors.
•Adaptive projects are those that make incremental changes to existing systems.•
A useful way to help derive a vision statement for a strategic project is the "elevator pitch". i.e. you can recite it to a perspective customer or stakeholder in a brief duration of an elevator ride. The stakeholder / customer should be able to remember it from a short encounter.
For adaptive projects, it's often easier to describe the vision in terms of business process change. If a business process model or description is available, that's a good start point.
No comments:
Post a Comment