<Enter Project Name here> <enter phase name> Phase Kick-Off Presentation

1. <Enter Project Name here> <enter phase name> Phase Kick-Off Presentation

2. Meeting Objectives: • Understand Project Goals, Scope and Constraints • Understand Target Project Timeline & Required Deliverables • Review/Accept Team Member Roles & Responsibilities • Review Key Project Risks/Issues • Review Key Project Assumptions

3. Project Description Give a short, narrative description about the project here. You need to keep all the information on this page within this single slide. Project Objectives: • objective 1 • objective 2 • objective 3 Project Benefits: • benefit 1 • benefit 2 • benefit 3 Project Constraints: • Timeline: {Original Timeline} • Cost: {Original Cost}

4. Scope: • In Scope: • <Enter major scope item 1> • <Enter major scope item 2> • <Enter major scope item x> • Out of Scope: • <Enter major OUT of scope item 1> • <Enter major OUT of scope item 2> • <Enter major OUT of scope item x> • Constraints: • Business Needs by Date: <Enter the date by which the business needs solution delivery> • Budget: <Enter the current phase and overall project budget constraints> • Phase Budget: $$,$$$ • Overall Project Budget: $$$,$$$ • Key Assumptions: • <Enter key assumption 1> • <Enter key assumption 2> • <Enter key assumption x>

5. Template Notes for User: This text box is informational to help you create this slide. Delete this text box with “red” text before publishing your final Project Kickoff presentation. This is where you need to insert the appropriate Status Overview slide from below, based on the phase that you are in.

6. Committed Completed Targeted Legend: • = Completed Phase: Business Issues Overall Status: Green, Yellow,Red Schedule: G Budget: Y Quality: R Business Issues xx/xx/xx xx/xx/xx Phase Milestones xx/xx/xx: Project Profile Approved xx/xx/xx: Project Steering Committee Established xx/xx/xx: Project Team Established xx/xx/xx: Project Kickoff Meeting Conducted xx/xx/xx: Detailed Business Requirements Schedule Completed xx/xx/xx: Project Management Plan Completed xx/xx/xx: Cost Benefit Analysis Document Completed xx/xx/xx: Phase-End Decision Point Meeting Business Requirements xx/xx/xx xx/xx/xx Design xx/xx/xx xx/xx/xx Construction xx/xx/xx xx/xx/xx Testing xx/xx/xx xx/xx/xx Implementation xx/xx/xx xx/xx/xx Post-Implementation xx/xx/xx xx/xx/xx Budget Summary Business Issues Phase Total Project

7. Committed Completed Targeted Legend: • = Completed Phase: Business Requirements Overall Status: Green, Yellow,Red Schedule: G Budget: Y Quality: R Business Issues xx/xx/xx xx/xx/xx Phase Milestones xx/xx/xx: Kick off Meeting Completed xx/xx/xx: Detailed Project Plan Completed xx/xx/xx: Process Model Completed xx/xx/xx: Business Requirements Completed xx/xx/xx: Technical Requirements Approved xx/xx/xx: Solution Recommendation Completed xx/xx/xx: Plans for Remaining Phases Completed xx/xx/xx: Decision Point Meeting Conducted Business Requirements xx/xx/xx xx/xx/xx Design xx/xx/xx xx/xx/xx Construction xx/xx/xx xx/xx/xx Testing xx/xx/xx xx/xx/xx Implementation xx/xx/xx xx/xx/xx Post-Implementation xx/xx/xx xx/xx/xx Business Issues Phase Total Project Budget Summary

8. Committed Completed Targeted Legend: • = Completed Phase: Design Overall Status: Green, Yellow,Red Schedule: G Budget: Y Quality: R Business Issues xx/xx/xx xx/xx/xx Phase Milestones xx/xx/xx: Release Strategy & Plan Completed xx/xx/xx: General Design Review Approved xx/xx/xx: General Design Decision Point Meeting Conducted xx/xx/xx: Detail Design Review Approved xx/xx/xx: Plans for Remaining Phases Completed xx/xx/xx: Phase-End Decision Point Meeting Conducted Business Requirements xx/xx/xx xx/xx/xx Design xx/xx/xx xx/xx/xx Construction xx/xx/xx xx/xx/xx Testing xx/xx/xx xx/xx/xx Implementation xx/xx/xx xx/xx/xx Post-Implementation xx/xx/xx xx/xx/xx Budget Summary Business Issues Phase Total Project

9. Committed Completed Targeted Legend: • = Completed Phase: Construction Overall Status: Green, Yellow,Red Schedule: G Budget: Y Quality: R Business Issues xx/xx/xx xx/xx/xx Phase Milestones xx/xx/xx: Development Environment(s) Ready & Signed Off xx/xx/xx: Deployment Strategy & Plan Signed Off xx/xx/xx: Test Environment(s) Ready and Signed Off xx/xx/xx: Code & Unit Testing Completed xx/xx/xx: Integration Test Cases Completed xx/xx/xx: System Test Cases Completed xx/xx/xx: Performance Test Cases Completed xx/xx/xx: User Acceptance Test Cases Completed xx/xx/xx: User Documentation & Training Completed xx/xx/xx: Plans for Remaining Phases Completed xx/xx/xx: Phase-End Decision Point Meeting Conducted Business Requirements xx/xx/xx xx/xx/xx Design xx/xx/xx xx/xx/xx Construction xx/xx/xx xx/xx/xx Testing xx/xx/xx xx/xx/xx Implementation xx/xx/xx xx/xx/xx Post-Implementation xx/xx/xx xx/xx/xx Budget Summary Business Issues Phase Total Project

