Professional Documents
Culture Documents
This physical Project Book is intended to serve as an "Executive Briefing Book". It should provide key documentation, together with a cross-reference to where the archived documentation is physically located in the project files. If the Project Manager changes over the course of the project, it should be possible for the new Project Manager to briefly walk-through the Project Book and get quickly up to date on all of the key aspects of how the project is being managed and its current status.
3.
Include a brief and easy to read description (one-two pages) of the project. This information could be extracted from the News Release which accompanies a major win, or from the project experience domain in the knowledge base (after the project has been entered).
1.2
Include a completed form defining the project's size, complexity and class. The project class (I, II, or III) is used to determine the applicability of procedures in the Quality Manual. 2. OPEN ACTION ITEMS
This section allows the Project Manager to maintain a readily accessible list of open action items. This should include:
On a large project, these lists should be generated automatically from the tool that is being used to track action items, and updated periodically. Include in this section a copy of the most recent Project Review. 3. 3.1 CUSTOMER ORGANIZATION AND CONTACT LIST Project Organization Chart
Include the standard H-chart which identifies the Acceptor, the Deliverer (i.e., Project Manager), their Line Managers, their executives and the Steering Committee.
3.2
Contact List
Provide a list of the names, titles and phone numbers of the key contacts from the Project Manager's perspective.
3.3
Include a brief summary of the high level strategies and plans for achieving internal and customer objectives.
3.4
Include the most recent minutes from the Steering Committee (i.e., the group of senior customer and delivery management identified on the Project Organization Chart).
3.5
4. 4.1
Include a brief summary of the key contractual requirements in language that can be readily understood by the Project Team.
4.2
Include a completed Contract Management checklist. 5. 5.1 WORK PLANNING Delivery Approach
Include a summary of the delivery strategy and approach, covering the following topics. the customer (one to two paragraphs of descriptive material), the business problem (one to two paragraphs of descriptive material), the customer's critical success factors and how we plan to achieve or exceed them, the technology solution and its competitive aspects, the delivery methodology and its competitive aspects, the risk analysis and risk management approach, key planning assumptions.
5.2
Summary of Estimates
Identify the estimated effort required to deliver each WBS element and include a brief summary of the estimating approach.
5.3
Schedule Summary
Include a high-level schedule identifying the major work components and milestones for the project. Include the schedules for each sub-contractor, as appropriate.
5.4
5.5
Include the minutes of the Peer Review Session, at which the proposed approach to the project was discussed with a group of designated peers who have experience on similar projects. 6. 6.1 FINANCIAL MANAGEMENT Initial Financial Management Plan
Include the initial Financial Management Plan that defines the project management baseline.
Include a current Financial Management Plan that accurately reflects the currently projected financial performance of the project. 7. 7.1 PROJECT ORGANIZATION Project Team Organization Chart
Include a chart that identifies the roles and individuals who make up the delivery team.
7.2
Summarize the staff rotation plan that permits individuals to rotate off the project, or into new roles on the project, in a 12 to 18 month time frame.
7.3
Include the agenda for the initial team meeting which provides a formal orientation to the project/phase.
7.4
Include a completed Project Start-Up Checklist. 8. 8.1 PERFORMANCE MANAGEMENT Monthly Status Report
Include the most recent Monthly Status Reports along with their attachments (e.g., last three months).
8.2
Include the most recent Weekly Status Reports along with their attachments (e.g., last four weeks).
8.3
Include the most recent Weekly Risk Reports along with their attachments (e.g., last four weeks).
8.4
Include the most recent minutes from the regular meetings of the project team.
8.5
Include a completed Process/Performance Management Checklist. 9. 9.1 QUALITY MANAGEMENT Requirements List
9.2
Include the minutes of the audit of the Conceptual Solution, conducted by the Director/Manager of Technology (or designate) before the solution was presented to the customer.
9.3
Include the minutes of the audit of the technical architecture, conducted by the Director/Manager of Technology (or designate) before the solution was presented to the customer.
9.4
10.1 Location of Files Include a table identifying the structure of the Project Library and indicate where the project files are physically located.