The questions below are undergoing review during Summer 2011 and are subject to change.
Phase Description
The Planning Phase begins when the project has been formally approved and funded, and the Project Charter is approved. This Phase requires study and analysis culminating in the full Project Management Plan and that may lead to system development activities.
In the planning phase, sufficient requirements detail is required to support the development of the project’s Project Management Plan and permit outside validation of this deliverable.
Stage Gate Review Purpose
The Project Baseline Review (PBR) is a formal inspection of the entire project and performance measurement baseline initially developed for the IT project. The PBR is conducted to obtain management approval that the scope, cost and schedule that have been established for the project are adequately documented and that the project management strategy is appropriate for moving the project forward in the life cycle.
Architecture Review Purpose
Conclude that compliance with the NIH Enterprise Architecture has been maintained.
EA Reviewer Domain Acronyms
| Acronym |
Reviewer Domain |
|---|
| CA |
Chief Architect |
|---|
| BA |
Business Architecture |
|---|
| AA |
Application Architecture |
|---|
| IA |
Information Architecture |
|---|
| SOA |
Service-Oriented Architecture / Integration Architecture |
|---|
| TA |
Technology Architecture |
|---|
| All |
All domains |
|---|
Planning Phase Questions
| No. |
Question |
Domain |
Response
(Y, N, NA) |
Comments |
|---|
| 1 |
Has compliance with the NIH Enterprise Architecture been maintained through the planning phase or an exception request submitted and approved? |
All |
|
|
|---|
| 2 |
Does the Work Breakdown Structure (WBS) (or scope definition) reflect evidence of reuse of services†, either as a service provider or a service consumer, if applicable? |
SOA |
|
|
|---|
| 3 |
Does the budget reflect evidence of reuse of services†, either as a service provider or a service consumer, if applicable? |
SOA |
|
|
|---|
| 4 |
Does the WBS and/or schedule include the Service Analysis Assessment, if applicable, no later than the Requirements Phase or within the first few development iterations for an iterative project? |
SOA |
|
|
|---|
| 5 |
Has the project considered technical risks, including probability, impact, mitigation strategies / contingency plans and are the technical risks mapped to architectural components? |
AA, TA, SOA |
|
|
|---|
| 6 |
Does the Acquisition Plan and/or acquisition deliverables reflect language that encourages or specifies reuse for any planned IT service contracts? |
AA, TA, SOA |
|
|
|---|
| 7 |
Does the Acquisition Plan and/or acquisition deliverables incorporate requirements for alignment with the NIH Enterprise Architecture, published NIH standards, and Federal standards and guidelines? |
TA |
|
|
|---|
| 8 |
Does the Project Plan reflect appropriate, architecturally significant deliverables, including the to-be business process model, the final conceptual and logical data models, requirements, Service Analysis Assessment, and the solution architecture (unless waived in the Project Process Agreement)? |
All |
|
|
|---|