1. Plan
The Plan phase moves a project from an approved, prioritized High-Level Analysis to the point where it is ready to begin analyzing and defining requirements for the solution.
Execute Entry Criteria
Requirement
|
Accountable
Role
|
---|---|
□ Approved, Six Questions
|
Idea Owner
|
Plan
Activities
Activity
|
Accountable
Role
|
---|---|
□ Request Clarity project number
|
IT Delivery Manager
|
Description
The delivery manager requests the
project to be setup in Clarity. The Clarity Team creates a project number in
Clarity.
|
Templates
Clarity Project Request
Form
|
□ Assign a Project Manager
|
IT Delivery Manager
|
Description
The delivery manager works with the
resource managers to assign a Project Manager to the
project.
|
2. Analysis
The Analysis phase defines the requirements of
the system and states in a clear, precise fashion the functions of the
system.
Analysis
Activities
Activity
|
Accountable
Role
|
---|---|
□ Elicit, analyze, and validate
detailed requirements
|
BA Lead
|
Description
Based on the high-level business
requirements, created detailed functional and non-functional requirements for
the solution.
|
Non functional Requirements
Requirements Packet
Business Data Requirements
Service Level Agreements
|
Sub-Activities
□ Elicit and define business
requirements (functional/non-functional)
□ Document business requirements
(functional/non-functional)
□ Evaluate information security
needs
□ Review and approve
requirements
□ Define Business Data Requirements
□ Ensure functional/non-functional
requirements are
testable
|
Contributing Roles
BA Lead, Stakeholders
BA Lead, Tech Lead, Project
Sponsor, UX Lead
Information Security Lead, Tech
Lead, BA Lead
Project Manager, Solution Architect
Lead, Data Architect Lead, Operational Lead *NEW
BA Lead, Data Architect Lead
System Test Lead, Performance Test
Lead, Operational Lead *NEW
|
3. Design
The primary objective of the Design phase is
to create a design that satisfies the agreed application requirements. In the
Design phase, the Systems Development Life Cycle (SDLC) process continues to
move from the “what” questions of the analysis phase to the “how” questions.
Design Activities
Activity
|
Accountable
Role
|
---|---|
□ Complete user interface design
|
UX Lead
|
Description
Based on the user analysis, design
and test the user interface of the
application.
|
User Experience Prototype/Wireframe
|
Sub-Activities
□ Create wireframes
□ Create prototypes
□ Conduct usability tests
□ Document design
specifications
|
Contributing
Roles
UX Lead, BA Lead, Tech Lead, Project Sponsor
UX Lead, BA Lead, Tech Lead
UX Lead, BA Lead
UX
Lead
|
□ Design solution
|
Tech Lead
|
Description
Use the detailed requirements to
investigate the best solution and create a technical design. The design should
be directly traceable to the detailed requirements.
|
Templates
Business Solution Design
Enterprise Architecture
Technical Design Document
|
4. Build
During the Build phase, developers execute the
plans laid out in the Design phase. The developers create the database, generate
code for the data flow process, and create the user interface. During
construction, unit and integration tests are executed, test scripts are created,
and test environments and data are prepared.
Build
Activities
Activity
|
Accountable
Role
|
---|---|
□ Begin Transition planning
|
Project Manager
|
Description
Begin creating the necessary plans
to transition the finished product to the
customers.
|
Templates
Organizational Change Management Plan
Training Plan
Implementation Plan
Documentation Plan
Support Transition Plan
Detailed Hardware/Software Inventory
|
Sub-Activities
□ Begin creating Organizational Change Management
Plan
□ Begin creating Training
Plan
□ Begin creating Production Validation Plan
□ Begin creating Back Out Plan
□ Begin creating Support Transition Plan
□ Complete Documentation
Plan
|
Contributing
Roles
OCM Lead, Project Manager, Project Sponsor
BA Lead, Project Manager, Project
Sponsor
Change Owner, Project Manager, Release Manager, BA
Lead
Release Manager, Project Manager, Tech Lead
Operational Lead, Project Manager
Technical Writer, Team
Leads
|
5. Test & Production Readiness
The Test phase takes a working software or technology and
tests it for functionality, system, performance, and user acceptance to ensure
the deliverable meets quality standards.
Test Activities
Activity
|
Accountable
Role
|
---|---|
□ Test software or technology
solution
|
System Test Lead, Performance Test Lead
|
Description
Test the software and technology,
including system, performance, and user acceptance testing, to ensure the
software or technology satisfies business goals and objectives.
|
Service Level Agreement
|
Sub-Activities
□ Move and configure code through
environments
□ Complete system testing
□ Complete performance testing
(pass PEGT)
□ Verify
authentication/authorization models
□ (If applicable) Complete security
assessment test
□ (If applicable) Validate
monitoring and detection capabilities
□ Complete user acceptance
testing
□ Review and approve user
acceptance test results
□ Validate SLAs
□ Review and approve
SLAs
|
Contributing Roles
Software Configuration Manager,
Developers
System Test Lead
Performance Test Lead, Performance
& Capacity
System Test Lead, Info Security
Lead
System Test Lead, Info Security
Lead
Info Security Lead
System Test Lead, BA Lead
System Test Lead, BA Lead, OCM
Lead
Performance Test Lead, Performance
& Capacity
Project Manager, Project Sponsor,
Solution Architect Lead, Tech Lead, Operational Lead, BA Lead, System Test
Lead
|
6. Transition
The Transition phase includes the activities necessary to
deliver working software or technology as an enabler to the customer. The
project leadership team is accountable for delivering software or technology
that meets the business case’s requirements and success measures. Documentation
for the closure decision is minimal and covers only the requirements to complete
the transition.
Transition
Activities
Activity
|
Accountable
Role
|
---|---|
□ Complete training and
communications
|
Project Manager
|
Description
Conduct training and send internal
and external communications to prepare the customers for the new software or
technology.
|
|
Sub-Activities
□ Execute Organizational Change
Management Plan
□ Execute Communication Plan
□ Review
authentication/authorization models
□ Review software/technology with
production support staff
□ Execute Training
Plan
|
Contributing Roles
OCM Lead
OCM Lead, Project Manager
BA Lead, Info Security Lead,
Project Sponsor
BA Lead, Project Manager
BA Lead, Project
Manager
|
□ Deploy software or technology
|
Release Manager
|
Description
Move the software or technology
into production for customer to begin
using.
|