1. Executive Project Kickoff

2. Agenda Meeting Objectives and Introduction
Project History and Overview
SOW Review and Scope Confirmation
Project Approach
Project Structure
Project Team and Organization
Roles and Responsibilities
External Stakeholders
Facilities
Communication Management
Controlling and Sign-Off
Risks & Issues Management
Conditions of Satisfaction
Additional Project Planning Sessions and Actions
Q&A

3. Meeting Objectives and Introduction
Introduce [Customer Name] and [Partner Name] Project Management Teams
Confirm Engagement Objectives
Confirm Scope and Review Current WBS
Confirm Project Approach and Structure
Conduct Stakeholder Analysis
Determine Customer Conditions of Satisfaction (COS)
Schedule Additional Project Planning Sessions

4. Project Management Team
Name
Role
Commitment
Project Manager
Full-time
Engagement Manager
Part-Time
Relationship

5. Project History & Overview
Company Background
Project (Sales) History
Opportunity Overview & Project Definition
Project Vision
Project Approach
Business Objectives
Technical Objectives
Project Vision– Describe the project objectives that are identified to meet some or all of the customer’s business goals.
Business Objectives– Describe the customer’s business goals in a bulleted list. The list should focus on business needs and goals---it should not include specific technologies or specific products. Define why the customer needs the technologies and the business problems that need to be resolved.
Project Approach – Discuss whether a Waterfall or Agile Project approach is being taken and the differences or impact this will have on the projects execution

6. Review SOW and Confirm Scope
Solution
Sites, Locations & Divisions
Business Processes
Requirements & Configuration
Custom Coding
Integration & Interfaces
Training
Testing
Data Migration
Add other items as defined in Project Scope Statement.

7. Project Scope: High-level Out-of-Scope
Business Process Re-Engineering
Infrastructure Deployment
Post Operational Solution Support
Add additional “out of scope” activities as appropriate for the project.

8. Project Approach – Timeline & MilestonesID
Task Name Q 1 2
Jan
Feb
Mar
Apr
May
Jun
Analysis
Design 3
Development 4
Deployment 5
Operation
Jul
Aug
Sep
Duration (
Range ) -
weeks 8 15 20 6
Slide to be used if a Waterfall Project Type (Standard, Enterprise, Rapid or Upgrade) is being used.

9. Project Approach – Timeline & MilestonesQ 1 Q 2 Q 3
Duration ID
Task Name (
Range )
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep 1
Agile Preparation 2 - 4
weeks 2
Agile Execution
4 weeks per sprint 3
Deployment
3 – 6 weeks 4
Operation 2 - 4
weeks
Slide to be used if an Agile Project Type is being used

10. Project Approach - Methodology
Provide a brief overview of Microsoft Dynamics Sure Step including methodologies and components. Give a high-level view of benefits to the customer.
(Proven methods, best practices, reduced risk, speeds implementation, etc. Details will be expanded upon in the next slide.)

11. Project Approach – Project Management
Briefly describe the project management steps, strategies, and tools that will help manage a highly-successful project.

12. Project Approach: Key Deliverables
Project Plan
Training (Overview, Core & TTT)
Functional Requirements Document & Fit Gap Analysis
Infrastructure Design
Functional & Technical Design Documents
Solution Design Document
Completion of Process & Integration Testing
Completion of User Acceptance Testing
Final Data Migration
Production System
Project Closure Report
Slide to be used if a Waterfall Project Type (Standard, Enterprise, Rapid or Upgrade) is being used.
Add more items as appropriate to the specific project.

13. Project Approach: Key Deliverables
Project Plan
Training (Overview, Core & TTT)
Solution Backlog
Integration Strategy
Infrastructure Design
Completion of Process & Integration Testing
Completion of User Acceptance Testing
Final Data Migration
Production System
Project Closure Report
Slide to be used if an Agile Project Type is being used
Add more items as appropriate to the specific project.

14. Project Structure: Partner Team Structure
Name
Role
Commitment
Full-Time
Part-Time
Relationship

15. Project Structure: Customer Team Structure
Name
Role
Commitment
Full-Time
Part-Time
Relationship

16. Project Structure: Project Organization
This is an example diagram confirming the organization relationships and how the project will be structured. This illustration should show lines of communication between the customer and partner project teams.

