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. Iterative Build
The Iterative Build phase uses the plan to
develop the software or technology through iterations. At each iteration, the
team can use the knowledge they gained during previous iterations to make
modifications and add functions more efficiently.
Iterative Build
Activities
|
Activity
|
Accountable
Role
|
|---|---|
|
□ Complete story card design
|
UX Lead
|
|
Description
In conjunction with detailed
requirements, design and test the user interface for each story card; must be
completed 1 to 2 iterations prior to the scheduled build.
|
User Experience
DEtailed Hardware/Software Specification
|
|
Sub-Activities
□ Complete user analysis
□ Design solution for each story
card
□ Create wireframes
□ Create prototypes
□ Conduct usability tests
□ Document design
specifications
□ Update and store inventory in the
project’s SharePoint
site
|
Contributing Roles
UX Lead, BA Lead, Project Sponsor,
Project Manager
BA Lead, UX Lead, System Test
Lead
UX Lead, BA Lead, Tech Lead,
Project Sponsor
UX Lead, BA Lead, Tech Lead
UX Lead, BA Lead
UX Lead
BA Lead, Project
Manager
|
|
□ Begin Transition planning
|
Project Manager
|
3. 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
|
4. 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.
|
Detailed Hardware/Software Inventory
|