WMS Work Management System Governance Governance Approach Governance identifies the key governance roles and responsibilities for the project. In addition to documenting the stakeholders involved in managing the project, this governance section covers who is responsible for approving project documents, who approves deliverables and who makes the final decision to accept the system and product. The escalation process for issues will also be defined. The objective of this section is to detail the structure of the project organization, and the methods by which it reaches official decisions and carries out regular business. This ensures commitment and effective management of the project in order to: Ensure the project remains on course to deliver products of the required quality to meet the business case Approve all major deliverables Authorize deviations through integrated change control Arbitrate on internal project conflicts Negotiate solutions to problems within the project if they arise, and between the project and external bodies Ensure communication between the vendors and project team is effective and consistent Process This section should be modified to meet specific project needs. For example, if the project is not a large project, there is language in the Project Sponsor section that should be taken out. Recommendation is to provide a description for each role that is noted on the RACI chart. Authority Stakeholders are all of the people that are in any way affected by the new product or service. Since the organization will rely on various stakeholders it is important to understand the roles and responsibilities. You may want to do a search on the various roles (e.g., project manager) mentioned in this project plan template to make sure your final version uses the same terminology (e.g., project manager vs. primary project manager, or state project manager vs. vendor project manager) Executive Steering Committee (ESC) ESCs are optional for projects with a budget below $250,000, as these projects are not governed by STD009-05. If your project is under $250,000 and will not be using an ESC, you may delete this section.
WMS Work Management System Governance Governance Approach Governance identifies the key governance roles and responsibilities for the project. In addition to documenting the stakeholders involved in managing the project, this governance section covers who is responsible for approving project documents, who approves deliverables and who makes the final decision to accept the system and product. The escalation process for issues will also be defined. The objective of this section is to detail the structure of the project organization, and the methods by which it reaches official decisions and carries out regular business. This ensures commitment and effective management of the project in order to: Ensure the project remains on course to deliver products of the required quality to meet the business case Approve all major deliverables Authorize deviations through integrated change control Arbitrate on internal project conflicts Negotiate solutions to problems within the project if they arise, and between the project and external bodies Ensure communication between the vendors and project team is effective and consistent Process This section should be modified to meet specific project needs. For example, if the project is not a large project, there is language in the Project Sponsor section that should be taken out. Recommendation is to provide a description for each role that is noted on the RACI chart. Authority Stakeholders are all of the people that are in any way affected by the new product or service. Since the organization will rely on various stakeholders it is important to understand the roles and responsibilities. You may want to do a search on the various roles (e.g., project manager) mentioned in this project plan template to make sure your final version uses the same terminology (e.g., project manager vs. primary project manager, or state project manager vs. vendor project manager) Executive Steering Committee (ESC) ESCs are optional for projects with a budget below $250,000, as these projects are not governed by STD009-05. If your project is under $250,000 and will not be using an ESC, you may delete this section.
Project%20Plan%20Template%20-%20vendor%20or%20over%20$250K.docx