The project methodology provides the following opportunities for stakeholder engagement: Project Kick-off: At the start of our project we recommend inviting all project stakeholders to hear more about project goals, project approach and to generally orient to the work ahead. Discovery & Design Sessions: These sessions will focus on the needs of individual business units as well as considering end-to-end processes. We recommend inviting a large percentage of project stakeholders into these discussions to ensure their needs are heard. These sessions should provide an avenue for round-table discussion and open and honest dialogue. User Acceptance Testing Sessions: Testing sessions will provide an opportunity for end-users to test-drive the system well before deployment. These sessions serve to both provide critical feedback and further the engagement of stakeholders on the project. Documentation and Training: This project includes time to develop documentation and deliver comprehensive training to end-users of the system. It is our goal to build confidence in the new system by building capacity. Post Go-Live Metrics: This project will deliver reports and dashboards that demonstrate user adoption metrics. These tools will provide clear analysis as to how widespread usage is of the new system and actionable intelligence as to where attention is needed. Project Close / Debrief: A cross-section of stakeholders will be provided an opportunity to participate in the project debrief. Lessons learned in the project close can be applied to future projects. Open items can also be discussed and assigned through the project closing process so as to ensure any loose ends are neatly tied. Ongoing project activities that further support stakeholder engagement include: Governance Participation: The Governance section of the Project Management Plan formalize an approach to how individuals will lend their expertise or oversight to the project. Ongoing Communication: The Communication Plan section of the Project Management Plan describes how information will be shared with stakeholders throughout the project. Quality Management Plan Delivering a project on time and on-budget does not guarantee the project success. A project must also be delivered well – to meet quality expectations – to be considered successful. This section of the Project Management Plan will identify quality management processes built into the project methodology and describe quality management practices overall. Best Practices in Quality Management The following represent best practices in Quality Management that informed the content of this section of the plan:
IV. Acceptance & Agreement Acceptance of this document represents a key milestone of this project. Acceptance of this deliverable indicates agreement that its contents represent the direction provided by [Client Name]. For [Client Name]: Signed: ______________________________ Print Name: ______________________________ Print Title: ______________________________ Date: ______________________________ For Craftsman Technology Group: Signed: ______________________________ Print Name: ______________________________ Print Title: ______________________________ Date: ______________________________