INDIVIDUAL TEMPLATES

Welcome to MYPROJECT ROADMAP Individual Template Solutions page!

Please CLICK on this symbol to collapse the listing of templates in each category.

Come again soon!
 
PRODUCTS
     Comprehensive Solution
    • 20065470 MYPROJECT ROADMAP Comprehensive Suite $99.00
      MYPROJECT ROADMAP™ is a suite of over 60 professionally packaged template solutions to implement and integrate industry best practice throughout the complete project lifecycle. MYPROJECT ROADMAP™ is a comprehensive business solution for your project which integrates the PMBOK (Project Management Body of Knowledge Guide®, Third Edition), the industry best practice in the field of Project Management, and Knowledge Management all into one powerful integrated solution.
       

       
     Initiating
    • 20059702 Project Initiation Overview $4.95
      The Project Initiating Process Group Overview is used to understand the characteristics of this phase and delineate the type of activities involved in this beginning phase of the project. It is created as part of the Develop Project Charter activity.
       

       
    • 20059703 Project Initiation Checklist $7.95
      The Project Initiating Checklist is used to ensure that all important aspects of initiating a project are considered. This checklist serves as an input (historical information) to new projects in preparation for project initiation activities.
       

       
    • 20059704 Project Feasibility Study $12.95
      The Project Feasibility Study is created in the Initiating Process Group. The Project Feasibility Study provides an overview of the prevalent issues related to a proposed business objective. The purpose of the study is to identify and analyze the critical factors that can assist or hinder the success of a potential business objective.
       

       
    • 20059705 Project Business Case $12.95
      The Business Case document is created in the Initiating Process Group. It is created as part of the Develop Project Charter activity. At various levels of planning, the business case document can be used as a basis for a decision on whether to cancel or proceed with a project, provide direction to the project manager, and provide upfront risk assessment for a project prior to the launch of a project.
       

       
    • 20059706 Product Description $12.95
      The Product Description is created in the Initiating Process Group. It is created as part of the Develop Project Charter activity. Generally, this document contains less detail in the early phases of the project. As the project progresses, the project/product scope is refined and updated.
       

       
    • 20059707 Project Charter $12.95
      The Project Charter document formally authorizes the project and provides the project manager the authority to apply resources to the project. A project manager external to the performing organization typically writes the Project Charter. The Project Charter is one of three outputs in the Initiation process of a project.
       

       
    • 20059708 Project Review Checklist $7.95
      The Project Review checklist is used to ensure that all important aspects of the project are reviewed to determine whether or not the project should continue to the next phase. Project reviews are useful to identify risks and issues, review key deliverables, and determine the project's overall health (status).
       

       
    • 20059709 Project Review Summary $10.95
      The Project Review Summary is created in the Initiating Process Group. It is created as part of the Develop Preliminary Project Scope Statement activity. This document is used to capture critical information about a project which helps determine the overall stability and performance of the project effort. The Project Review Summary contains key sections to document information that is germane to that particular project as well as contains a section where the overall disposition of the project can be assessed and documented as part of the project record.
       

       
     Planning
    • 20060709 Project Planning Overview $4.95
      The Project Planning Process Group Overview is used to understand the characteristics of this process group and delineate the type of activities performed.
       

       
    • 20060710 Project Planning Checklist $7.95
      The Project Planning Checklist is used to ensure all necessary steps to properly plan a project. This checklist will serve as an input (historical information) to new projects in preparation for project planning activities.
       

       
    • 20060711 Project Management Plan $12.95
      The Project Management Plan is a formal document used to manage the execution of the project. It integrates the outputs of other planning processes including, but not limited to, all of the subsidiary management plans by creating a comprehensive document. The Project Management Plan is expected to change over the life span of the project.
       

       
    • 20060712 Project Scope Statement Form $10.95
      The Project Scope statement provides a basis for future decision-making by defining the baseline scope of the project given the known constraints and assumptions. The Product Description is a feeder document to the Project Scope Statement because it contains the Project s Justification, deliverables, and objectives.
       

       
    • 20060713 Project Scope Management Plan $12.95
      The Scope Management plan defines how changes to the project/product scope will be identified, managed, and controlled. It also identifies the necessary approval levels needed to authorize a change to the project/product scope, such as a Project Change Control Board.
       

       
    • 20060714 Project Work Breakdown Structure List $8.95
      The Project Work Breakdown Structure List comprises the project's master list of deliverables (tangible and intangible) defined in the Scope Definition Process. The Project Work Breakdown Structure List is a document that shows all of the deliverables at the work-package level that will be produced at the end of the project. It can also be graphically depicted to illustrate the relationship between deliverables across the project.
       

       
    • 20060715 Project Work Breakdown Structure Dictionary $8.95
      The Work Breakdown Structure Dictionary is used to provide detail information for each work breakdown structure identified in the project scope and schedule. The Work Breakdown Structure will contain detail description of the task, Predecessor tasks, Successor tasks, duration, cost, resource allocation and Risk information.
       

       
    • 20060716 Project Activity List $8.95
      The Activity List is used to list all of the activities needed to complete the project. Similar to the Scope Definition Process, the Activity List should list the activity required, and only the work required, to complete the project. The Project team should utilize this document as a cross-reference to the work breakdown structure.
       

       
    • 20060717 Project Risk Management Plan $12.95
      The Risk Management Plan describes the manner in which the project team will identify, qualify, quantify, and mitigate risks on the project. The Risk Management plan has several major components including Methodology, Roles and Responsibilities, Budget, Scoring and Interpretation, Thresholds, Reporting, and Tracking.
       

       
    • 20060718 Project Risk Identification Form $10.95
      The Risk Identification Form is used to Identify risks for the project and determine which risks might affect (positively or negatively) the project. This form helps the project team document the risks characteristics, denote a Risk Contingency Plan, Risk Fallback Plan. The Risk Fallback Plan details an approach to address a risk event if the Risk Contingency Plan is ineffective.
       

       
    • 20060719 Project Issue Identification Form $7.95
      The Project Issues Identification Form is used to document all issues that arise in the project. It is created as part of the Risk Identification activity. Once an issue is defined as a risk, the project team will use this form as a baseline in creating the Risk identification form.
       

       
    • 20060720 Project Risk Register & Issues Log $8.95
      The Project Risk Register & Issues Log is used throughout the life of the project's lifecycle.It is created as part of the Risk Identification activity. The Project Risk Register and Issues Log are created as part of the Risk Identification activity. Every identified risk and issue should be catalogued in this document for continued project team review. All risks and issues should be managed in accordance to the Project Risk Management Plan. During the Risk Response Planning activity, additional information, including a Risk mitigation strategy is updated by the project team.
       

       
    • 20060721 Project Quality Management Plan $12.95
      The Quality Management Plan is describes how the project teams will implement the projects and/or organizations quality policy on the project. The Quality Management plan should list how the project team plans to address quality assurance and quality improvements on the project. It is used as a feeder document to a number of other project planning processes, including, but not limited to, Project Management Plan development.
       

       
    • 20060722 Project Cost Management Plan $12.95
      The Project Cost Management Plan is created as part of the cost estimating process to document the activities, and their related criterion, to properly plan, structure, and control cost across all project resources (material, services, personnel-labor, facilities. As change requests are approved, the Project Cost Management Plan is also updated to incorporate the changes that have a significant influence on project costs.
       

       
    • 20060723 Project Procurement Management Plan $12.95
      The Procurement Management Plan represents an action plan to be followed throughout the procurement process to acquire and evaluate the services and products (deliverables) from a seller. The decision to acquire services or products from a seller is often directly related to the project team's Risk Mitigation Strategy
       

       
    • 20060724 Request For Proposal (RFP) $12.95
      The Request for Proposal (RFP) is created by the Buyer to document a need to acquire services or products from a Seller. This document is considered to be a solicitation from a Buyer to a prospective Seller.
       

       
    • 20060725 Project Change Control Management Plan $12.95
      The Project Change Control Management Plan is used to define the project team's methodology to manage changes to the project/product scope on the project. Given that changes to one of the triple threats (Scope, Quality, Time, Cost, Customer satisfaction) can potentially impact one another, the project team should develop an overall methodology and approach to changes across all integration points within the projects.
       

       
    • 20060726 Project Communication Management Plan $12.95
      The Communication Management Plan defines the project team's methodology for collecting, distributing, and managing the overall disposition of information on the project. This management plan defines the filing structure and methods used to gather, organize, store project information.
       

       
    • 20060727 Project Communication Management Plan Matrix $8.95
      The Communication Management Plan Matrix is a combination of a traditional Responsibility Assignment Matrix and a Communication Requirement Form. The Project Communication Management Plan Matrix is used to align project team member roles delineate responsibilities (approver, reviewer, developer, etc) against deliverables defined in the Work Breakdown Structure for the project
       

       
    • 20060728 Project Glossary Notebook $12.95
      The Project Glossary Notebook is used throughout the life of the project s lifecycle. It is created as part of the Acquire Project Team activity. The purpose of this document is to list all of the key terms used on the project team. The project team uses this document to create a common language.
       

       
    • 20060729 Project Roles & Responsibilities Notebook $8.95
      The Project Roles and Responsibilities Notebook are created in the Planning Process Group. It is created as part of the Acquire Project Team activity. This notebook is used to help delineate the tasks and decision-making responsibilities that stakeholders have on a given project.
       

       
    • 20060730 Project Team Directory $8.95
      The Project Team Directory is used to define how the resources are assigned to the project, Project Team Directory delineates their roles, placeholder names and other contact information. Based on your project's requirements, this document can be either very detailed or more broadly structured to cover, at a high level, all of the project Stakeholders.
       

       
    • 20060731 Project Team Member Job Description Form $10.95
      The Project Team Member Job Description Form is used to describe the general nature of each team member's duties and responsibilities. This form is not an exhaustive list on responsibilities on the team, but rather serves as an overview of the duties, deliverables, and responsibilities within particular role/position.
       

       
     Executing
    • 20061732 Project Executing Overview $4.95
      The Project Executing Process Group Overview is used to understand the characteristics of this process and delineate the type of activities involved. It is created as part of the Direct and Manage Project Execution activity.
       

       
    • 20061733 Project Executing Checklist $7.95
      The Project Executing Checklist is used to validate that all necessary steps are being properly executed when the project team begins working on the project deliverables.
       

       
    • 20061734 Project Work Authorization Form $10.95
      The Project Work Authorization Form is used to control scope by aligning resources to specific tasks identified in either the Scope Statement or project work breakdown structure. This form provides a team member the authorization to apply effort and time to a particular task.
       

       
    • 20061735 Project Training Plan $12.95
      The Project Training Plan is used to document the strategy for providing the team member the needed skills to execute their tasks on the project. The project manager, working with the team member, creates this plan based on the Project Work Breakdown Structure and relative activities defined in the Project Activity List. This plan is reviewed after the training activities to validate the training objectives were achieved.
       

       
    • 20061736 Project Training Course Description Form $10.95
      The Project Training Course Description Form is created in the Executing Process Group. It is created as part of the Develop Project Team activity. A company's internal training team develops this form to describe the types of training course offering available to the project team or end users.
       

       
    • 20061737 Project Team Member Profile Form $10.95
      The Team Member Profile Form is used to capture professional and personal related information for each Team Member. As part of the Projects Manager's responsibilities, he/she should work with the Human Resource department to provide opportunities for professional and personal growth as a result of the team member's participation. As a result, team member will be able to work with the project management team to address skill gaps or area of personal growth that will benefit the project, as well as the team member.
       

       
    • 20061738 Project Change Request Form $10.95
      The Project Change Request Form is used to document change requests related to the Project and Product. All Change Request Forms should be presented to the Change Control Board members as per the Project Change Control Management plan.
       

       
    • 20061739 Project Change Control Log $8.95
      The Project Change Control Log is created in the Executing Process Group; but used in the Controlling (Monitoring and Controlling) Process Group as a system-of-record to track the identification and status of change requests on the project. Every change request should be catalogued in this document for Change Control Board review. All changes to the project should be managed in accordance to the Project Change Control Management Plan.
       

       
    • 20061740 Proposal $12.95
      The Proposal is created in the Executing Process Group. It is created as part of the Request Sellers Response activity. The Proposal is created by the Seller in response to a procurement package, such as a Solicitation or Request for Proposal (RFP). The Seller documents how he/she plans to provide services or products to the Buyer based on the requirements defined in the procurement package.
       

       
    • 20061741 Seller's Invoice Form $9.95
      The Seller's Invoice is created in the Executing Process Group. It is created as part of the Contract Administration activity. As the Seller performs services or produces deliverables for the project, the Seller submits an invoice for payment. The invoice serves as a request for payment based on work performed in accordance with the scope of the Seller's responsibility as defined in the Contract Statement of Work, Contract, or Contract Work Breakdown Structure.
       

       
     Monitoring and Controlling
    • 20062742 Project Monitoring and Controlling Overview $4.95
      The Project Monitoring and Controlling Process Group Overview is used to understand the characteristics of this phase and delineate the type of activities involved in this phase of the project.
       

       
    • 20062743 Project Monitoring and Controlling Checklist $7.95
      The Project Monitoring and Controlling Checklist is used to validate that all necessary steps to properly control the project are identified and implemented.
       

       
    • 20062744 Project Team Meeting Minutes $8.95
      The Team Meeting Minutes is created in the Controlling (Monitoring and Controlling) Process Group. It is created as part of the Manage Project Team activity. Project Team Meeting Minutes are an important tool to capture discussion topics and points that take place in a meeting. The Team Meeting Minutes should be disseminated to the project team in accordance to the guidelines established in the Communication Plan.
       

       
    • 20062745 Project Team Meeting Agenda $8.95
      The Team Meeting Agenda is created in the Controlling (Monitoring and Controlling) Process Group. It is created as part of the Manage Project Team activity. The Agenda is sent to meeting participants in advance to highlight upcoming discussion topics that will be covered in upcoming team meetings. The Team Meeting Agenda should be disseminated to the project team in accordance to the guidelines established in the Communication Plan.
       

       
    • 20062746 Project Team Member Status Report $10.95
      The Team Member Status Report is used to communicate status, work results, issues, and risks to the project management staff (Team Leader or Project Manager). The Project Manager states the frequency (weekly, monthly) for when project team members submit their status reports.
       

       
    • 20062747 Project Change Control Board Checklist $7.95
      The Project Change Control Board Checklist used to document the procedures that the Change Control Board will use to address change requests on the project.
       

       
    • 20062751 Project Deliverable Audit Form $10.95
      The Project Deliverable Audit Form is used during the Controlling (Monitoring and Controlling) Process Group. It is created as part of the Scope Verification and Perform Quality Control activity. Although quality is considered during the initial steps of the project, it is up to the team member to check his/her own work. During Quality Assurance, the project team reviews the technical aspects of the deliverable to ensure correctness to scope and quality standards.
       

       
    • 20062752 Project Deliverable Formal Acceptance Form $10.95
      The Project Deliverable Formal Acceptance form is used during the Controlling (Monitoring and Controlling) Process Group. It is created as part of the Scope Verification activity. During Product verification, the customer provides feedback to the project team regarding whether or not the completion of the deliverable is acceptable.
       

       
    • 20062748 Project Lessons Learned Form $10.95
      The Project Lessons Learned Document is used to capture critical events and/or decisions that took place on the project as a result of variances, best-practice activities; corrective actions taken that impacted the project. Each team member should complete this form to document an experience that was salient to them and/their work area.
       

       
    • 20062749 Project Lessons Learned Log $8.95
      The Project Lessons Learned Log is used to consolidate all of the individual Lessons Learned into one database format. The Project Lessons Learned Log is a quick reference to documented lessons learned for a particular project.
       

       
    • 20062750 Project Earned Value Reference Guide $8.95
      The Earned Value Reference Guide provides an understanding of basic concepts in Earned Value management to track project costs on scope (work performed), schedule, and resources. This document provides earned value definitions, formulas, and a graph illustration.
       

       
    • 20062753 Seller's Monthly Performance Report $10.95
      The Seller's Monthly Performance Report is used to document the Seller's overall work performance as part of the project's Performance Reporting activity. The Project Manager should review the Project Communication Management Plan and Project Communication Management Plan Matrix documents with the Seller to ensure that the Seller's communication requirements are included.
       

       
     Closing
    • 20063754 Project Closeout and Transfer Overview $4.95
      The Project Closing Process Group Overview describes the characteristics and delineates the type of activities involved in the process.
       

       
    • 20063755 Project Closeout Checklist $7.95
      The Project Closeout Checklist is used to validate that all necessary steps to properly close out a project was completed. It also provides an overall project disposition for how the project was ended.
       

       
    • 20063756 Project Contract Closeout Checklist $8.95
      The Project Contract Closeout Checklist is used to assist the Project Manager to address administrative and project work performance related items as part of the Seller's contract closeout procedures. This document should also be captured in the Project Procurement Management Plan as a standard procurement document used in the procurement process.
       

       
    • 20063757 Project Release Authorization Form $10.95
      The Project Release Authorization Form is used by a project management professional to formally release a resource from the project.
       

       
    • 20063758 Project Performance Evaluation Form $14.95
      The Project Performance Evaluation Form is used during the project closeout administration. All project stakeholders should complete this form to capture lessons learned. At minimum, the project team and project manager should complete this form and use it as (historical information) input to future project initiatives.
       

       
     Product Development
    • 20064759 Product Design/Specification $12.95
      The Product Design/Specification is used in an Information Technology environment to capture business user requirements. This document addresses the business requirement, proposed solutions, and the user's testing strategy from a functional perspective.
       

       
    • 20064760 Product Technical Specification $12.95
      The Technical Specification is used to address the technical changes and implications to the system and/or technical infrastructure to support the solution.
       

       
    • 20064761 Product Test Plan $10.95
      The Product Test Plan is used to define the overall testing strategy and approach for a particular deliverable or set of related deliverables. A project team member responsible for developing a deliverable(s), such as a Report, Interface, or Program, describes his/her testing strategy, (what he/she plans to test, how he/she plans to test, lists the type of data needed to execute the test, and describes the criterion for acceptance of test results).
       

       
    • 20064762 Product Test Case $9.95
      The Test Case document is used to document that details of the testing process and related outcomes. This document details each step executed in a given test and provides overall results for the test case.
       

       
 
 
 
 

HOME   |   PRODUCTS   |   DOWNLOADS   |   NEWS  |   CONTACTS

 
 
 
 
Copyrights © MTC Integration Corporation 2005. All Rights Reserved

TERMS OF USE | LICENSE AGREEMENT | TRADEMARKS | PRIVACY POLICY