10.1.0 Home
The home or banner page for a pm4 project can include;
10.1.1 Project Title <dd:pm kc:wotitle>
10.1.2 Project Summary <dd:pm kc:wosumry>
This is a single paragraph summary of the project, even a single sentance if possible. It is similar to the infamous "elevator pitch" in which "wannabe" entrpreneurs are required to condense their entire concept and rasin d'etre into th etime it take the elevator to make its trip - only it should be true.
10.1.3 Project Number <dd:pm kc:wo>
This is the reference "code" for the project/ work order.
10.2.0 Task Description <dd:pm kc:wodesc>
The task description is a one or two paragraph summary, not a procedure. If formal procedural documents are needed then they should be listed as "deliverables" as noted following. It should be assumed that persons of average skill in the fields required for the task will be using it as their basic instructions of what to do. Care should be taken to avoid overlap with work in other Task Descriptions however, and the task should be interpreted narrowly - i.e.: if work isn't required by the description or its connected procedures then it should not be charged to this task.
10.3.0 Deliverables
The whole purpose of a work order or a project is to produce “deliverables” – some of which may never be actually delivered to anybody and only exist as artefacts. (This does not mean they were a waste of effort and money – artefacts are the necessary, but perhaps less showy, “homework” required to produce the final products which the project owner paid for.) Any work order which produces no “deliverables” should be regarded with suspicion. Any work order which does not clearly define what the deliverable will look like before it is delivered should also be regarded with suspicion. (The person who buys a “car” without specifying what they want, deserves whatever they get. The person who buys a Final Report without saying what they want may similarly get only whatever the author feels like giving them.)
There are a number of essential objects which should exist with each deliverable being specified. These include:
10.3.1 The CDRL item number: <dd:km kc:cdrlitem>
10.3.2 The deliverable’s formal title <dd:km: kc:cdidtitle>
10.3.3 The electronic file name <dd:km: kc:filename>
10.3.4 etc……..<to be continued>
10.4.0 Project Plan
10.5.0 Notes
10.6.0 References
10.7.0 Resources
10.8.0 PreRequisites
10.9.0 Funding