DL Migration Project Decision Matrix

The Project Decision Matrix is a standard, repeatable process to determine if a new APHL Informatics initiative is a “project”, “O&M” effort, or other. If it is a project, then this determines if it needs to be tracked via PMO biweekly status reporting.

Note: to use this template, follow the process in PMO Process 006 - Project Decision Matrix. This process only relates to APHL Informatics efforts, not APHL Datapult.

Question	Yes/No	Weight	Value

Question	Yes/No	Weight	Value
Initiative Name: <name>
1. Is this initiative led by a PM with start and end date?	Yes	If YES, add 1 point	1
2. Does this initiative lead to new Informatics systems capabilities or modify existing Informatics systems to improve capacity, functions, or performance substantively [ON AIMS platform]?	No	If YES, add 1 point	0
3. Does this initiative have a "life-cycle" for new efforts (not yet in production) [ON AIMS platform]? Examples: New tools or functions: Analysis, Design, Build, Test, Move to Production Onboarding states: Plan, Connect, Validate, Production	No	If YES, add 1 point	0
4. Is this initiative a major release or enhancement for a new or existing product…[ON AIMS platform]? Focus is on pre-production/new efforts Major enhancements to existing projects/products	No	If YES, add 1 point	0
5. Is this a long-range initiative with a duration of more than 2 months?	Yes	If YES, add 1 point	1
6. Is this initiative high-risk, requiring close monitoring by APHL leadership and key interested parties?	Yes	If YES, add 1 point	1
7. Does this initiative have at least one major cross-project dependency with an existing project?	Yes	If YES, add 1 point	1
8. Does the outcome of this initiative impact at least one other existing project?	Yes	If YES, add 1 point	1
9. Does this initiative require the use of shared CoAg resources or services that are currently allotted to existing and in progress projects?	Yes	If YES, add 1 point	1
10. Is this initiative a part of the process of continuously monitoring, upgrading, and maintaining production applications or IT infrastructure? Examples: Production support of projects previously developed More ongoing support w/o end date Maintenance may include bug fixes are minor releases of a few new features	Yes	If NO, add 1 point	1
11. Is this initiative associated with maintaining and operating the production environment of an existing service?	Yes	If NO, add 1 point	1
Total			8/11