Project Name

Date Updated

Document Completeness

Item not available (N) 0

Items available (Y) 0
Completeness 0%
Phase Milestone
Preparation Validation

Budget

Planning Handover

Risk Assessment

Communication
 Kick Off

Development Development Team trained /

Preparation Staffing

Content Architecture

System Architecture

Application Architecture
(aka Solution Design) Sign Off

System Integration

Experience Design

Test Concept
 Test Concept

Support Setup

Development Development Environment

Test System

Production System

Integration

Documentation

Feature Freeze
Performance & Testing (End-) user Acceptance Test

Performance and Load-Test

Rollout Admins trained

Users trained

Pen Test

Go-Live Security
Go-Live

Fallback

Support
Operations Permissions

Monitoring & Maintenance

Recovery Plan
AEM Project Checklist

Required information →
Input
Customer Roadmap
Scope Document
ROI expectations
Initial Experience Designs Requirements
Business Requirements Documentation
Technical Requirement Documentation
Scope Document
High Level Solution Design
Hardware Estimates
Project efforts
Requirement Documentation
Customer overall Project Roadmap
Project Scope Definition
ROI expectations
Initial Experience Designs
Business and Technical Requirements Documentation
High Level Solution Design
Architecture Draft
Hardware Estimates
Historical Performance KPIs, Expectations
Relevant contract terms
Identify critical key solutions/functionalities
Customer roadmap vs project timeline
Technical and Business Risk Assesment
Proof of concept, design and implemenation
Test and verify POC against Requirement Documentation
Definition of Stakeholders internal and external
Issue Tracking System and processes from involved parties
Status Report format definition
Reporting Schedule
Customer Roadmap
Project Scope Document
ROI expectations
Initial Experience Designs
Requirements Documentation
High Level Solution Design
Architecture Draft
Hardware Estimates
Performance KPIs
Timeline and Milestones
Project Ogranization and Communication
AEM technical trainings
AEM Certification Exam

Initial Experience Designs

Requirements Documentation
High Level Solution Design
Architecture Draft
KPIs Definition
Requirements Documentation

High Level Solution Design

Architecture Draft
Hardware Estimates
KPIs Definition
Sign Off with Lead Dev Checklist
Performance and scalability concept
Requirements Documentation

High Level Solution Design

Architecture Draft

Hardware Estimates

KPIs Document

Component and template concept

Special functionality concept

3rd party system for integration
SLAs for 3rd party systems
Initial Experience Designs
Requirements Documentation
Initial Experience Designs
Requirements Documentation
High Level Solution Design

Transform Performance KPIs into customized Test Suite

Use cases / customer stories

Setup Support processes (eg. Partners/Customer/Adobe)
List of users require access to Adobe Support Portal
Definition of escalation process
Request for setting up project section in Adobe Support portal
List of standard development tools to be used in the project
High Level Solution Design
Architecture Draft
High Level Solution Design
Architecture Draft
System Architecture Definition
Run Test Suite on final Production setup

Disk performance test

Integration Testing, automated test setup

Role Definition, which developer is executing IT and/or Unit Tests
Document customizations which affects upgrades, hotfixes
Document operational tasks
Release Notes
Requirement Documentation
Release running on prod

Acceptance test

Test Suite passed? Performance KPIs

Use Cases Definitions
Real content for testing
Full breadth and depth QE test suite, covering features,
components, bug fix verifications and regressions from previous
drops
Test Suite

AEM Admin Training

Standard author training
If required: specific training material for application and/or site
Security checklist [1] & policy
System Architecture
Security Checklist [1]
List of security issues
Penetration Test
Fallback system
Fallback procedure tested
Golive Schedule

Permission Concept (list of roles, group)

Disk space monitoring

CPU Monitoring
Disk I/O Monitoring
Network Bandwith Monitoring
DataStore Garbage Collection enabled and tested
Respository Optimization
External System Monitoring
Request monitoring
Backup of Author & Publish Instances
Restore tested and documented
Cluster: steps for cloning was tested and is documented
 PASSED
expected Output
Output Y/N
High Level Solution Design
Architecture Draft
Hardware Estimates
Performance KPIs
Project efforts

Validated budget plan

Performance KPI Document

Project management understands scope of project and expectations

Technical risk factors known

Adjustment of the scope/features required?
Results and business decision proposal
Technical risk factors verified

Issue tracking process is set up and integrated

Project status reports within a defined schedule
Project team understands project and expectations
Hardware will be available to fullfil requirements
Agreement on KPIs, defined as goals for project
Project team is aware of the commmunication plan

Staff Trained
75 % Certified AEM Component Dev
min. 1 AEM Lead Developer Certified
min. 1 AEM Architect Certified
Content Architecture Definition
Feasability confirmation on KPIs

System Architecture Definition

Run baseline tests on OOTB AEM, using preferred automation testing
suite, confirm deviation to plan and adjust
How can KPI for performance & scalability be met?

Application Architecture Definition

Run baseline tests on OOTB AEM, using preferred automation testing
suite, confirm deviation to plan and adjust
list of components and templates to be developed, dialog definition,
most important properties (name and type) of these
implementation concept for specific large parts of AEM in case they are
used

3rd party integration concept

SLAs defined and in sync with the plattform
Experience Design

Test concept documentation

Test Plan
Test Suite, covering customer use cases
User stories → dissected into click paths → executable test cases
Formalized Acceptance Test

Staff understand the support processes from Adobe

Staff have sufficient permission in Support portals
Staff understand Escalation processes
Project setup in Adobe Support Portal
Development environment set up
Devolpment system ready

Test System ready

Production System ready

