Most (software) project management processes recognize the need for an initial high-level definition of what is expected from the project. PMI’s “PMBOK Guide” for example defines a “Project Charter“. On its turn the UP has a “Vision Document” which is very similar.
Very similar but with two important differences:
- Project Charter is business-agnostic, supposed to be usable in any project kind from building construction to off-shore exploration. Hence its Project Charter does not know anything about software development specificity or terminology.
- Vision Document is actually a requirements document (it is not included in the project management artifacts) and thus lacks some important information at this respect.
I long felt the need for an “unification” of both documents, including what is recommended by the PMBOK and what is needed in the context of software development.
The result can be downloaded here: Software Project Chater Template
achillecarette 