Credit: FreelandBuck |
The 46 core templates are divided into two groups, Basic (18 templates) and Advanced (28 templates). Basic templates define the core set of processes all project managers need to understand.
Advanced templates focus on more complex project governance, work breakdown structure, scheduling, performance reporting, and program management issues. To learn more about the Basic templates, go here.
- Project governance: This template provides a record of how decisions are made on the project. #HR
- Human resource plan: Lists number of people, HR category, and schedule for personnel assigned to the project. It is details roles and responsibilities, facilities required by personnel, team development, training sessions and other team-related activities. #HR
- Product breakdown: A description of work products, by hierarchy of components and constituent parts.#Scope
- Project schedule: The timeline for the project. Defines organizational unit milestones, start and finish dates, interdependencies between organizational units, and which unit is responsible for which work products. Presented in a phased task and activities format. Encompasses entire scope of the project.#Time
- Work breakdown: Describes work to be completed, by hierarchy, from the level of an individual worker’s daily task to the team level work products to the project level milestones. #Scope
- Contract: A contract is a mutually binding agreement between parties to provide goods, services, or results in exchange for some form of payment. There may be more than two parties involved to a Contract.
- Vendor review: Details how suppliers were selected. Includes selection criteria and results of selection process. #Procurement
- Procedures log: Describes procedures followed to complete the project work, either directly or points to where the procedures are found. #Quality
- Quality plan: Describes how the project team will ensure that all deliverables or work products will meet the required quality standards. #Quality
- Infrastructure plan: Describes the technical environment structure and how to implement it, including timelines. #Integration
- Communications plan: Describes how communications will occur throughout the project, including who is involved (stakeholders), what content is to be presented, what medium will be used (meeting or e-mail, for example), how often it will be communicated, and when it will be communicated. #Communications
- Infrastructure review: Assesses the effectiveness of the technical environment and identifies means of enhancement or improvement. #Integration
- Operational schedule: A breakdown of the work by organizational unit into a timeline detailing the work packages and corresponding work items. Details individuals responsible for the work and resources required. #Time
- Contact list: A directory of how to contact various project resources and personnel. May include telephone, email, and address information. #HR
- Staff list: Basic personnel data for assigned members of the project team. #HR
- Staff schedule: Detailed availability information for assigned project personnel. #HR
- Asset tracking: A list of all physical resources assigned to the project, and who they are assigned to.#Procurement
- Team charter: Defines operational guidelines team will follow. Presented to the project team at commencement of project, usually at the “kickoff” meeting. Also presented to new members as they join the team. #Integration
- Individual status: Periodically statuses an individual’s project contributions, as required by the Communication plan. #Communications
- Contractor status: Periodically statuses an contractor’s project contributions, as required by the Communication plan. #Communications
- Meeting forms: Collects information to organize a meeting and record the results of a meeting.#Communications
- Expense tracking: Records all expenditures of the project. Entries include expenditure type, amount, date, authorized agent, reference to budget items, and approval authentication (if required). #Cost
- Event tracking: Notable events and constraints requiring later reference or analysis. #Communications
- Risk occurrence: Records risks as they occur. Links to action control documents used to respond to the risk. #Risk
- Situation review: Contains preparation documents for a situation analysis, the situation analysis, and resulting reports. #Integration
- Correspondence log: Records all important communications and information broadcasts that occur during the project lifetime. #Communications
- Project closure: Summarizes project and lessons learned. Identifies materials that may be reused.#Quality
No comments:
Post a Comment