APN Partner Deal Acceleration Program –

Project Plan

[Customer] – [Partner] – [Date]

Page | 1
1 TABLE OF CONTENTS
2 PROJECT OVERVIEW ................................................................................................................................................................. 3
2.1 EXECUTIVE SUMMARY ............................................................................................................................................................. 3
2.2 PROJECT SPONSOR(S) / STAKEHOLDER(S) / PROJECT TEAM .............................................................................................................. 3
2.3 PROJECT SUCCESS CRITERIA............................................................................................................................................... 3
2.4 ASSUMPTIONS .................................................................................................................................................................. 3
2.5 OUT OF SCOPE .................................................................................................................................................................. 4
3 SCOPE OF WORK - TECHNICAL PROJECT PLAN .......................................................................................................................... 4
4 SOLUTION ARCHITECTURE / ARCHITECTURAL DIAGRAM .......................................................................................................... 4
5 SUMMARY OF MILESTONES & DELIVERABLES........................................................................................................................... 5
5.1 EXPECTED AWS COST BREAKDOWN BY SERVICES ............................................................................................................... 5
6 RESOURCES & COST ESTIMATES ............................................................................................................................................... 6
7 CUSTOMER SIGN OFF TEMPLATE .............................................................................................................................................. 6
8 APPENDIX A – TECHNICAL PROJECT PLAN FOR MIGRATION PROJECT ....................................................................................... 7

Page | 2
2 PROJECT OVERVIEW

2.1 EXECUTIVE SUMMARY

[Use this section of the document to provide a high-level overview of the project. Briefly describe the customer’s business
and technical objectives, including the business and technical drivers for moving to the AWS cloud. Briefly summarize the
partner’s professional services to be delivered to meet the customer’s objectives.]

Note: please complete the POC form within the ‘APN Fund Request and Claim Toolkit’ excel file.

2.2 PROJECT SPONSOR(S) / STAKEHOLDER(S) / PROJECT TEAM

[Identify and list the customer’s Executive Sponsor and Project Stakeholders, including Title and Description (describe
their role and responsibilities in the organization). The Executive Sponsor is the individual with overall accountability for
the project. The Sponsor is primarily concerned with ensuring that the project delivers the agreed business benefits.
Project stakeholders are entities that have an interest in a given project, and usually represent a business group or
organization]

Partner Executive Sponsor

Name Title Description Email / Contact Info

John Doe SVP Finance Head of Financial Services

Project Stakeholders

Name Title Stakeholder for Email / Contact Info

Ivan Doctorow Sr. Manager, QA IT – Testing / QA

Jane Smith Director, PMO Program Management Office
Dan Jacobs VP, IT Operations IT Operations – Networking

Partner Project Team

Name Title Role Email / Contact Info

Steve Jones Delivery Manager Project Manager

Philip McDaniels Sr. Solutions Architect Architect; Technical Lead

2.3 PROJECT SUCCESS CRITERIA

[Provide a bulleted list of items that are important to address for the success of the project. Describe the important
business and technical objectives of the project in a way that is quantitative and measurable, i.e., how success would be
defined and measured for this project.]

2.4 ASSUMPTIONS
[Provide a bulleted list of items that are known prerequisites, dependencies, constraints or assumptions to execute the
project. Record any assumptions that were made (as opposed to known facts) when conceiving the project. Note any
major external dependencies the project must rely upon for success, such as specific technologies, third-party vendors,

Page | 3
development resources, or other business relationships. Also note any business or technical constraints that exist, which
might impact cloud migration or adoption, such as an on-premise mainframe system or on-premise
integration/messaging bus.]

2.5 OUT OF SCOPE

[Provide a bulleted list of items that are discussed but considered out of scope for this project.]

3 SCOPE OF WORK - TECHNICAL PROJECT PLAN

[Provide a list of items and activities as scope of the work expected to be accomplished by the APN Partner. For
Migration projects, please reference Appendix A for additional guidance.]
Note: This section is required to be included should you choose to use another project plan template.

4 SOLUTION ARCHITECTURE / ARCHITECTURAL DIAGRAM