10. Committed Completed Targeted Legend: • = Completed Phase: Testing Overall Status: Green, Yellow,Red Schedule: G Budget: Y Quality: R Business Issues xx/xx/xx xx/xx/xx Phase Milestones xx/xx/xx: Integration Test Exit Criteria Met xx/xx/xx: System Test Exit Criteria Met xx/xx/xx: User Acceptance Test Exit Criteria Met xx/xx/xx: Performance Test Exit Criteria Met xx/xx/xx: Deployment Readiness Test Exit Criteria Met xx/xx/xx: Business Process Changes Validated xx/xx/xx: User Acceptance Test Cases Completed xx/xx/xx: Production Support & Administration Document Approved xx/xx/xx: Plans for Remaining Phases Completed xx/xx/xx: Phase-End Decision Point Meeting Conducted Business Requirements xx/xx/xx xx/xx/xx Design xx/xx/xx xx/xx/xx Construction xx/xx/xx xx/xx/xx Testing xx/xx/xx xx/xx/xx Implementation xx/xx/xx xx/xx/xx Post-Implementation xx/xx/xx xx/xx/xx Budget Summary Business Issues Phase Total Project

11. Committed Completed Targeted Legend: • = Completed Phase: Implementation Overall Status: Green, Yellow,Red Schedule: G Budget: Y Quality: R Business Issues xx/xx/xx xx/xx/xx Phase Milestones xx/xx/xx: End-Users Training Completed xx/xx/xx: Implementation Checklist Verified xx/xx/xx: Solution Deployed xx/xx/xx: Warranty Period Completed xx/xx/xx: Production Support Turnover Completed xx/xx/xx: Phase-End Decision Point Meeting Conducted Business Requirements xx/xx/xx xx/xx/xx Design xx/xx/xx xx/xx/xx Construction xx/xx/xx xx/xx/xx Testing xx/xx/xx xx/xx/xx Implementation xx/xx/xx xx/xx/xx Post-Implementation xx/xx/xx xx/xx/xx Budget Summary Business Issues Phase Total Project

12. PSC Membership MemberAgency / Role xxxxx xxxxxx xxxxxxxx / xxxxxxxxxxxx • Template Notes for User: This text box is informational to help you create this slide. • Delete this text box with “red” text before submitting your final Project Kickoff presentation. • List the names of the Project Steering Committee members, the Agency that they represent, and their role within the Agency. • Project Steering Committee members must fulfill the following roles & responsibilities: • Sets business strategies within the targeted area; • Sets priorities and allocates resources (people and budgets); • Makes Go, No-Go, or Redirect decisions for any project in the business area throughout the entire project life cycle.

13. Template Notes for User: This text box is informational to help you create this slide. Delete this text box with “red” text before publishing your final Project Kickoff presentation. This is where you need to insert the appropriate Project Wheel slide from below, based on the phase that you are in. Please download the Project Wheel for your phase from the SDM Website and insert here. The Project Wheel templates are located on the SDM website, on the “Deliverable Templates” webpage. You will see a link called “Project Wheels”.

14. Template Notes for User: This text box is informational to help you create this slide. Delete this text box with “red” text before publishing your final Project Kickoff presentation. This is where you need to insert the appropriate Roles & Responsibilities slide from the SDM Website, based on the phase that you are in. Modify the roles and responsibilities as appropriate.

15. Critical Success Factors <List the things that MUST go right in order for the project to succeed. Should be no more than 5.> • <Enter CSF #1. For example: “An entity must be established to represent all agencies in definition of requirements for this enterprise-wide solution””. • <Enter CSF #2. For example: “Project Steering Committee members must have active, senior-level representation from Agency A and Agency B”. • <Enter CSF #3> • <Enter CSF #4> • <Enter CSF #5>”

16. Project Risk X X X HIGH INFORMATION PROBABILITY X X ACTION X LOW LOW HIGH Remove the “X” that does not apply. IMPACT Remove all X’s that do not apply. Current Risk: (Briefly describe the risk here) Impact to Project: (Briefly describe the impact here) Owner: (Insert single owner’s name here.) Due Date to Avoid Project Impact: mm/dd/yy Mitigation Strategy: (Describe the mitigation strategy here-Bullet points preferred). Template Notes for User: This text box is informational to help you create this slide. Delete this text box with “red” text before submitting your final Project Kickoff presentation. A risk is based on an unavoidable occurrence. However, there are measures that can be taken to mitigate the impact. If there is more than one risk, duplicate this page; if there are no risks, omit this page.

17. Project Issue X X X HIGH INFORMATION PROBABILITY X X X ACTION LOW LOW HIGH Remove the X that does not apply. IMPACT Remove all X’s that do not apply. Current Issue: (Briefly describe the issue here) Impact to Project: (Briefly describe the project impact here) Owner: (insert single owner’s name here) Due Date to Avoid Project Impact: mm/dd/yy Recommended Solution: (Describe the recommended solution here-Bullet points preferred) Template Notes for User: This text box is informational to help you create this slide. Delete this text box with “red” text before submitting your final Project Kickoff presentation. An issue causes a project roadblock, but can be resolved. Issues outside of the boundary of a project, or, those that cross organizations or projects, should be presented as risks. If there is more than one issue, duplicate this page. If there are no issues, omit this page.

18. Next Steps • Schedule Weekly Status Meeting (what’s a good day?) • Time Reporting • Anything else?

19. PMO Use Only Document Attributes Revision History