Charters, mandates, roadmaps and other artefacts at the launch of a project: Characteristics and similarities
The content presented here represents a little abstract of the article that we published in the journal of modern project management. If you want to consult the article directly, please >>>click here<<<
Ever stood in front of a project you tried to lunch and weren't able to puzzle together all the pieces? Or just another time that a project is executed and the final product does not match with the customers requirements? Or no one knows what her/his responibilities are because it was not properly documented?
Well then it seems like you did not properly initialise and launch your project!
Current problem. Over the last years and decades quite a number of project methodologies established themselves, and all of those methodologies have their own document to initialise a project under different names. Therefore the vocabulary they use is not even the same. Sometimes it is called project mandate, project charter, mission statement, project scope etc. Therefore the aim of our study was to go through recognised project manatement methodologies and document the characteristics and similarities of the artefact they use to initialise a project.
Those are the methodologies we had a closer look at.
Objectives
The objectives we defined as the follwing:- Overview of the different artefacts
- Clarify the characteristics and similarities
- Open a discussion about a more synthetic document
Methods
To gather information and data we had a look at the following domains: System Engineering and Project Management. Inside those domains we went through standards, methodologies and textbooks to create an inventory of artefacts that initialise a project.
Results
Following an inventory created of all the artefacts, and the sections they contained.