17. Project Structure: Roles and Responsibilities
Task
Project Manager
Customer Project Manager
Solution Architect
Application Consultant
Technology Consultant
Development Consultant
IT Manager
BDM
Key User …
Define Project Roles A R C I
Assign Resources to Project
Assign Work Package to Resource -
Estimate Task V S
Schedule Task
Slide to be used if a Waterfall Project Type (Standard, Enterprise, Rapid or Upgrade) is being used.
Extended RACI-Matrix:
R Responsible, implying the main responsibility in doing/delivering effort and skill.
A Accountable, implying management (overrides R when both are implied).
C Consultative, implying assistance (both active and advisory).
I Informed, implying a requirement of the one responsible to report on the task.
V Verify, implying a check against the defined scope and conditions of quality standards.
S Sign-off, implying the actions of review, validation and acceptance.

18. Project Structure: Roles and Responsibilities
Task
Project Manager
Customer Project Manager
Solution Architect
Application Consultant
Sprint Cycle Manager
Build Manager
Technology Consultant
Development Consultant
IT Manager
BDM
Key User …
Define Project Roles A R C I
Assign Resources to Project
Assign Work Package to Resource -
Estimate Task V S
Schedule Task
Slide to be used if an Agile Project Type is being used.
Extended RACI-Matrix:
R Responsible, implying the main responsibility in doing/delivering effort and skill.
A Accountable, implying management (overrides R when both are implied).
C Consultative, implying assistance (both active and advisory).
I Informed, implying a requirement of the one responsible to report on the task.
V Verify, implying a check against the defined scope and conditions of quality standards.
S Sign-off, implying the actions of review, validation and acceptance.

19. Project Structure: External Stakeholders
Name
Role
Organization

20. Project Structure: Communication Management
Communication Plan
Reporting &Meetings
Meeting Minutes
Project Status Meetings & Reporting
Issues & Risks Logs
Kick-Off Meetings
Executive Steering Committee Meetings
Phase Tollgate Reviews
Workshops
Collaboration & Documentation Repository
Planning project communications will inform and educate team members about the project, objectives, progress and impact of day-to-day activities. Identifying the right communication channels facilitates an effective communication between individuals and teams. For large and complex projects it might be necessary to limit formal communication channels to keep the project communication manageable. Rules, guidelines and commitments for the project communication need to be described in the Communication Plan.
Below is a list of typical components of a Communication Plan:
         Communication Types – What type of communication will happen when? Who is the owner and who are the recipients or attendees?
         Project Repository – Explains the location and the structure for storing, sharing and maintaining the project documentation and information.
         Project Content Management – A list of managed documents, the owner, recipients who should know the content and the latest version of the document. This list includes also the different templates that should be used during the project execution.
         Contact List – A list of all active and supportive persons involved in the implementation project.
         Escalation Path – A defined path for how escalations need to be initiated. Who should escalate to whom?
         Confidential and Sensitive Information – Provides general guidance on disclosing information and how such information needs to be handled.
Steps for building and establishing a Communication Plan include: Listing the stakeholders, determining their communication needs, establishing the Communication Plan, assigning responsibilities, implement and communicate the plan the Communication Plan within the project team and the project stakeholders.

21. Project Structure: Facilities
On-Site Requirements
Remote Connectivity
Building Access
Business Hours
Dress Code
Activities with Facilities Dependencies

22. Project Structure: Controlling and Sign-Off
Progress and Performance
Change Control Plan
Process
Initiating a change request
Core team review
Impact analysis (including cost regardless of implementation)
Project board review
Final disposition
Quality Management
Sign-Off & Approvals
Engagement Exit Criteria
Project Closure Process

23. Project Structure: Risks & Issues Management
Risk Management Planning
Managing the Three Major Risk Areas
Business
Technology
Project Execution
Issue Management Planning
Issue Resolution Management
Risks & Issues Escalations
Core Team
Project Steering Committee
Project risks include funding, schedule, contract, relationships and political risks. Technical risks may involve the risk of meeting a performance requirement.

24. Additional Project Planning Sessions & Actions
Finalize the Project Charter
Finalize the Work Breakdown Structure (WBS) & Project Plan
Review and Approve the Project Charter
Review and Approve the Project Plan
Initiate the Plan Project Kick-off
Review Outstanding Issues or Actions

25. Questions & Answers What are your questions? What are your concerns?
What was not mentioned during the Executive Kick-Off presentation?

26. Thank you.