Baseline Performance verfied with Test Suite

Disk performance (DiskBenchmark) result with a valid pattern

Automated deployment

Operations Manual

Feature completeness
Functionality of the application are accepted by stakeholders
Formalized Checklist for customer handover, ideally automated and run
on a nightly basis on snapshot; results sent to project manager and
development team
Test suite results available
Validated Test Script against realistic and expected load
Test suite adapted to real content and result comparison to OOTB test
run
Tests run automated ormanually on a regular basis
70% of the requests for pages respond in less than 100ms
No pages respond slower than 1 second
Acceptance from Business Stakholders
Trained system administrators
Trained authors/users
End Users trained
List and assesmment of Security related issues

Default security enabled

Security issues fixed
Penetration Test passed
System available to switch back in case of golive failure
Inform Adobe Support about the Golive Schedule

Permissions meet security guidelines

System Monitoring enabled

Threshold and intervention enabled
External system Monitoring enabled

Recovery plan and procedures documented

Notes
KPIs:
- Number of parallel authors/users (Concurrency)
- Response times
- Number of assets/day (avg and peak)
- Number of page modifications/day (avg/peak)

multiple contracts possible (license, project as T&M or fixed budget, M&A, etc)

- Project management has clear understanding of throughput, # of visitors including peak times (events iDay, Superbowl et
- Page render times millisecond granularity, including 3rd party integrations, asset delivery and caching strategy

Identification of any solution elements that can be a potential risk (eg. MSM, Commerce integration, etc.). The result will be
business whether the full requirements can be implemented. In case the solution concept is fraught with risk the business r
to deal with the requirements.

- Separate systems with cross-posting need to be avoided

- All involved parties have approperiate access and are able to follow the process
REFERENCES:
http://docs.adobe.com/docs/en/aem/6-2/manage/managing-projects/project-kick-off.html
http://docs.adobe.com/docs/en/aem/6-2/manage/managing-projects/concept-planning.html#Setting%20Target%20Metrics

REFERENCES:
- https://training.adobe.com/training/courses.html#solution=adobeExperienceManager
- http://www.adobemarketplace.com/Learn-Adobe-Experience-Manager-s/1912.htm
- http://training.adobe.com/certification/exams.html#p=1&solution=adobeExperienceManager&certificationType=certificatio

basic structures (content, assets, campaigns, ...)

multi site and multi language structures (MSM, Translation, etc.)
supportive content (tags, ...)
cached vs uncached content

- required environments (dev, stage, prod, other?)

- servers and processes for each environment
- maintenance activities (Datastore GC, TarPM Opt, ...)
- matching KPIs from Sales Handover

dispatcher caching, offloading, share-nothing publishs, author cluster

Very important: performance for client-side (JS minifify, concat, css sprites, total number of http requests, etc)

- basic code structure for project

- code artifacts (bundles, packages, ...)
- templates/components break-down and their relationships
- required customizations (high level, specific overlays later)
- design of general workflows that the solution must support (content creation, approval, publishing, transformations, impor

leverage component inheritence

"large parts": eg. MSM, translation workflows, ecommerce

Technical concept for how the 3rd party system shall be integrated (offline/online, client-side/browser-side)
Also requires fail-over handling when 3rd party system is down

- this should be as complete as possible, as changes later will be costly

- includes functional, performance and regression tests, milestone definition

- to be automated (Selenium, hobbes (AEM 6.2 Developer mode))
- includes functional, performance and regression tests, milestone definition
- to be automated (Selenium, hobbes (AEM 6.2 Developer mode))

REFERENCE:
- http://helpx.adobe.com/marketing-cloud/contact-support.html
- Note: Only trained developers get read/write access on Adobe's Support Portal
- Typical: Issues Tracking, IDEs like Eclipse, Maven, Jenkin for CI, GIT/SVN, Archiva/Nexus, ...

- for nightly builds

- for Sprint releases

- preferred: sizing similar to prod for performance tests

REFERENCE:
- http://docs.adobe.com/docs/en/aem/6-2/develop/test/tough-day.html

Disk performance benchmarks results required; especially when Network filesystem will be used.

- Automated process to move application from dev to test to prod (and content the other direction)
- Definition of which level developer should test (i.e. IT, Unit)

- info about changes that may affect installed systems and content
- info about customizations and overlays that may affect upgrades, hotfixes, ...
- info about operations related tasks (configuration, ...)

this is the final check for functional/workflow issues (should be verified with every sprint as mentioned above)

REFERENCES:
- http://docs.adobe.com/docs/en/aem/6-2/deploy/configuring/performance.html
- http://docs.adobe.com/docs/en/aem/6-2/develop/test/planning.html

- functional tests
- as soon as available also performance tests against test system (same scale as prod)

- For Basic Guidelines on response time see:

- http://docs.adobe.com/docs/en/aem/6-2/deploy/configuring/performance.html#Basic%20Performance%20Guidelines

[1] https://docs.adobe.com/docs/en/aem/6-2/administer/security/security-checklist.html

REFERENCE:
- https://docs.adobe.com/docs/en/aem/6-2/administer/security/security-checklist.html
REFERENCE:
- https://docs.adobe.com/docs/en/aem/6-2/administer/security/security-checklist.html

List of roles, groups and read/write access for each of them, also priviledges like "replicate" defined.
For users with minimal privilieges, workflows are defined.
No editor should have admin rights or be part of the adminsitrators group.
REFERENCE:
- http://docs.adobe.com/docs/en/aem/6-2/deploy/configuring/monitoring-and-maintaining.html

In emergency situation a full rollback/restore must be available to secure production use of AEM