PROJECT CHECKLIST – AUDIT FORM
Partner Name – Project Name
To: Partner POC
Project: Initial Implementation
Date: 02/26/2013
Overall Partner Status
Completed Developer Training
Current Project
Certification
Pending
On Track
Documentation
required
Prepared by: CrownPeak
crownpeak@crownpeak.com
p. 310-841-5920 x200
INTRODUCTION
This document includes 3 checklists to validate a project. These checklist, and the related deliverables,
should be completed by the project team and audited by CrownPeak for certification
1. Preparation for Development
a.
Deliverable: Project Information Document (or CMS requirements document)
2. Preparation for Delivery
a.
Deliverables: CMS ready for UAT, UAT Agenda (or user documentation)
3. Preparation for Launch
a.
Deliverables: CMS ready for launch, launch plan, Welcome to Support document, Support
Transition document
Partner Name
February 6, 2016 / Page 1 of 12
Project Name
1. PREPARATION FOR DEVELOPMENT CHECKLIST AND AUDIT
This should be completed before starting CrownPeak development.
Partner Instructions
Complete the following steps to make sure all requirements are defined for the CrownPeak implementation

Confirm front end code that will be the basis for content published has been developed based on best
practices
-
http://connect.crownpeak.com/documents/best-
practices/htmldeliveryrequirementsandrecommendationspdf

Confirmed that CrownPeak trained developers will be resources on the project

Collect and review site map, wireframes, and/or functional specification to understand the site that
CrownPeak will be configured to support

Complete Project Information Document (PID) and confirm with checklist below
CrownPeak Instructions

Audit the PID with checklist below before development begins. Rate each task:
Partner Name
o
Critical (Fix it now)
o
Warning (Fix in the next project)
o
On Track (Great Job!)
February 6, 2016 / Page 2 of 12
Project Name
PID CHECKLIST & AUDIT FORM
Task
Partner
CrownPeak Audit
Checklist
Complete? Follows Best Notes
Practices?
HTML developed according to standards
Y/N
On Track
Site map and functionality delivered
Y/N
On Track
Define project scope
Y/N
On Track
Define Sites
Y/N
On Track
Y/N
On Track
Define hosting plan
Y/N
On Track
Define templates
Y/N
On Track
Define models
Y/N
On Track
Define content plan
Y/N
On Track
Define application requirements
Y/N
On Track
Y/N
On Track
Identify and plan 3rd Party integrations
Y/N
On Track
Define users
Y/N
On Track
Define groups
Y/N
On Track
Define workflows
Y/N
On Track
Define Project team and responsibilities
Y/N
On Track
Completed DNS planning meeting with all
stakeholders including CrownPeak IT and
Customer IT
Identify and plan CrownPeak module
integrations
Partner Name
February 6, 2016 / Page 3 of 12
Project Name
CrownPeak-trained developers participated in
PID creation
AUDIT SUMMARY
Y/N
On Track
On Track
NEXT STEPS

Partner: Address audit issues - Critical (Fix it now), Warning (Fix in the next project), On Track (Great
Job!)

CrownPeak: Confirm critical items have been fixed before moving on to development
Partner Name
February 6, 2016 / Page 4 of 12
Project Name
2. PREPARATION FOR UAT CHECKLIST AND AUDIT
This should be completed before delivering the CrownPeak implementation to the customer.
Partner Instructions

In order to validate a CrownPeak implementation, test it against the checklist below.

Create UAT Agenda
o
Create a UAT agenda that provides an overview of CrownPeak and describes the functionality
of every template and that will serve as a guide for content authors.
CrownPeak Instructions

Audit implementation with checklist below and review UAT agenda. Rate each task:
o
Critical (Fix it now)
o
Warning (Fix in the next project)
o
On Track (Great Job!)
IMPLEMENTATION CHECKLIST & AUDIT FORM
Task
Partner
Checklist
Complete?
CrownPeak Audit
Follows Best
Practices?
PID validation: Implementation matches scope?
Y/N
On Track
PID validation: All sites delivered?
Y/N
On Track
PID validation: Content plan in place?
Y/N
On Track
PID Validation: Application requirements complete?
Y/N
On Track
Y/N
On Track
Y/N
On Track
PID validation: CrownPeak module integrations
complete?
PID validation: 3rd Party integrations complete?
Partner Name
February 6, 2016 / Page 5 of 12
Notes
Project Name
PID validation: All users added?
Y/N
On Track
PID validation: All groups configured?
Y/N
On Track
PID validation: All workflows implemented?
Y/N
On Track
Y/N
On Track
Y/N
On Track
Hosting plan is on track
Y/N
On Track
UAT Agenda completed
Y/N
On Track
Implementation confirmed in weekly technical
meetings
CrownPeak-trained developers implemented or
validated implementation
AUDIT SUMMARY
Partner Name
On Track
February 6, 2016 / Page 6 of 12
Project Name
NEXT STEPS

Partner: Address audit issues - Critical (Fix it now), Warning (Fix in the next project), On Track (Great
Job!)

CrownPeak: Confirm critical items have been fixed before delivering instance for UAT

Partner: Deliver UAT training to customer.
o
This training should be delivered to the users who will validate the implementation for end
users and content creators. During UAT the customer is expected to:

Validate the PID by creating and editing content, using the workflow and publishing
as every type of user for every type of page

