Communication Description Frequency Author(s) Recipient(s) Location Approved? Tool Summarize progress of the project and Sponsor, team upcoming activities, Project Status Reports lead, project SharePoint No including reporting Manager team budget and schedule variance Meeting Written record of a See meeting Facilitator or attendees and Minutes SharePoint Yes meeting table above designee other interested parties Quality Management Perform Quality Assurance Following are the quality assurance processes for this project: Integrated change control verifies that any changes to quality during the project are discussed – and approved by the appropriate person Monitoring schedule and cost variance ensures oversight of the project schedule and cost in – relation to the project baseline to provide visibility to any potential project schedule or cost issues Definition of deliverable acceptance criteria and/or expectations verifies that the deliverables – are of an acceptable quality and meet the expectations customer’s Acceptance management verifies that the deliverables are of acceptable quality and that they – meet the established project requirements Peer review of project management documents provides documents associated with – management of this project (e.g., business case, project charter, and this project plan) a review by the ITD project management office for clarity and implementations of previous lessons learned Following are the quality assurance processes for the product produced by this project: Add or remove as necessary. Web design walkthroughs with and web design team verifies ITD’s software architect – compliance with the design specifications and web design quality Prototype walkthroughs screen shots are shown to the appropriate user group to confirm that – the requirements were understood and the system designed correctly Usability testing (before development) provides further validation that the requirements were – understood and the system designed correctly (while no databases are in place, this is used to walk users through the application and determine if requirements need to be clarified or changed before the design is complete) Code walkthroughs with software architect verifies compliance with the design ITD’s – specifications and code quality
Communication Tool Description Frequency Author(s) Recipient(s) Location Approved? Status Reports Summarize progress of the project and upcoming activities, including reporting budget and schedule variance Project Manager Sponsor, team lead, project team SharePoint No Minutes Written record of a meeting See meeting table above Facilitator or designee Meeting attendees and other interested parties SharePoint Yes Quality Management Perform Quality Assurance Following are the quality assurance processes for this project: Integrated change control – verifies that any changes to quality during the project are discussed and approved by the appropriate person Monitoring schedule and cost variance – ensures oversight of the project schedule and cost in relation to the project baseline to provide visibility to any potential project schedule or cost issues Definition of deliverable acceptance criteria and/or expectations – verifies that the deliverables are of an acceptable quality and meet the customer’s expectations Acceptance management – verifies that the deliverables are of acceptable quality and that they meet the established project requirements Peer review of project management documents – provides documents associated with management of this project (e.g., business case, project charter, and this project plan) a review by the ITD project management office for clarity and implementations of previous lessons learned Following are the quality assurance processes for the product produced by this project: Add or remove as necessary. Web design walkthroughs with ITD’s software architect and web design team – verifies compliance with the design specifications and web design quality Prototype walkthroughs – screen shots are shown to the appropriate user group to confirm that the requirements were understood and the system designed correctly Usability testing (before development) – provides further validation that the requirements were understood and the system designed correctly (while no databases are in place, this is used to walk users through the application and determine if requirements need to be clarified or changed before the design is complete) Code walkthroughs with ITD’s software architect – verifies compliance with the design specifications and code quality
Project%20Plan%20Template%20-%20under%20$250K%20ITD%20SD.docx