Project Initiation Best Practices Checklist

These project initiation best practices allow teams to identify risk areas early in the project lifecycle.

The following content can also be downloaded as a Microsoft Word document for sharing with teams and for offline completion: Project Initiation Best Practice Checklist.docx.

Project Information

Item	Importance	Status
Project lead has been identified	High
Technical lead has been identified	High
Product Owner has been identified	High
Schedule has been defined	Medium
Expected time commitment per stakeholder defined

Item	Importance	Status
Peak concurrent user load has been estimated	High
Peak process initiation rate has been estimated	High
Average process size, duration and retention in memory has been estimated	High
Expected process memory use has been estimated	High
Document storage has been estimated	Low
Database storage has been estimated	Low

Item	Importance	Status
Environments have been defined and will be available when needed	High
Production-use software has been procured	High
Production clone environments have been defined	Medium
Production physical architecture has been defined	High
Production network architecture has been defined	Medium
Mobile access from internal and/or public networks has been defined	High
Appian Health Check schedule has been defined for each environment	High

Item	Importance	Status
High level design has been documented	High
Up-to-date user interface usage (i.e. tempo, sites, mobile) is defined	High
Encourages user collaboration	Medium
Supports mobile use	Medium
Application/global naming prefix(s) have been defined	Medium
Business Roles have been identified and mapped to Appian Group structure
Groups and the appropriate interfaces have been defined (i.e. tempo, sites, mobile)

Item	Importance	Status
Key business record types have been identified	High
Source of data for key business record types have been identified	Medium
Expected number of records per record types have been defined	Medium
Security models for key business reports have been defined	Medium

Item	Importance	Status
Key business reports have been identified	High
Source of data for key business reports have been identified	Medium
Security models for key record types have been defined	Medium
Avoids using process analytics reports in favor of database entity-backed reporting	Medium

Item	Importance	Status
Datasources have been identified	Medium
Datasources are for exclusive Appian use	Medium
Datasource schema will be defined by development team	Low
Number of CDTs has been estimated	Medium
Total number of data elements has been estimated	Medium
Uses appropriate data model relationships for expected use cases	High
Expected levels of auditing for data elements identified

Item	Importance	Status
High level process models have been identified	High
Design calls for decomposition of process models into sub-processes	High
Process archival rules have been identified

Item	Importance	Status
Base product integrations have been defined	High
Custom integrations have been defined	High
Points of contact are defined for all external systems	Medium

Item	Importance	Status
Account creation, update, and deactivation has been defined	Medium
Group management has been defined	Medium
Authentication method has been defined	High
Allows mobile access	Medium
Allows Administrator/sysadmin access	Medium

Item	Importance	Status
Version control is defined	Low
Uses Configure Script	Medium
Appian deployment procedures have been defined (see the Application Deployment Guide)	Medium

Item	Importance	Status
All plugins are approved for Cloud deployment	Medium
Requires access to self-managed resources via VPN	Medium
Requires data migration between environments	Medium

Item	Importance	Status
Requires new custom plugins	Medium
Requires data migration	Medium
Requires critical security requirements	Medium
Must support users who speak different languages	Medium
Requires strict 508 compliance	Medium