Review published site on staging server to confirm it works as delivered and
integrations are functional
o
During UAT, the implementation team is expected to rapidly address issues, bugs, and feature
requests so customer can continue to test
o
Partner Name
UAT is normally limited to about 2 weeks.
February 6, 2016 / Page 7 of 12
Project Name
3. PREPARATION FOR LAUNCH CHECKLIST AND AUDIT
This should be completed before site launch.
Partner Instructions

Prepare your team and CrownPeak support for launch using the checklist below.

Complete Support transition document and review with support team

Purpose of this process is
o
Assuring smooth and risk-free Go- live process
o
Adherence to Best practices
o
Ability to audit the site to address and manage UAT critical issues
o
Easy transition to support
CrownPeak Instructions

Complete launch audit and review support transition document prior to launch date. Rate each task:
Partner Name
o
Critical (Fix it now)
o
Warning (Fix in the next project)
o
On Track (Great Job!)
February 6, 2016 / Page 8 of 12
Project Name
LAUNCH CHECKLIST & AUDIT FORM
Task
Partner
Checklist
Complete?
All critical reported UAT issues completed.
CrownPeak Audit
Follows Best
Practices?
Y/N
On Track
Y/N
On Track
Y/N
On Track
Y/N
On Track
Y/N
On Track
Y/N
On Track
Notes
A plan to fix any outstanding UAT issues has been
created, We should have a document/artifact
detailing the plan, and capturing the client’s
signoff
A “go live” meeting with the client has been held.

Review the differences between sending
files to LIVE and actually being live (DNS
switchover).
Assets published to Live will be available for
review using temporary Live URLs. The site
will become available for public on the real
live URL only after the DNS cutover
Go Live Plan
Create “go live” team and plan for the launch
date. The team should include CrownPeak PM and
CrownPeak Tech Lead.
Create Rollback plan. Usually it is just one task "
Make the old IPs active in DNS", but may require
more steps based on the implementation.
The transition to support meeting has been held
before going Live

Review implementation with CrownPeak
support, & CrownPeak project support
team, invite
PS, Support, IT Ops, and
Partners to the meeting if needed.

Capture outcome of meeting in a Jira
ticket with todo’s and action items or the
Partner Name
February 6, 2016 / Page 9 of 12
Project Name
hand-over document
All pages should be published and tested in LIVE
twice as soon as possible to repair possible broken
cross-page links.
Y/N
On Track
Y/N
On Track
Y/N
On Track
Y/N
On Track
Y/N
On Track
Y/N
On Track
Run the Link checker report (for example
http://home.snafu.de/tilman/xenulink.html)
Ensure “Go Live” team is ready at launch in case
any issues arises.

Use project support team & CrownPeak
Support as backup.
Ensure the Client prepared high-level test plan in
order to run on the new Live site after the DNS
cutover
Provide the Client with new hosting IPs

Work with CrownPeak IT Operations to
provide load balancer IP, or CNAME.

CDN information if needed.
Request site monitoring, Jira ticket to IT:
Hi,
Please add <domain name> to the 24x7
site monitor
Whitelist CP

Include any support specific
documentation that prevents CP access
to production site . Information like this
needs to be included in a support
document, so CrownPeak support is
aware of special server constraints or
configurations (like web.config)
Partner Name
February 6, 2016 / Page 10 of 12
Project Name
Remind customers’ IT to lower the TTL prior to go
live, so content will be available when DNS is
made live (usually 5 to 15 minutes)
Review
/
Validate
CrownPeak
Search
configuration
Y/N
On Track
Y/N
On Track
Y/N
On Track
Y/N
On Track
Y/N
On Track
Review / Validate WCO Configuration, some
snippets may require redirect URLs update from
Stage to Live
DNS cutover.

Work with CrownPeak support,
CrownPeak project support team, &
CrownPeak IT Operations
Ensure there is a Client's network resource
assigned to the DNS cutover task
Welcome to Support document (for customer)
and
Support
Transition
document
(for
CrownPeak Support) are complete
AUDIT SUMMARY
Partner Name
On Track
February 6, 2016 / Page 11 of 12
Project Name
NEXT STEPS

Partner: Address audit issues - Critical (Fix it now), Warning (Fix in the next project), On Track (Great
Job!)

CrownPeak: Confirm critical items have been fixed before launch

Partner: Launch the Site!
Go-Live steps:

Remind customers’ IT to lower the TTL prior to go live, so content will be available when DNS is
made live

For publishing content for the initial go-live, the process will be easy. Typically the site content will
be published in its entirety to the "live/production" site, before DNS is cutover. This way, the site
can be validated fully by the customer prior to making it "public".
Making it public would be done
by cutting over DNS, which would be handled by the customer’s IT department. Here are some
basic steps for launch

Route from STAGE to LIVE all the contents of the /Site/_Assets/ folder. (We need
to select only the assets that are currently on STAGE to be routed).

Start routing a few folders and subfolders from (STAGE to LIVE). We need to
route them in different batches to speed up publishing (by doing "batches", we
are creating multiple publishing threads).

After all the folders have been sent, manually publish the assets (branches) that
are on the root folder

Review that the site is getting published correctly

Republish folders/files if necessary.
It is best to use the Route option in the CrownPeak to promote content live. This allows users (with the
correct permission) to select multiple files and move them all to the Live state in a single action.
CrownPeak recommends publishing live begin at least 5 business days before DNS switch over.
Also to avoid broken links CrownPeak recommends re-deploying the site one more time after the first
publishing to Live.
Partner Name
February 6, 2016 / Page 12 of 12
Project Name