...
What | Who/Target | Purpose | When/Frequency | Type/Method |
---|---|---|---|---|
Team Meetings | Entire project team. Individual meetings for sub-teams, technical team, and functional teams as appropriate. | To review detailed plans (tasks, assignments, and action items). | Regularly scheduled. Weekly is recommended for entire team. Weekly or bi-weekly for sub-teams as appropriate. If agile project, then daily scrums. | Meeting and Minutes (Weekly Project Status Report Template) |
Phase Transition Walk Throughs | Entire project team and user groups as appropriate. | To review work completed and demo deliverables prior to moving to next phase. | End of each project phase, as needed. | Presentation/Discussion |
Steering Committee Meetings (may only apply to larger projects) | Steering Committee and Project Manager. | Update Steering Committee on status and discuss critical issues. Work through issues and change requestss here before escalating to Sponsor(s). | Regularly Scheduled. Monthly is recommended. | Meeting and minutes |
Sponsor Meetings | Sponsor(s) and Project Manager. | Update Sponsor(s) on status and discuss critical issues. Seek approval for changes to project plan. | Regularly scheduled. Recommended monthly and also as needed when issues cannot be resolved, decisions need to be reached, or changes need to be made to project plan. | Meeting (see Sponsor Status Report Template) |
IS&T Project Reviews | IS&T extended senior staff and project supporters | Review project snapshot and overall health of the project. To identify and communicate potential risks and issues that may affect the schedule, budget, or deliverables | Quarterly review. Monthly to updae snapshot. | Review Session (see project snapshot report in Daptiv) |
Periodic demos and target presentations | Specific focus groups, Help Desk or end users | To gain input and build awareness of the project with special groups and keep groups abreast of project status. | As you complete critical phases or make major enhancements. | Presentation/Discussion |
...
What | Who/Target | Purpose | When/Freqency | Type/Method(s) |
---|---|---|---|---|
Training | End users, Help Desk | To prepare end users to utilize the system on roll out or during a pilot. To prepare help desk to be able to troubleshoot issues on rollout or during a pilot. | End of project or end of major phase. | Demos, workshops, hands-on, e-learning |
Post Project Review | Project Manager, key stakeholders, project supporters and sponsor(s). | Identify improment plans, lessons learned, what worked and what could have gone better. Review accomplishments. | Enof of project or end of major phase. | Meeting/Report |
...