[Provide a description of the proposed high-level technical architecture, to address common architectural aspects such
as: network infrastructure; data/process flows; software services/components; integration/messaging/middleware;
security; deployment models; operations/support models. (As appropriate, based on the type of project).

Also provide architectural diagram(s) that illustrate the proposed solution architecture. As an APN Partner, you are
permitted by AWS to use AWS Icons to create architecture diagrams. For details, please visit
https://aws.amazon.com/architecture/icons/.]

Page | 4
5 SUMMARY OF MILESTONES & DELIVERABLES
[Provide project milestones with timeline and respective deliverables, corresponding to the items and activities described
in the Scope of Work / Technical Project Plan section.]
Note: This section is required to be included should you choose to use another project plan template.

Project Phase Est. Completion Date Deliverables

• item 1
Click to Select Date
• item 1
Click to Select Date
• item 1
Click to Select Date
• item 1
Click to Select Date

Click to Select Date • item 1

5.1 EXPECTED AWS COST BREAKDOWN BY SERVICES

[Include a link to the AWS monthly calculator pricing created specifically for this project. Pricing should include all AWS
Services like EC2, S3, EBS and others expected to be deployed based on the architecture listed above in this document]

Link:

Page | 5
6 RESOURCES & COST ESTIMATES
[List all billable and non-billable resources involved in the project] Note: This section is required to be included should you
choose to use another project plan template.

Partner Technical Team

1. Title - Name
2. Title - Name

Resource Rate (USD) / Hour

Solution Architects
Engineers
Other (Please specify)

Solution Other
Project Phase Engineers Total Hours
Architects (Please specify)

Total Hours
Total Cost

Cost Contribution distribution between Partner, Customer, AWS:

Party Contribution (USD) % Contribution of Total

Customer
Partner
AWS

7 CUSTOMER SIGN OFF TEMPLATE

Please fill out below information and send to customer upon project or defined milestone(s) completion. Once
customer acknowledges the cost contribution and project deliverables, please attach the customer email as a proof of
execution for fund claim from AWS. Missing information in Customer Sign Off may cause payment delay or rejection.

Party Contribution (USD) % Contribution of Total

Customer
Partner
AWS
Project Deliverables
(Estimated / Actual) Project Start Date
(Estimated / Actual) Project End Date
Expected Date of Production
Customer’s AWS Account ID for Production (If any)
Public reference if project successful? (Yes / No)
Case study potential if project successful? (Yes / No)

Page | 6
8 APPENDIX A – TECHNICAL PROJECT PLAN FOR MIGRATION PROJECT
The migration scope and deliverables below is for guidance and demonstration purposes. Actual project details may
include other work items not limited to the following areas.

I. PLANNING
(1) Discover, analyze, and prioritize application and data center resource portfolios for migration. Select and use
portfolio discovery tools to automate the discovery work. Work with the customer.

Deliverables:

(a) A document with discovered resources, dependencies, and usage data

(b) A prioritized list of applications and workloads for migration

(2) Design and deploy an initial AWS Landing Zone which is comprised of Account Structure, Network Structure,
Account Security Baseline, Logging (including CloudTrail) and Alerts, and User Access and Identity Management.

Deliverables:

(a) A document capturing the initial Landing Zone design

(b) Initial Landing Zone implementation

(3) Develop or refine a multi-year migration business case that encompasses current on-premise costs, new AWS
costs, and migration costs based on the discovered resource portfolio data.

Deliverable:

A multi-year Total Cost of Ownership (TCO) summary with the on-premise costs, new AWS costs, and migration
costs.

Note that Operating Model shall be established in this Planning phase. The Operating Model design and
implementation is described separately below.

II. DESIGN
For a given set of applications or type of workloads identified for migration from the Planning work above, complete
the following items:

(1) Determine migration method – Re-host, Re-platform, Re-factor, Re-purchase, Retain, or Retire
(2) With the customer, specify migration target requirements (RTO, RPO, security, reliability, scaling, performance,
monitoring, deployment automation, etc.)
(3) Based (1) and (2) and the Landing Zone defined in the Planning phase, design application architecture with
architectural diagrams; address the requirements using the AWS Well-Architected Framework covering security,
reliability, performance efficiency, cost optimization, and operations excellence.
(4) Evaluate and select migration tools
(5) Based on (1), (2), (3), and (4), develop integration, validation test, and cutover and rollback plans

Deliverables: Documentation for the design items (1) ~ (5); the tooling is ready for the migration work.

III. MIGRATION
(1) Install migration tools and agents where needed
(2) Develop or capture reusable templates (e.g., CloudFormation) for deployment automation
(3) Perform actual migration based on the Design above using the migration tools; conduct basic validation

Page | 7
 (4) Integrate migrated workloads (application servers, databases, data, or infrastructure services) with the AWS
environment and services; conduct validation based on the test plan from the Design work
(5) Perform cutover to the migrated services with the rollback plan from the Design work

Deliverables: Migrated applications and workloads validated and running in the production environment in AWS

IV. OPERATION
Establish and implement Operating Model. Review the Basic Operations Checklist. Establish operation best practices
including one or more of the following areas.

• Monitoring and logging

• Backup and Restore
• Change management process and tools
• Deployment automation
• Troubleshooting and escalation procedures.

Deliverables: Rollout of operation best practices accompanied with documentation and tools in one or more of the
above areas

Note that the Operating Model shall be determined during the Planning phase ahead of the Migration work.

V. OPTIMIZATION
Conduct post-migration optimization if it is under the scope of the migration project. The optimization should cover
one or more of the following areas.

• Cost optimization (e.g., using Reserved or Spot Instances)

• Application optimization (e.g., Service Oriented Architecture, Containerization, etc.)
• Process optimization (e.g., CI/CD)
• Operational optimization (e.g., infrastructure as code with deployment and upgrade automation)

Deliverables: Implementation and validation of one or more of the optimizations above

VI. PROJECT CLOSURE

Reach the project closure with the customer by completing the following work.

(1) Provide hands-on trainings about the AWS environment running migrated or deployed applications to the
customer
(2) Handover the design documents, implementation notes, test reports, and operation procedures to the customer
(3) Obtain letter from the customer accepting the applications and workloads that were migrated to or deployed in
AWS based on mutually agreed acceptance criteria

Deliverables: Trainings, documents, and customer’s acceptance letter

Page | 8