Project Management Guidelines
|
|
- Edwin Hoover
- 8 years ago
- Views:
Transcription
1 Project Management Guidelines 1. INTRODUCTION. This Appendix (Project Management Guidelines) sets forth the detailed Project Management Guidelines. 2. PROJECT MANAGEMENT PLAN POLICY AND GUIDELINES OVERVIEW. I. Cover Page The Project Management Plan (PMP) is a critical document that aids the Project Manager in managing the project. It is a documentation of the understanding of the expectations of cost, scope and time and provides a roadmap to the project s success. Establishing a baseline will allow the Project Manager to permanently capture and store these constraints for future use such as impact analysis of a potential change in the project. The change must be documented by stating the effect on cost, schedule and scope after proceeding through the pre-defined Change Management Process. The Project Manager should negotiate the PMP with the State Project Manager so that expectations can be set; and cost, schedule, and scope targets can be maintained. Once completed, any approved change order is stored in an appendix to the PMP. The Contractor must provide a Project Management Plan to demonstrate to the State that the Contractor has a clear understanding of the overall complexity of the project and all associated tasks to successfully implement the requirements in this RFP. The Project Management Plan must address the operational aspects of the project and must address all major sections of this RFP. The Project Management Plan must be approved by the State Contract Manager and must be continuously updated by the Contractor throughout the duration of the project. The Project Management Plan is a living document that charts the path of the project and contains the project s baseline at various points in time. As the project changes, the Project Management Plan is referenced to help determine the impact of those changes on cost, schedule, and scope. If the change is agreed upon, the plan is edited and its contents rebaselined. The project then continues under new constraints. The contents and size of the Project Management Plan will vary from project to project. The effort to create the plan must be weighed against the size and complexity of the project. A two week project may only need a 2-3 page Project Management Plan while a multi-phase, multiyear project, filled with risk and complexity may warrant a much bigger PMP. Depending upon the size of the project, the PMP should contain the following sections: II. Table of Contents III. Document Change History IV. Executive Summary
2 V. Project Work Plan VI. Facility Management Plan VII. Issues Management Plan VIII. Transition Plan IX. Communication Plan X. Weekly Status Reporting XI. Requirements Management Plan XII. Change Management Plan XIII. Issues Management Plan XIV. Risk Management Plan XV. Training Plan XVI. Maintenance and Operations Plan XVII. Administrative Completion Reporting APPROACH AND METHODOLOGY In response to the Request for Proposal, which the State defines as Pre-Award in the system development lifecycle, the State expects a Project Management Plan that describes the approach and methodology for seventeen (17) key aspects of the project management effort associated with a project as determined necessary by the Project Steering Committee, which are numbered I through XVII in the document structure listed above. A description of each key aspect, along with the associated requirements, can be found below. The Contractor will be provided the opportunity to update the Project Management Plan in Requirements and Planning Phase; and in doing so, will begin to provide a history of document issuance and change(s). Project Management Plan Requirements: The Contractor Must 1. Prepare and deliver a Project Management Plan during the Pre-Award Phase. 2. Starting in Requirements Analysis and Design Phase and for the duration of the System Development Life Cycle, provide an update to the Project Management Plan following the implementation of any change or configuration that impacts the Project Management Plan. 3. Track each deliverable of the Project Management Plan in Microsoft Project format (or a similar software package or application with Contractor provided licenses). All updates must be presented for review at the weekly status meeting.
3 4. Cooperate with the IV&V (Independent Validation and Verification) Contractor and provide access to staff, documentation, and deliverables, as directed by the State. 5. Describe the management process for obtaining approval of the deliverables, as well as any go/no-go decision points in the project. 6. Update the Project Management Plan and identify the status of all activities and milestones associated with the Project Management Plan. 7. The Project Management Plan must include a cover page that contains a title, issuance date, and version number. 8. The Project Management Plan must include a table of contents and associated links to permit a reader to move directly to the data content from the table of contents. 9. The Project Management Plan must include a history of changes that identifies each issuance date, version number, and the list of changes made compared to the previous issuance and version of the plan. 10. The Project Management Plan must include an executive summary, including the purpose of the plan, and the contents of the document. 11. The Project Management Plan must include a section Project Work Plan (aka Schedule), and follow the content and requirements defined below. 12. The Project Management Plan may include a section Facility Management Plan, (if applicable) and follow the content and requirements defined below. 13. The Project Management Plan must include a section Transition Plan, and follow the content and requirements defined below. 14. The Project Management Plan must include a section Communication Management Plan, and follow the content and requirements defined below. 15. The Project Management Plan must include a section Weekly Status Reporting, and follow the content and requirements defined below. 16. The Project Management Plan must include a section Requirements Management Plan, and follow the content and requirements defined below. 17. The Project Management Plan must include a section Change Management Plan, and follow the content and requirements defined below. 18. The Project Management Plan must include a section Issues Management Plan, and follow the content and requirements defined below. 19. The Project Management Plan must include a section Risk Management Plan, and follow the content and requirements defined below. 20. The Project Management Plan must include a section Training Plan, and follow the content and requirements defined below. 21. The Project Management Plan must include a section Maintenance and Operations Plan, and follow the content and requirements defined below. 22. The Project Management Plan may include a section Certification Readiness, and follow the content and requirements defined below. 23. The Project Management Plan must include a section Administrative Completion Reporting, and follow the content and requirements defined below. Project Work Plan Requirements The Contractor must provide a Project Work Plan to help guide the project team through the execution, operations and closure phases of the project. The Project Work Plan is a set of plans to help manage
4 staff, and subcontractors if applicable, to ensure that the project is delivered on time and within budget. The Project Work Plan must be broken down into specific tasks and sub-tasks, including the identification of project deliverables, and assignment of allocated resources to each task. The Project Work Plan must adhere to the following outlined structure: I. Cover Page II. Table of Contents III. Document Change History IV. Executive Summary Overview V. Contractor s Approach a. Policies b. Procedures c. Metrics VI. Project s Critical Path a. Performance monitoring VII. Conditions and Standards for verification and compliance with any mandates (if applicable) VIII. Work Breakdown Structure a. Deliverables b. Tasks and subtasks c. Proposed Milestones d. Schedules e. Resources IX. Project Scope a. Procedures and resources b. Applications and tools X. Implementation of modules and components XI. Weekly Status Reporting
5 a. Approach b. Tools c. Examples APPROACH AND METHODOLOGY In response to the Request for Proposal, which the State defines as Pre-Award Phase in the System Development Life Cycle the State expects an approach and methodology of the Project Work Plan which will help guide the project team for the duration for the System Development Life Cycle. The approach and methodology must cover all aspects of the Project Work Plan. PLAN AND PROCESS During the Planning phase and through Maintenance and Operations Phase, the Contractor must prepare and deliver a Project Work Plan that complies with the general and plan requirements listed below. This deliverable represents the detailed plan and process associated with the approach and methodology previously described in the Project Management Plan for the work plan. Upon approval of the plan, the Contractor must replace in the Project Management Plan the approach and methodology section with the approved Project Work Plan. The Contractor must: 2.1 Describe its approach and methodology for the work plan management in Pre Award Phase, which will help guide the project team for the duration of the System Development Life Cycle. 2.2 Prepare and deliver the PWP during Planning Phase and update as needed for the life of the project. 2.3 Create a Work Breakdown Structure (WBS) developed in Microsoft Project, or equivalent format acceptable to the State, which includes: all deliverables; tasks and subtasks; proposed milestones; associated dependencies; and resources assigned to each task and subtask to be performed during Pre- Award Phase and through Maintenance and Operations Phase 2.4 Update the Project Management Plan and identify the status of all activities and milestones associated with the PWP, as necessary. 2.5 The PWP must include a cover page that contains a title, issuance date, and version number. 2.6 The PWP must include a table of contents and associated links to permit a reader to move directly to the data content from the table of contents. 2.7 The PWP must include a history of changes that identifies each issuance date, version number, and the list of changes made compared to the previous issuance and version of the plan. 2.8 The PWP must include an executive summary, including the purpose of the plan, the approach and methodology, and the contents of the document.
6 2.9 The PWP must include a project overview that includes a narrative description of its overall management approach, policies, procedures, and project metrics The PWP must document the project s critical path and include a performance monitoring plan The PWP must include a description and organization of the Work Breakdown Structure (WBS) The PWP must describe the business processes and procedures for controlling the scope of the project The PWP must describe how changes in project scope will be presented to the State, including prioritization of changes, budget and schedule implications The PWP must describe the Contractor s approach for the phased implementation of modules and components The PWP must describe any applications and/or tools that will be used to control scope The PWP must include the approach to weekly status reporting and tools that will be used as part of the reporting methodology The PWP must include examples of the weekly status report(s) that will be used throughout all phases of the project. The report(s) must include a summarization of the progress and status of all activities, milestones and achievements, schedule risks, schedule status of all activities related to the enterprise scope of work, documented problems encountered and the resulting impact, as well as corrective measures taken. Facility Management Plan Requirements (If needed) The Contractor must provide a Facility Management Plan that will include all activities, resources and schedules supporting the establishment and maintenance of the project office and facilities for the development, implementation and operations of the Project. The Contractor will be required to provide a fully functional and operational facility for the Project. The Project Facility will house the entire Project Team including NJ State Project staff, Contractor staff, and any other Project Contractors. The Contractor must establish a primary project facility in a location approved by the State Contract Manager. The Contractor must maintain an office in New Jersey. The Contractor s proposals must include strategies to rapidly procure adequate space for key and core State and Contractor staff during the initial phases of project development. The State reserves the right to inspect all facilities at any time. Successful completion of this deliverable will ensure that the Project Team has an adequate facility in which to work. The Facility Management Plan must adhere to the following outlined structure:
7 I. Cover Page II. Table of Contents III. Document Change History IV. Executive Summary V. Roles and Responsibilities VI. Contractor s Approach VII. Approach and Methodology APPROACH AND METHODOLOGY In response to the Request for Proposal, which the State defines as Pre-Award Phase in the System Development Life Cycle for the project, the State expects an approach and methodology to facility management for the duration of the System Development Life Cycle. The approach and methodology must cover all aspects of facility management. PLAN AND PROCESS During Planning Phase, the Contractor must prepare and deliver a Facility Management Plan that complies with the general and plan requirements listed below. This deliverable represents the detailed plan and processes associated with the approach and methodology previously described in the Project Management Plan for facility management. Upon approval of the plan, the Contractor must replace in the Project Management Plan the approach and methodology section for facility management with the approved Facility Management Plan. REQUIREMENTS 3.1 The Facility Management Plan must include a cover page that contains a title, issuance date, and version number. 3.2 The Facility Management Plan must include a table of contents and associated links to permit a reader to move directly to the data content from the table of contents. 3.3 The Facility Management Plan must include a history of changes that identifies each issuance date, version number, and the list of changes made compared to the previous issuance and version of the plan. 3.4 The Facility Management Plan must include an executive summary, including the purpose of the plan, the approach and methodology, and the contents of the document.
8 3.5 The Facility Management Plan must include the Contractor s approach and methodology to the requirements above and the process of maintaining compliance with these requirements. Transition Plan Requirements The Contractor must provide a Transition Plan to describe an approach for knowledge transfer, and for evaluating the risks and issues involved in the Project transition, and the strategies to minimize disruption to the normal business operations of the State during Project integration, implementation, and cutover activities. The Contractor must develop and implement its approach to transition planning and provide the State with the ability to monitor business operations throughout the project phases and life of the Contract. The Transition Plan must adhere to the following outlined structure: I. Cover Page II. Table of Contents III. Documents Change History IV. Executive Summary V. Contractor s Approach VI. Major Activities and Milestones VII. Roles and Responsibilities VIII. Proposed Sequence and Schedule by Transition Phase-In IX. Communication X. Business Process Transition XI. Technical Transition XII. Staff Transition APPROACH AND METHODOLOGY In response to the Request for Proposal, which the State defines as Pre-Award Phase in the System Development Life Cycle for the Project, the State expects an approach and methodology for initiating and maintaining normal business operations during Project transition for the duration of the System
9 Development Life Cycle. The approach and methodology must cover all aspects of transition management, including transition items, transition reporting, and transition auditing. PLAN AND PROCESS During Planning Phase, the Contractor must prepare and deliver a Transition Plan that complies with the general and plan requirements listed below. This deliverable represents the detailed plan and processes associated with the approach and methodology previously described in the Project Management Plan for transition management. Upon approval of the plan, the Contractor must replace in the Project Management Plan the approach and methodology section for transition management with the approved Transition Plan. REQUIREMENTS The Contractor must: 4.1 Describe its approach and methodology for initiating and maintaining normal business operations during the Project transition. 4.2 Provide the Transition Plan during Planning Phase within 30 State work days after the effective date of the Contract, to allow appropriate knowledge transfer between the incumbent project Contractor and the new Contractor. 4.3 Participate in joint review meetings with the State and the incumbent Contractor to discuss methods to minimize disruption to the normal business operations of the State during the Project transition. 4.4 Provide major activities and milestones. 4.5 Describe the method of documenting strategies and decisions. 4.6 Identify and define the impact of each business process to be transitioned from incumbent Contractor to successor Contractor. 4.7 Identify and define the impact of each technical process to be transitioned from incumbent Contractor to successor Contractor. 4.8 Identify the proposed staff transition from incumbent Contractor to successor Contractor. 4.9 Describe the process for materials, artifacts, and equipment transfers Initiate, coordinate and host an initial Project Kickoff meeting with the State within ten (10) State business days after the contract effective date or as defined by the State Describe how appropriate knowledge transfer between the current Project Contractor and the successor Project Contractor will occur Not employ any individuals who are employees of the current Fiscal Agent without prior written consent and approval by the State Provide a transition strategy that ensures knowledge transfer, evaluating the risks and issues involved in the Project transition, and the strategies to minimize disruption to the normal business operations of the State during Project integration, implementation, and cutover activities 4.14 Update the Project Management Plan and identify the status of all activities and milestones associated with the Transition Plan, as necessary.
10 4.15 The Transition Plan must include a cover page that contains a title, issuance date, and version number The Transition Plan must include a table of contents and associated links to permit a reader to move directly to the data content from the table of contents The Transition Plan must include a history of changes that identifies each issuance date, version number, and the list of changes made compared to the previous issuance and version of the plan The Transition Plan must include an executive summary, including the purpose of the plan, the approach and methodology, and the contents of the document The Transition Plan must include a list of major activities and milestones to be achieved The Transition Plan must include a definition of roles and responsibilities of designated staff and/or teams that will manage and perform transition activities The Transition Plan must include an inventory of all transition items, categorize each item into phases for transition, include calendar schedule by phase-in, hardware, software and materials The Transition Plan must include all processes and procedures associated with communication of the transition, the workflow steps for each process, and examples of all associated forms The Transition Plan must include all processes and procedures associated with business process transition, the workflow steps for each process, and examples of all associated forms The Transition Plan must include all processes and procedures associated with technical transition, the workflow steps for each process, and examples of all associated forms The Transition Plan must include all processes and procedures associated with staff transition, the workflow steps for each process, and examples of all associated forms. Communication Management Plan Requirements The Contractor must provide a Communication Management Plan to document the methods and activities needed to ensure timely and appropriate collection, generation, dissemination, storage, and ultimate disposition of project information among the project team and stakeholders. The Contractor must develop and implement its approach to communications management. The Communication Management Plan must include strategies and tools that will be used throughout all project phases. The Communication Management Plan must adhere to the following outlined structure: I. Cover Page II. Table of Contents III. Document Change History IV. Executive Summary V. Roles and Responsibilities VI. Contractor s Approach
11 VII. Process and Procedures VIII. Tools APPROACH AND METHODOLOGY In response to the Request for Proposal, which the State defines as Pre-Award Phase in the System Development Life Cycle for the Project, the State expects an approach and methodology to ensure timely and appropriate collection, generation, dissemination, storage, and ultimate disposition of project information among the project team and stakeholders for the duration of the System Development Life Cycle. The approach and methodology must cover all aspects of communication management including the strategies and tools that will be used throughout all project phases. PLAN AND PROCESS During Planning Phase, the Contractor must prepare and deliver a Communication Plan that complies with the general and plan requirements listed below. This deliverable represents the detailed plan and processes associated with the approach and methodology previously described in the Project Management Plan for communication management. Upon approval of the plan, the Contractor must replace in the Project Management Plan the approach and methodology section for communication management with the approved Communication Management Plan. REQUIREMENTS The Contractor must: 5.1 Describe its approach and methodology for communication management in Pre Award Phase, including timely and appropriate collection, generation, dissemination, storage, and ultimate disposition of project information among the project team and stakeholders for the duration of the System Development Life Cycle. 5.2 Prepare and deliver the Communication Management Plan during Planning Phase and at least 30 Days prior to start of Requirements Analysis and Design Phase. 5.3 Integrate fully all communication management processes into the Project Workflow Management System (if present and applicable). 5.4 Describe how communication with the different stakeholders will be accomplished, e.g., members, providers, state staff, vendors, throughout all phases of the lifecycle. 5.5 Describe the business processes and procedures for managing communication channels. 5.6 Update the Project Management Plan and identify the status of all activities and milestones associated with the Communication Management Plan, as necessary. 5.7 Provide tools for both internal and external communication throughout all project phases. 5.8 Update the Communication Plan annually or at the direction of the State. 5.9 Describe how the Communication Plan will be implemented and how it will be integrated into the overall Project Management Plan.
12 5.10 The Communication Management Plan must include a cover page that contains a title, issuance date, and version number The Communication Management Plan must include a table of contents and associated links to permit a reader to move directly to the data content from the table of contents The Communication Management Plan must include a history of changes that identifies each issuance date, version number, and the list of changes made compared to the previous issuance and version of the plan The Communication Management Plan must include an executive summary, including the purpose of the plan, the approach and methodology, and the contents of the document The Communication Management Plan must include a definition of roles and responsibilities as related to communications The Communication Management Plan must include all processes and procedures associated with communication management, the workflow steps for each process, and examples of all associated forms The Communication Management Plan must describe any applications and/or tools that will be used to track and report written, electronic and telephone inquiries. Weekly Status Reporting Plan Requirements The Contractor must provide weekly status reporting to summarize the progress and status of all activities, milestones and achievements, risks, and status of all activities related to the project s scope of work. The Contractor must provide a Weekly Status Reporting Plan to describe the methods and activities needed to ensure documentation of problems encountered and the resulting impact as well as corrective actions taken. The Weekly Status Reporting Plan must adhere to the following outlined structure: I. Cover Page II. Table of Contents III. Document Change History IV. Executive Summary V. Contractor s Approach VI. Roles and Responsibilities VII. Process and Procedures VIII. Applications and Tools APPROACH AND METHODOLOGY
13 In response to the Request for Proposal, which the State defines as Pre-Award Phase in the System Development Life Cycle for the Project, the State expects an example of a status report. The approach and methodology of the weekly status reporting activities must be described in the Contractor s draft Project Work Plan (PWP) submitted as part of its bid response. PLAN AND PROCESS During Planning Phase, and throughout the life of the contract, the Contractor must prepare and deliver the PWP that includes the details of the weekly status reporting activities and complies with the requirements listed below. This Weekly Status Reporting Plan represents the detailed plan and processes associated with the approach and methodology previously described in the PWP. Upon approval of the PWP, the Contractor must begin generating required reports and provide an update to the Project Management Plan, as needed. REQUIREMENTS The Contractor must: 6.1 Provide an initial status report during Planning Phase within 30 State business days after the effective date of the Contract, and weekly thereafter or at a frequency designated by the State. 6.2 Provide an updated PWP during Planning Phase no later than twenty-four (24) hours prior to the status meeting. 6.3 Ensure attendance of appropriate staff as identified by State at all status reporting meetings. 6.4 Participate in weekly project status and other meetings as directed by the State. 6.5 Describe within the PWP the strategies to be used to summarize the progress and status of all activities, milestones and achievements, schedule risks, schedule status of activities related to the scope of work, and document problems encountered and the resulting impact as well as corrective actions taken. 6.6 Provide a meeting agenda, previous meeting minutes and supporting documentation no later than twenty-four (24) hours prior to the status meeting. 6.7 Submit status report in a format approved by the State Contract Manager. 6.8 Update Project Management Plan, as necessary. 6.9 The Weekly Status Reporting Plan must include a cover page that contains the following: a title; issuance date; and version number The Weekly Status Reporting Plan must include a table of contents and associated links to permit a reader to move directly to the data content from the table of contents The Weekly Status Reporting Plan must include a history of changes that contains the following: identifies each issuance date: version number: and the list of changes made compared to the previous issuance and version of the plan The Weekly Status Reporting Plan must include an executive summary, including the purpose of the plan, the approach and methodology, and the contents of the document The Weekly Status Reporting Plan must include a definition of roles and responsibilities as related to weekly status reporting.
14 6.14 The Weekly Status Reporting Plan must include all processes and procedures associated with weekly status reporting, the workflow steps for each process, and examples of all associated forms The Weekly Status Reporting Plan must describe any applications and/or tools that will be used for weekly status reporting. Requirements Management Plan Requirements The Contractor must provide a Requirements Management Plan to describe the approach and methodology that will be used to document and track the project requirements from initial proposal submission through design, testing, and certification to verify that all requirements have been fulfilled. The Requirements Management Plan must ensure that the technical requirements can be clearly traced to the business or functional requirements that they support and must include any unresolved traceability issues. The Contractor must submit an initial Requirements Traceability Matrix (RTM) as part of its proposal and must maintain the baseline requirements in order to directly associate the baseline to the configuration of the Project. Additions, modifications, and deletions to these requirements must be added and modified throughout the project so it is imperative that a current version of the RTM be maintained at all times. The Requirements Management Plan must adhere to the following outlined structure: I. Cover Page II. Table of Contents III. Document Change History IV. Executive Summary V. Contractor s Approach VI. Roles and Responsibilities VII. Repository VIII. Tools APPROACH AND METHODOLOGY In response to the Request for Proposal, which the State defines as Pre-Award Phase in the System Development Life Cycle for the Project, the State expects an approach and methodology for documenting and tracking project requirements for the duration of the System Development Life Cycle. The approach and methodology must cover all aspects of traceability management, including tracing requirements and unresolved issues, change management, and version control.
15 PLAN AND PROCESS During Planning Phase, the Contractor must prepare and deliver a Requirements Management Plan that complies with the general and plan requirements listed below. This deliverable represents the detailed plan and processes associated with the approach and methodology previously described in the Project Management Plan for requirements traceability management. Upon approval of the plan, the Contractor must replace in the Project Management Plan the approach and methodology section for requirements management with the approved Requirements Management Plan and begin the process of traceability management within the Requirements Traceability Matrix (RTM). REQUIREMENTS The Contractor must: 7.1 Describe its approach and methodology for requirements management in Pre-Award Phase. The methodology will become the foundation for the Requirements Management Plan. 7.2 Prepare and deliver the Requirements Management Plan during Planning Phase and at least 30 Days prior to the start of Requirements Analysis and Design Phase. 7.3 Establish the initial Project baseline requirements that will serve as the basis for all subsequent configuration, integration, and testing activities. 7.4 Work with the State and its stakeholders to analyze and verify system functional and technical requirements and specifications, including business rules. 7.5 Use the RTM to ensure that all requirements can be traced to the supporting business rule or State objective. 7.6 Ensure that links for each unique requirement to other supporting requirements, including the RFP or deliverables, are established and maintained. 7.7 Document that all requirements have been verified and validated against the Requirements Traceability Matrix (RTM). If any external certification of requirements needs to occur (i.e. External Agency, Federal, State or local agencies, authorized third party, etc.) document that as well 7.8 Summarize its analysis and verification of the requirements, including any impacts to the Project design concept as proposed in its proposal to the State. 7.9 Secure additional documentation, such as clarifications, details and/or examples that help define a requirement and can be attached to the appropriate requirement(s) utilizing the RTM to identify the references to supporting documentation related to a requirement Document specifications for all requirements to support configuration activities through Planning Phase Provide an initial Requirements Traceability Matrix (RTM) as part of the Requirements Management Plan Use the Requirements Traceability Matrix (RTM) to document and track all phases of testing and evaluation Plan, schedule, and coordinate all necessary activities in this task, including the development of schedules, invitations, and locations for the appropriate analysis and review meetings.
16 7.14 Describe business processes and procedures that will be used for tracking requirements from design through coding, acceptance, unit and integration testing, as well as promotion into production Integrate fully all Requirement Managements processes in the Project Workflow Management System (if present and applicable) Describe how the Requirements Management Plan will be implemented and how it will be integrated into the overall Project Management Plan approach Update the Project Management Plan and identify the status of all activities and milestones associated with the Requirements Management Plan The Requirements Management Plan must include a cover page that contains a title, issuance date, and version number, as necessary The Requirements Management Plan must include a table of contents and associated links to permit a reader to move directly to the data content from the table of contents The Requirements Management Plan must include a history of changes that identifies each issuance date, version number, and the list of changes made compared to the previous issuance and version of the plan The Requirements Management Plan must include an executive summary, including the purpose of the plan, the approach and methodology, and the contents of the document The Requirements Management Plan must include a definition of roles and responsibilities associated with management of the matrix The Requirements Management Plan must describe how requirements will be stored in a repository and how the State and stakeholders will access the information The Requirements Management Plan must include a description of the tools associated with the RTM process and activities The Requirements Management Plan must include all processes and procedures, the workflow steps for each process, and examples of all associated forms. Change Management Plan Requirements The Contractor must provide a Change Management Plan to address contractual scope changes for the project. The Change Management Plan must define the approach, administrative procedures, and roles and responsibilities for submitting, evaluating, coordinating, approving or disapproving business and technical changes to the agreed upon solution. The Change Management Plan must adhere to the following outlined structure: I. Cover Page II. Table of Contents
17 III. Document Change History IV. Executive Summary V. Contractor s Approach VI. Roles and Responsibilities VII. Documenting Change a. Management Activities b. Workflow VIII. Training APPROACH AND METHODOLOGY In response to the Request for Proposal, in the System Development Life Cycle for the project, the State expects an approach and methodology for contractual change management for the duration of the System Development Life Cycle. The approach and methodology must cover all aspects of contractual change management, including document processing, reporting, archiving, and auditing. PLAN AND PROCESS During the Requirements Analysis and Design phase of the project, the Contractor must prepare and deliver a Change Management Plan that complies with the general and plan requirements listed below. This deliverable represents the detailed plan and processes associated with the approach and methodology previously described in the Project Management Plan for change management. Upon approval of the plan, the Contractor must replace in the Project Management Plan the approach and methodology section for contractual change management with the approved Change Management Plan. REQUIREMENTS The Contractor must: 8.1 Describe and provide its approach and methodology for Change Management in their response to this RFP. The methodology will become the foundation for the Change Management Plan, and should include at a minimum: resources, time, solution, etc. 8.2 Prepare and deliver the Change Management Plan during the Requirements Analysis and Design phase of the project and at least 30 Days prior to start of the Development and Testing phase. 8.3 Provide an application tool for submitting, tracking and reporting on activities and outcomes associated with a change request that has the potential to create a change in contract scope, throughout the System Development Life Cycle.
18 8.4 Ensure that the application supports pricing estimates and key dates for a change request. 8.5 Ensure that all contractual change request activities are represented in the Project Work Plan. 8.6 Develop a controlled change process for changes set against the baseline scope of work and define and provide for a Contractor management-level Change Control Board, with associated roles and the State s and Contractor s responsibilities, including a process for managing the change and for the review of supporting documentation such as resources, estimated timeframe, estimated time and materials costs, etc. 8.7 Maintain an audit trail of all updates/changes to the project. 8.8 Document all procedures for users of the Change Management tracking application through an online version. 8.9 Provide training for users of the Change Management tool Describe how the Change Management Plan will be implemented and how it will be integrated into the overall Project Management Plan approach, including any and all COTS tools that will be used Integrate fully all change management processes in the Project Workflow Management System (if present and applicable) Update the Project Management Plan and identify the status of all activities and milestones associated with the Change Management Plan, as necessary Describe the process of analyzing scope, time and cost to support change request activities Ensure that all change request activity status is documented and reported on a regular basis The Change Management Plan must include a cover page that contains a title, issuance date, and version number The Change Management Plan must include a table of contents and associated links to permit a reader to move directly to the data content from the table of contents The Change Management Plan must include a history of changes that identifies each issuance date, version number, and the list of changes made compared to the previous issuance and version of the plan The Change Management Plan must include an executive summary, including the purpose of the plan, the approach and methodology, and the contents of the document The Change Management Plan must include a definition of roles and responsibilities.
19 8.20 The Change Management Plan must include an inventory of all change management items The Change Management Plan must include all processes and procedures associated with documenting change management activities, the workflow steps for each process, and examples of all associated forms The Change Management Plan must include all processes and procedures associated with training staff and stakeholders, the workflow steps for each process, and examples of all associated forms. Issues Management Plan Requirements The Contractor must provide an Issues Management Plan that comprehensively documents technical and administrative issues that occur as the project progresses. The Contractor must develop and implement an Issues Management Plan that describes its approach to issue resolution and provides the State with the ability to monitor resolution of issues throughout the project phases and life of the Contract. The primary goal of the plan is to ensure that the issues are identified, evaluated, assigned for resolution, monitored, documented and communicated. The Issues Management Plan must adhere to the following outlined structure: I. Cover Page II. Table of Contents III. Document Change History IV. Executive Summary Overview V. Roles and Responsibilities VI. Contractor s Approach VII. Process and Procedures VIII. Tools IX. Workflow APPROACH AND METHODOLOGY In response to the Request for Proposal, which the State defines as Pre-Award Phase in the System Development Life Cycle for the Project, the State expects an approach and methodology to issue resolution with the ability to monitor resolution of issues for the duration of the System Development Life Cycle. The approach and methodology must cover all aspects of issues management to ensure that
20 issues are identified, evaluated, assigned for resolution, monitored, resolved, documented and communicated. PLAN AND PROCESS During Requirements Analysis and Design Phase and throughout the life of the contract, the Contractor must prepare and deliver an Issues Management Plan that complies with the general and plan requirements listed below. This deliverable represents the detailed plan and process associated with the approach and methodology previously described in the Project Management Plan for issues management. Upon approval of the plan, the Contractor must replace in the Project Management Plan the approach and methodology section for issues management with the approved Issues Management Plan. REQUIREMENTS The Contractor must: 9.1 Describe its approach and methodology for issues management in Pre-Award Phase, ensuring that issues are identified, evaluated, assigned for resolution, monitored, resolved, documented and communicated. 9.2 Prepare and deliver the Issues Management Plan during Requirements Analysis and Design Phase and at least 30 Days prior to start of Development and Testing Phase. 9.3 Define the procedures for the escalation of an issue. 9.4 Describe how the business processes and procedures will be implemented and integrated into the overall Project Management Plan. 9.5 Identify the criteria for determining priority, severity, resolution, and category of issues. 9.6 Provide an issues management strategy, including analysis, impact assessment, mitigation, tracking/control, resolution methodology and escalation management. 9.7 Integrate fully, all issues management processes into the Project Workflow Management System (if present and applicable). 9.8 Update the Project Management Plan and identify the status of all activities and milestones associated with the Issues Management Plan, as necessary. 9.9 The Issues Management Plan must include a cover page that contains a title, issuance date, and version number The Issues Management Plan must include a table of contents and associated links to permit a reader to move directly to the data content from the table of contents The Issues Management Plan must include a history of changes that identifies each issuance date, version number, and the list of changes made compared to the previous issuance and version of the plan The Issues Management Plan must include an executive summary, including the purpose of the plan, the approach and methodology, and the contents of the document The Issues Management Plan must include a definition of roles and responsibilities.
21 9.14 The Issues Management Plan must include all processes and procedures associated with issues management, the workflow steps for each process, and examples of all associated forms The Issues Management Plan must propose an application that will record and track issues and describe how it will be utilized by all stakeholders The Issues Management Plan must include the tools to be used for the identification, definition and evaluation of project issues related to the Project. Risk Management Plan Requirements The Contractor must provide a Risk Management Plan to comprehensively document the approach to risk analysis, risk mitigation, and risk tracking/control. The Contractor must develop and implement its approach to risk analysis (i.e., the evaluation of risks and risk interactions to assess the range of possible project outcomes), risk mitigation (i.e., the identification of ways to minimize or eliminate project risks), and risk tracking/control (i.e., a method to ensure that all steps of the risk management process are being followed and risks are being mitigated effectively) and provide the State with the ability to monitor resolution of risk throughout the project phases and life of the Contract. The Risk Management Plan must ensure a clearly established process for problem escalation and must be updated, as needed, throughout the term of the contract. The Risk Management Plan must include an annual Project risk assessment. The Risk Management Plan must adhere to the following outlined structure: I. Cover Page II. Table of Contents III. Document Change History IV. Executive Summary V. Contractor s Approach VI. Process and Procedures VII. Roles and Responsibilities VIII. Annual Risk Assessment IX. Tools X. Workflow APPROACH AND METHODOLOGY
22 In response to the Request for Proposal, which the State defines as Pre-Award Phase in the System Development Life Cycle for the Project, the State expects an approach and methodology to risk management for the duration of the System Development Life Cycle. The approach and methodology must cover all aspects of risk management, including analysis, mitigation, and tracking and control. PLAN AND PROCESS During Requirements Analysis and Design Phase, the Contractor must prepare and deliver a Risk Management Plan that complies with the general and plan requirements listed below. This deliverable represents the detailed plan and processes associated with the approach and methodology previously described in the Project Management Plan for risk management. Upon approval of the plan, the Contractor must replace in the Project Management Plan the approach and methodology section for risk management with the approved Risk Management Plan. REQUIREMENTS The Contractor must: 10.1 Describe its approach and methodology for risk management in Pre-Award Phase, for all aspects of risk management, including analysis, mitigation, and tracking and control Prepare and deliver the Risk Management Plan during Requirements Analysis and Design Phase and at least 30 Days prior to start of Development and Testing Phase Describe the business processes and procedures to be used for identifying and defining, tracking, monitoring, quantifying, prioritizing, and mitigating risks Provide a risk management strategy for risk analysis, risk mitigation and risk tracking/control, including methodology and escalation management Describe its approach to various risk factors including contractual risk, technology risk, size and complexity risks, risk assessment, personnel acquisition and retention risks, and risks to achieving customer acceptance Describe how the business processes and procedures will be implemented and integrated into the overall Project Management Plan Update the Project Management Plan and identify the status of all activities and milestones associated with the Risk Management Plan, as necessary The Risk Management Plan must describe the application and/or tools and techniques that will be used for risk identification, documentation, management, analysis, logging and risk mitigation The Risk Management Plan must include a cover page that contains a title, issuance date, and version number The Risk Management Plan must include a table of contents and associated links to permit a reader to move directly to the data content from the table of contents The Risk Management Plan must include a history of changes that identifies each issuance date, version number, and the list of changes made compared to the previous issuance and version of the plan.
23 10.12 The Risk Management Plan must include an executive summary, including the purpose of the plan, the approach and methodology, and the contents of the document. The Risk Management Plan must describe the processes and procedures that will be used for risk assessment The Risk Management Plan must include a definition of roles and responsibilities The Risk Management Plan must describe processes that will be completed annually for the Project risk assessment The Risk Management Plan must include all processes, procedures, and tools associated with risk management, the workflow steps for each process, and examples of all associated forms. Training Plan Requirements The Contractor must provide a Training Plan to describe the strategy for training the project staff, State users, providers, and other stakeholders on using any and all aspects of the Project. The Training Plan must cover both the system training for all users and providers and operations training for all subcontractors, if applicable, as well as State operations personnel. The Training Plan must describe training approaches, including video conferencing, face-to-face presentations, and self-directed tutorials. The training plan must include both initial and ongoing training strategies. Since the training requirements will vary based on the project phase, the plan must be organized by project phase. The Training plan must provide an integrated training approach covering the different modules in the Project and include training for unique module areas. The Training Plan must adhere to the following outlined structure: I. Cover Page II. Table of Contents III. Document Change History IV. Executive Summary V. Contractor s Approach VI. Roles and Responsibilities VII. Training Environment VIII. Tools IX. Documentation and Artifacts X. Reporting and Evaluation APPROACH AND METHODOLOGY
PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME >
PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME > Date of Issue: < date > Document Revision #: < version # > Project Manager: < name > Project Management Plan < Insert Project Name > Revision History Name
More informationMinnesota Health Insurance Exchange (MNHIX)
Minnesota Health Insurance Exchange (MNHIX) 1.2 Plan September 21st, 2012 Version: FINAL v.1.0 11/9/2012 2:58 PM Page 1 of 87 T A B L E O F C O N T E N T S 1 Introduction to the Plan... 12 2 Integration
More information<name of project> Software Project Management Plan
The document in this file is adapted from the IEEE standards for Software Project Management Plans, 1058-1998, which conforms to the requirements of ISO standard 12207 Software Life Cycle Processes. Tailor
More informationProject Management Plan for
Project Management Plan for [Project ID] Prepared by: Date: [Name], Project Manager Approved by: Date: [Name], Project Sponsor Approved by: Date: [Name], Executive Manager Table of Contents Project Summary...
More informationTHE COMPLETE PROJECT MANAGEMENT METHODOLOGY AND TOOLKIT
THE COMPLETE PROJECT MANAGEMENT METHODOLOGY AND TOOLKIT GERARD M. HILL CRC Press Taylor & Francis Group Boca Raton London New York CRC Press is an imprint of the Taylor & Francis Croup, an informa business
More informationTemplate K Implementation Requirements Instructions for RFP Response RFP #
Template K Implementation Requirements Instructions for RFP Response Table of Contents 1.0 Project Management Approach... 3 1.1 Program and Project Management... 3 1.2 Change Management Plan... 3 1.3 Relationship
More informationProgram Lifecycle Methodology Version 1.7
Version 1.7 March 30, 2011 REVISION HISTORY VERSION NO. DATE DESCRIPTION AUTHOR 1.0 Initial Draft Hkelley 1.2 10/22/08 Updated with feedback Hkelley 1.3 1/7/2009 Copy edited Kevans 1.4 4/22/2010 Updated
More informationIntroduction to the ITS Project Management Methodology
Introduction to the ITS Project Management Methodology In September 1999 the Joint Legislative Committee on Performance Evaluation and Expenditure Review (PEER) produced a report entitled Major Computer
More informationATTACHMENT 3 SPS PROJECT SENIOR PROGRAM MANAGER (SPM) DUTIES & RESPONSIBILITIES
1. ROLE DEFINITIONS ATTACHMENT 3 SPS PROJECT SENIOR PROGRAM MANAGER (SPM) DUTIES & RESPONSIBILITIES The purpose of this section is to distinguish among the roles interacting with the SPM obtained through
More informationDepartment of Administration Portfolio Management System 1.3 June 30, 2010
E 06/ 30/ 2010 EX AM PL 1. 3 06/ 28/ 2010 06/ 24/ 2010 06/ 23/ 2010 06/ 15/ 2010 06/ 18/ 2010 Portfolio System 1.3 June 30, 2010 Contents Section 1. Project Overview... 1 1.1 Project Description... 1 1.2
More information- ATTACHMENT - PROGRAM MANAGER DUTIES & RESPONSIBILITIES MARYLAND STATE POLICE W00B0400021
- ATTACHMENT - PROGRAM MANAGER DUTIES & RESPONSIBILITIES MARYLAND STATE POLICE W00B0400021 About this document this is a detailed description of typical Project Manager (PM) duties, responsibilities, and
More informationPROJECT MANAGEMENT PROFESSIONAL CERTIFIED ASSOCIATE IN PROJECT MANAGEMENT (PMP & CAPM) EXAM PREPARATION WORKSHOP
TSE015 PROJECT MANAGEMENT PROFESSIONAL CERTIFIED ASSOCIATE IN PROJECT MANAGEMENT (PMP & CAPM) EXAM PREPARATION WORKSHOP Course Outline I. Introduction and Course Objectives A. About PMI B. PMP and CAPM
More informationAppeals Case Management System Project. Scope Management Plan. November 20, 2014
Appeals Case Management System Project Version 1.0 Health and Human Services Agency, Office of Systems Integration Template Revision History REVISION HISTORY REVISION # DATE OF RELEASE OWNER SUMMARY OF
More informationProject Start Up. Start-Up Check List. Why a Project Check List? What is a Project Check List? Initial Release 1.0 Date: January 1997
Why a Project Check List? A good way to ensure that all start-up tasks are completed prior to actually starting the project is to develop a start-up check list. The check list can be developed and then
More informationVA ICJIS. Program Management Plan
VA ICJIS Program Management Plan 1 08/29/01 Program Management Plan VA Integrated Criminal Justice Information System (ICJIS) Program 1. Introduction. The Commonwealth of Virginia Integrated Criminal Justice
More informationPROJECT MANAGEMENT PLAN Outline VERSION 0.0 STATUS: OUTLINE DATE:
PROJECT MANAGEMENT PLAN Outline VERSION 0.0 STATUS: OUTLINE DATE: Project Name Project Management Plan Document Information Document Title Version Author Owner Project Management Plan Amendment History
More informationSTATE BOARD OF ELECTIONS P.O. BOX 6486, ANNAPOLIS, MD 21401-0486 PHONE (410) 269-2840
MARYLAND STATE BOARD OF ELECTIONS P.O. BOX 6486, ANNAPOLIS, MD 21401-0486 PHONE (410) 269-2840 Bobbie S. Mack, Chairman David J. McManus, Jr., Vice Chairman Rachel T. McGuckian Patrick H. Murray Charles
More informationMinnesota Health Insurance Exchange Project (MNHIX) Deliverable Definition Document (DDD) For Project Management Plan Date: 07-31-2012
Minnesota Health Insurance Exchange Project (MNHI) Deliverable Definition Document (DDD) For Project Plan Date: 07-31-2012 11/9/2012 1:18 PM Page 1 of 8 1. High Level Deliverable Description The Project
More informationColorado Department of Health Care Policy and Financing
Colorado Department of Health Care Policy and Financing Solicitation #: HCPFRFPCW14BIDM Business Intelligence and Data Management Services (BIDM) Appendix B BIDM Project Phases Tables The guidelines for
More informationDevelop Project Charter. Develop Project Management Plan
Develop Charter Develop Charter is the process of developing documentation that formally authorizes a project or a phase. The documentation includes initial requirements that satisfy stakeholder needs
More informationMNLARS Project Audit Checklist
Audit Checklist The following provides a detailed checklist to assist the audit team in reviewing the health of a project. Relevance (at this time) How relevant is this attribute to this project or audit?
More informationPHASE 3: PLANNING PHASE
PHASE 3: PLANNING PHASE The Planning Phase focuses principally on required project planning work. Proper comprehensive project planning is essential to a successful IT project, and incomplete project planning
More informationThis is the software system proposal document for the <name of the project> project sponsored by <name of sponsor>.
Guide to Preparing the SOFTWARE PROJECT MANAGEMENT PLAN R. Buckley CSc 190 Senior Project Department of Computer Science - College of Engineering and Computer Science California State University, Sacramento
More informationCrosswalk Between Current and New PMP Task Classifications
Crosswalk Between Current and New PMP Task Classifications Domain 01 Initiating the Project Conduct project selection methods (e.g., cost benefit analysis, selection criteria) through meetings with the
More informationAppendix 2-A. Application and System Development Requirements
Appendix 2-A. Application and System Development Requirements Introduction AHRQ has set up a Distributed Systems Engineering Lab (DSEL) to support all internal development efforts and provide a facility
More informationSOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK
Office of Safety and Mission Assurance NASA-GB-9503 SOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK AUGUST 1995 National Aeronautics and Space Administration Washington, D.C. 20546 PREFACE The growth in cost
More informationPositive Train Control (PTC) Program Management Plan
Positive Train Control (PTC) Program Management Plan Proposed Framework This document is considered an uncontrolled copy unless it is viewed online in the organization s Program Management Information
More informationDesign Consultant Project Management Requirements
Design Consultant Project Management Requirements Version 2 April 25, 2013 AWTP Program Design Consultant Contents 1.0 Introduction... 1 2.0 General Management... 1 3.0 Project Management Plan... 1 4.0
More informationBiometrics Enterprise Architecture Project Management Plan (BMEA PMP)
Biometrics Enterprise Architecture Project Management Plan (BMEA PMP) Version 1.0 Prepared by: Date: November 24, 2008 Revision History Purpose Revision Date Level 11/17/2009 First Draft 1.0 Responsible
More informationAssessment of NCTD Program Management Framework for Positive Train Control Program
Assessment of NCTD Program Management Framework for Positive Train Control Program Subtask 2: Analysis Gap Analysis Prepared for: Brad Hansen, M.S., PMP Director, PMO Capital Projects May 2013 0 icfi.com/transportation
More informationConstruction Management Standards of Practice
Construction Management Standards of Practice 2010 Edition Advancing Professional Construction/ Program Management Worldwide. 7926 Jones Branch Drive, Suite 800 McLean, VA 22102-3303 USA 703.356.2622 703.356.6388
More informationProject Integration Management
Integration Initiating ning Executing Monitoring & Controlling Closing 4.1 Develop Charter Statement Of Work Business Case 4.2 Develop 4.3 Direct and Manage Work 4.4 Monitor and Control Work 4.5 Perform
More informationTerms of References for Infrastructure Expert
1. BACKGROUND Terms of References for Infrastructure Expert Sustainable Development Account Moldova (SDA Moldova) (hereinafter the institution) is a public entity established by the Government of the Republic
More informationIT Project Management Practices Guide
IT Project Management Practices Guide Introduction The IT Project Management Practices Guide (Guide) contains a repeatable, institutionwide approach for the management of application development and/or
More informationThe 10 Knowledge Areas & ITTOs
This document is part of a series that explain the newly released PMBOK 5th edition. These documents provide simple explanation and summary of the book. However they do not replace the necessity of reading
More informationMinnesota Health Insurance Exchange (MNHIX)
Minnesota Health Insurance Exchange (MNHIX) Project Status Report Week Ending: 09-19-2012 Page - 1 Executive Summary The Executive Summary provides an executive level review of general project activities,
More informationProject Knowledge Areas
From Houston S: The Project Manager s Guide to Health Information Technology Implementation. Chicago: HIMSS; 2011; pp 27 39. This book is available on the HIMSS online bookstore at www. himss.org/store.
More informationPMP Examination Tasks Puzzle game
PMP Examination Tasks Puzzle game Here is a great game to play to test your knowledge of the tasks you will be tested on in the actual examination. What we have done is take each of the domain tasks in
More informationCONFIGURATION MANAGEMENT PLAN GUIDELINES
I-680 SMART CARPOOL LANE PROJECT SYSTEM ENGINEERING MANAGEMENT PLAN CONFIGURATION MANAGEMENT PLAN GUIDELINE SECTIONS: PLAN GUIDELINES 1. GENERAL 2. ROLES AND RESPONSIBILITIES 3. CONFIGURATION MANAGEMENT
More informationPHASE 3: PLANNING PHASE
PHASE 3: PLANNING PHASE The ning Phase focuses principally on required project planning work. Proper comprehensive project planning is essential to a successful IT project, and incomplete project planning
More informationBest Practices Statement Project Management. Best Practices for Managing State Information Technology Projects
State of Arkansas Office of Information Technology 124 W. Capitol Ave. Suite 990 Little Rock, AR 72201 501.682.4300 Voice 501.682.4020 Fax http://www.cio.arkansas.gov/techarch Best Practices Statement
More informationTREASURY INSPECTOR GENERAL FOR TAX ADMINISTRATION
TREASURY INSPECTOR GENERAL FOR TAX ADMINISTRATION The Customer Account Data Engine 2 Systems Development Guidelines; However, Process Improvements Are Needed to Address Inconsistencies September 30, Year
More informationIntegrity 10. Curriculum Guide
Integrity 10 Curriculum Guide Live Classroom Curriculum Guide Integrity 10 Workflows and Documents Administration Training Integrity 10 SCM Administration Training Integrity 10 SCM Basic User Training
More informationSoftware Project Management Plan (SPMP)
Software Project Management Plan (SPMP) The basic template to be used is derived from IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans. The following is a template for the SPMP.
More information<Company Name> <Project Name> Software Development Plan. Version <1.0>
Version [Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=infoblue)
More informationOrganization. Project Name. Project Overview Plan Version # Date
Project Overview Plan Template Organization Project Name Project Overview Plan Version # Date REVISION HISTORY VERSION # REVISION DATE COMMENT 1 APPROVALS: Authorized Signature DATE 2 Table of Contents
More informationCONTENTS. Preface. Acknowledgements. 1. Introduction and Overview 1 Introduction 1 Whatis the CMMI"? 2 What the CMMI* is Not 3 What are Standards?
Preface Acknowledgements xi xiii 1. Introduction and Overview 1 Introduction 1 Whatis the CMMI"? 2 What the CMMI* is Not 3 What are Standards? 3 2. Summaryof CMMI-SW 5 The CMM*-SW 5 CMMI--SW Continuous
More informationScope of Work Microsoft Infrastructure Upgrade
Introduction Scope of Work Microsoft Infrastructure Upgrade The University of Texas M. D. Anderson Cancer Center (M. D. Anderson) in Houston, Texas, celebrating six decades of Making Cancer History, is
More informationProject Management Concepts, Methods, and Techniques
Project Management Concepts, Methods, and Techniques Claude H. Maley Uffi\ CRC Press Taylor & Francis Croup Boca Raton London New York CRC Press is an imprint of the Taylor & Francis Croup, an Informa
More informationProject Management Institute. Construction. Extension to. A Guide to the Project Management Body of Knowledge. PMBOK Guide 2000 Edition.
Project Management Institute Construction Extension to A Guide to the Project Management Body of Knowledge PMBOK Guide 2000 Edition Provisional Construction Extension to A Guide to the Project Management
More informationTHE PROJECT MANAGEMENT KNOWLEDGE AREAS
THE PROJECT MANAGEMENT KNOWLEDGE AREAS 4. Project Integration Management 5. Project Scope Management 6. Project Time Management 7. Project Cost Management 8. Project Quality Management 9. Project Human
More informationOE PROJECT CHARTER TEMPLATE
PROJECT : PREPARED BY: DATE (MM/DD/YYYY): Project Name Typically the Project Manager Project Charter Last Modified Date PROJECT CHARTER VERSION HISTORY VERSION DATE (MM/DD/YYYY) COMMENTS (DRAFT, SIGNED,
More information<PROJECT NAME> PROJECT MANAGEMENT PLAN
PROJECT MANAGEMENT PLAN Version VERSION HISTORY [Provide information on how the development and distribution of the Project Management Plan was controlled and tracked.
More informationSoftware Quality Subcontractor Survey Questionnaire INSTRUCTIONS FOR PURCHASE ORDER ATTACHMENT Q-201
PURCHASE ORDER ATTACHMENT Q-201A Software Quality Subcontractor Survey Questionnaire INSTRUCTIONS FOR PURCHASE ORDER ATTACHMENT Q-201 1. A qualified employee shall be selected by the Software Quality Manager
More informationInformation Technology Project Oversight Framework
i This Page Intentionally Left Blank i Table of Contents SECTION 1: INTRODUCTION AND OVERVIEW...1 SECTION 2: PROJECT CLASSIFICATION FOR OVERSIGHT...7 SECTION 3: DEPARTMENT PROJECT MANAGEMENT REQUIREMENTS...11
More informationREQUEST FOR PROPOSALS. Business Continuity Planning Consultant Services APPENDIX C RFP STATEMENT OF WORK EXHIBITS 1-3
REQUEST FOR PROPOSALS Business Continuity Planning Consultant Services APPENDIX C RFP STATEMENT OF WORK EXHIBITS 1-3 EXHIBITS EXHIBIT 1 EXHIBIT 2 EXHIBIT 3 Glossary of Terms and Acronyms Contract Discrepancy
More informationQuick Reference Guide Interactive PDF Project Management Processes for a Project
Project Processes for a Project Click the Knowledge Area title (below and left in blue underline) to view the details of each Process Group. Project Process Groups and Knowledge Areas Mapping Project Process
More informationInput, Output and Tools of all Processes
1 CIS12-3 IT Project Management Input, Output and Tools of all Processes Marc Conrad D104 (Park Square Building) Marc.Conrad@luton.ac.uk 26/02/2013 18:22:06 Marc Conrad - University of Luton 1 2 Mgmt /
More informationVoteCal Statewide Voter Registration System Project. Master Project Management Plan. Version 1.2
VoteCal Statewide Voter Registration System Project Master Project Management Plan Version 1.2 October 2010 October 2010 i REVISION HISTORY REVISION # DATE OF RELEASE OWNER SUMMARY OF CHANGES 0.1 3/12/2009
More informationPOLICY STATEMENT Commonwealth of Pennsylvania Department of Corrections
POLICY STATEMENT Commonwealth of Pennsylvania Department of Corrections Policy Subject: Policy Number: Project Management 1.1.5 Date of Issue: Authority: Effective Date: May 29, 2009 Signature on File
More information5.1 4.1 4.2 4.3 PROCESS GROUP: PLANNING PROCESS GROUP: INITIATION. Oracle Projects. PMBOK Oracle Mapping. Scope Planning. Develop Project Charter
Develop Project Charter Develop Preliminary Project Scope Statement Develop Project Management Plan Scope Planning PROCESS GROUP: INITIATION 4.1 The project charter serves as the input document for the
More informationConstruction Management System (CMS) Deliverable Review Process
Construction Management System (CMS) Deliverable Review Process State of California Department of Transportation Division of Construction December 21, 2009 Version 1.0 Approvals Name: Title: Mark Leja
More informationRequest for Resume (RFR) for Project Manager (Senior) CATS+ Master Contract All Master Contract Provisions Apply. Section 1 General Information
Request for Resume (RFR) for Project (Senior) Section General Information RFR Number: (Reference BPO Number) Functional Area (Enter One Only) Q00R00 BPO # 060B900 in ADPICS Functional Area 0 IT Management
More informationIT Project Management Methodology. Project Scope Management Support Guide
NATIONAL INFORMATION TECHNOLOGY AUTHORITY - UGANDA IT Project Management Methodology Project Scope Management Support Guide Version 0.3 Version Date Author Change Description 0.1 23 rd Mar, 2013 Gerald
More informationIntegration Mgmt / Initiating Process Group 4.1 Develop Project Charter
1 Mgmt / Initiating Process Group 4.1 Develop Project Charter Project statement of work Business case Agreements Facilitation techniques Project charter 26/02/2013 18:23:36 1 2 Mgmt / Planning Process
More information!"#$%&'(%)*$+ :%;$)*%<&%6 4.7&68'9"/6")& 0)1.%$2.3*%./'4"55*)6 ,&+-%$+./ !"#$%&##'()*+&## Figure 1: Five OSP Dimensions
!""#!$%&'(#)$*+,(-*(.&%/# &0*$1!"#$%&'(%)*$+ :%;$)*%
More informationProject Management Methodology
Project Management Methodology 1/6/2015 PAGE 1 OF 28 Version 2.0 Contents INTRODUCTION... 4 1. Overview... 4 PHASE 1 PROJECT INITIATION... 5 1. Governance Model... 6 2. Project Prioritization Process...
More informationLMI Aerospace PROJECT MANAGEMENT PLAN ACCESS REQUEST PROCESS IMPROVEMENT FEBRUARY 7, 2012
PROJECT MANAGEMENT PLAN ACCESS REQUEST PROCESS IMPROVEMENT FEBRUARY 7, 2012 TABLE OF CONTENTS INTRODUCTION... 2 PROJECT MANAGEMENT APPROACH... 2 PROJECT SCOPE... 2 MILESTONE LIST... 2 SCHEDULE BASELINE
More informationThe Project Management Plan will be used to guide, communicate and coordinate project efforts.
F.1 General Implementation Contractor Deliverables include critical system planning and development components. Sufficient deliverables have been identified at key steps in the project to guide the project
More informationManagement. Project. Software. Ashfaque Ahmed. A Process-Driven Approach. CRC Press. Taylor Si Francis Group Boca Raton London New York
Software Project Management A Process-Driven Approach Ashfaque Ahmed CRC Press Taylor Si Francis Group Boca Raton London New York CRC Press is an imprint of the Taylor St Francis Croup, an Informa business
More informationCity of Casper, Wyoming. Request for Proposals. for. Food Service Point of Sale Solution
City of Casper, Wyoming Request for Proposals for Food Service Point of Sale Solution The City of Casper, Wyoming (hereinafter referred to as City ) is seeking qualification statements and service proposals
More informationSOFTWARE ASSURANCE STANDARD
NOT MEASUREMENT SENSITIVE National Aeronautics and NASA-STD-8739.8 w/change 1 Space Administration July 28, 2004 SOFTWARE ASSURANCE STANDARD NASA TECHNICAL STANDARD REPLACES NASA-STD-2201-93 DATED NOVEMBER
More informationSkatteudvalget 2014-15 (2. samling) SAU Alm.del Bilag 48 Offentligt. Programme, Project & Service Management Analysis
Skatteudvalget 2014-15 (2. samling) SAU Alm.del Bilag 48 Offentligt Programme, Project & Service Management Analysis Table of Content 1 Executive Summary... 3 1.1 Scope of Work... 3 1.2 Methodology for
More informationApplication of Standard Project Management Processes in Fiber Optic Cable Plant Project Management. Introduction. Alfred Sankara, DigiBridge TelCo
Application of Standard Project Management Processes in Fiber Optic Cable Plant Project Management Alfred Sankara, DigiBridge TelCo Introduction The Project Management Institute (PMI) is the world's leading
More informationIT Project: System Implementation Project Template Description
2929 Campus Drive Suite 250 IT Project: System Implementation Project Template Description Table of Contents Introduction... 2 Project Phases... 3 Initiation & Requirements Gathering Milestone... 3 Initiation
More informationOffice of Small and Disadvantage Business Utilization (OSDBU) Logistics Support Contract
Office of Small and Disadvantage Business Utilization (OSDBU) Logistics Support Contract 1. Introduction. The Department of Veteran Affairs (VA) Office of Small and Disadvantaged Business Utilization (OSDBU)
More informationID Task Name Time Pred
0 UC Modernization Project Plan 1115 d 1 1 Phase I - Business Case Development and Competitive Procurement 205 d 2 1.1 Complete Initial Feasibility Study 55 d 3 1.2 Prepare and Issue LBR 30 d 2 4 1.3 Competitive
More informationPHASE 8: IMPLEMENTATION PHASE
PHASE 8: IMPLEMENTATION PHASE The Implementation Phase has one key activity: deploying the new system in its target environment. Supporting actions include training end-users and preparing to turn the
More informationIndependent Verification and Validation of SAPHIRE 8 Software Project Plan
INL/EXT-09-17022 Rev. 2 Independent Verification and Validation of SAPHIRE 8 Software Project Plan March 2010 The INL is a U.S. Department of Energy National Laboratory operated by Battelle Energy Alliance
More informationADVANCED CUSTOMER SUPPORT ORACLE FUNCTIONAL HELP DESK EXHIBIT
ADVANCED CUSTOMER SUPPORT ORACLE FUNCTIONAL HELP DESK EXHIBIT This exhibit incorporates by reference the terms of the order for Oracle Functional Help Desk services. A. Definitions. End Users means those
More informationGeneral Notes Time allowed 1 hour. Answer all 60 multiple choice questions Use the proforma answer sheet provided.
Introductory Certificate The APM Project Fundamentals Qualification. Examination paper Candidate Number Date Location Examination Paper Sample Paper v1.4 General Notes Time allowed 1 hour. Answer all 60
More informationDRAFT REGULATORY GUIDE
U.S. NUCLEAR REGULATORY COMMISSION August 2012 OFFICE OF NUCLEAR REGULATORY RESEARCH Division 1 DRAFT REGULATORY GUIDE Contact: K. Sturzebecher (301) 251-7494 DRAFT REGULATORY GUIDE DG-1206 (Proposed Revision
More informationMedicaid Eligibility and Enrollment (EE) Implementation Advanced Planning Document (IAPD) Template. Name of State Medicaid Agency:
Name of State: Name of State Medicaid Agency: Name of Contact(s) at State Medicaid Agency: E-Mail Address(es) of Contact(s) at State Medicaid Agency: Telephone Number(s) of Contact(s) at State Medicaid
More informationProject Management Certificate (IT Professionals)
Project Management Certificate (IT Professionals) Whether your field is architecture or information technology, successful planning involves a carefully crafted set of steps to planned and measurable goals.
More informationITRM Guideline CPM 110-01 Date: January 23, 2006 SECTION 4 - PROJECT EXECUTION AND CONTROL PHASE
PROJECT MANAGEMENT GUIDELINE SECTION 4 - PROJECT EXECUTION AND CONTROL PHASE Table of Contents Introduction... 3 Project Execution and Control Phase Overview... 3 Activities and Documents in the Execution
More informationProject Management Body of Knowledge (PMBOK) (An Overview of the Knowledge Areas)
Project Management Body of Knowledge (PMBOK) (An Overview of the Knowledge Areas) Nutek, Inc. 3829 Quarton Road, Suite 102 Bloomfield Hills, Michigan 48302, USA. Phone: 248-540-4827, Email: Support@Nutek-us.com
More informationEastern Illinois University EISE Configuration Management Plan
Eastern Illinois University EISE Configuration Management Prepared by: Bill Witsman Version: 10.0 Create Date: April 13, 2005 Approval Date: Last Revision Date: December 17, 2009 CM Analyst: Project Manager:
More informationPROJECT MANAGEMENT METHODOLOGY SECTION 3 -- PLANNING PHASE
PROJECT MANAGEMENT METHODOLOGY SECTION 3 -- PLANNING PHASE Table of Contents Introduction...3-1 Overview...3-1 The Process and the Project Plan...3-1 Project Objectives and Scope...3-1 Work Breakdown Structure...3-1
More informationProgram Management Professional (PgMP) Examination Content Outline
Program Management Professional (PgMP) Examination Content Outline Project Management Institute Program Management Professional (PgMP ) Examination Content Outline April 2011 Published by: Project Management
More informationITRM Guideline CPM 110-01 Date: January 23, 2006 SECTION 5 PROJECT CLOSEOUT PHASE
PROJECT MANAGEMENT GUIDELINE SECTION 5 PROJECT CLOSEOUT PHASE Table of Contents Introduction... 3 Project Closeout Phase... 3 Activities and Documents in the Closeout Phase... 4 Project Closeout Task...
More informationRequest for Proposal for Application Development and Maintenance Services for XML Store platforms
Request for Proposal for Application Development and Maintenance s for ML Store platforms Annex 4: Application Development & Maintenance Requirements Description TABLE OF CONTENTS Page 1 1.0 s Overview...
More informationThe Project Management Knowledge Areas as defined by PMI (PMBOK, 2004)
The Project Management Knowledge Areas as defined by PMI (PMBOK, 2004) is the processes required to ensure that the various elements of the project are properly coordinated. the processes required to ensure
More informationProject Management Plan for the VDI Data Center Project
Project Management Plan for the VDI Data Center Project Prepared by: Moe Yousof A paper submitted to the Project Management Training Program in partial fulfillment of the requirements for the Project Management
More information8. Master Test Plan (MTP)
8. Master Test Plan (MTP) The purpose of the Master Test Plan (MTP) is to provide an overall test planning and test management document for multiple levels of test (either within one project or across
More informationoutput: communications management plan
Q1. (50 MARKS) A. List the nine PMBOK knowledge areas and give a one sentence description of the purpose of each knowledge area along with at least one output (document etc.) and its purpose. 1.Project
More informationProject Audit & Review Checklist. The following provides a detailed checklist to assist the PPO with reviewing the health of a project:
Project Audit & Review Checklist The following provides a detailed checklist to assist the PPO with reviewing the health of a project: Relevance (at this time) Theory & Practice (How relevant is this attribute
More informationRegulatory Guide 1.169 Configuration Management Plans for Digital Computer Software Used in Safety Systems of Nuclear Power Plants
Regulatory Guide 1.169Configuration Managemen... Page 1 of 10 September 1997 Regulatory Guide 1.169 Configuration Management Plans for Digital Computer Software Used in Safety Systems of Nuclear Power
More informationCONTENTS. List of Tables List of Figures
Prelims 13/3/06 9:11 pm Page iii CONTENTS List of Tables List of Figures ix xi 1 Introduction 1 1.1 The Need for Guidance on ERP System Validation 1 1.2 The Need to Validate ERP Systems 3 1.3 The ERP Implementation
More informationProject Type Guide. Project Planning and Management (PPM) V2.0. Custom Development Version 1.1 January 2014. PPM Project Type Custom Development
Project Planning and Management (PPM) V2.0 Project Type Guide Custom Development Version 1.1 January 2014 Last Revision: 1/22/2014 Page 1 Project Type Guide Summary: Custom Development Custom software
More informationPROJECT MANAGEMENT PLAN <PROJECT NAME>
PROJECT MANAGEMENT PLAN TEMPLATE This Project Management Plan Template is free for you to copy and use on your project and within your organization. We hope that you find this template useful and welcome
More information