EHB_Sample Enterprise Project Life Cycle.pdf

SAMPLE ENTERPRISE PROJECT LIFE CYCLE (EPLC) DELIVERABLES

Deliverable Ownership Approach Date

Initiation Phase

Project Charter Project Lead, Contractor

The project lead will prepare the project charter in consultation with the contractor and the business owners. It will describe the business need, the solution to be produced by the project, and the project objectives.

Before the task is exercised

Project Capability Requirements (PCR)

Project Lead, Contractor

The project lead will prepare the project capability requirements document to the high level system features that need to be implemented using the system.

Before the task is exercised

Planning Phase

Project Process Agreement (PPA)

Project Lead The project lead will develop a tailored process document to define the EPLC requirements/reviews for the project.

Within 15 days after task is exercised

Project Management Plan (PMP)

Project Lead, Contractor

The project lead and the contractor will prepare the PMP after discussions with appropriate stakeholders. The plan will also address the scope, budget and schedule.

Within 45 days after task is exercised

Project Work Breakdown Structure (WBS)/Schedule

Contractor The project lead will develop a contract/project level WBS using Microsoft project software.

Within 45 days after task is exercised

Release WBS/Schedule

Contractor The project lead will develop a schedule and detailed list of tasks for each of the major releases.

Based upon release schedule

Project Budget Project Lead, Contractor

The contractor will develop a detailed budget prior to the commitment of resources for any development activities.

Within 30 days after task is exercised

Schedule Activity List

Contractor The project lead will develop a detailed list of activities in consultation with the stakeholders.

Once a month

Resource Requirements Log

Contractor

The project lead will develop a detailed software and hardware resource requirements as part of the infrastructure plan.

Based upon project plan

Risk Management Log

Project Lead, Contractor

The project lead and contractor will log all the major project risks in the risk log/register and communicate it to the stakeholders

Monthly (as well as when new risks are identified)

Training Plan Project Lead, Contractor

A training plan will be developed which would provide details, including the training approach, training courses offered, duration of each course, intended audience(s).

Based upon project plan

Requirements Phase

Business Process Definition (BPD)

Contractor

Based upon discussions with the business owners, this document will capture the appropriate business processes. This information will be used to drive additional requirements elaboration activities such as the creation of screen mockups.

Based upon project plan

Business System Requirements (BSR) Document

Contractor A requirements document reflecting the high level capabilities and attributes of the desired solution will be created.

Based upon project plan

Release-Level Requirements /RTM

Contractor

This document will provide of the traceability of project level and release level requirements to the functionality contained within a specific release.

Based upon project plan

Logical Data Model Contractor

The logical data model provides a way to represent the business processes (and depicts the relationship between them).

This document will be used to further elaborate the system requirements.

Based upon project plan

Design Phase

Technical Design Document (TDD)

Contractor This document will explain the system design and architecture.

Based upon project plan

Physical Data Model Contractor

The Physical Data Model will take the logical data model information and create the physical data model structures. This will be developed in compliance with all appropriate EHBs naming conventions and standards.

Based upon project plan

Data Dictionary Contractor This document would explain the detailed definitions for all tables and columns.

Based upon project plan

Development Phase

Test Plan Contractor

The test plan would define the overall plan for performing the QA testing activities for the project. It would contain the proposed testing approach, types of testing that will performed, and details about the testing tools that will be used..

Based upon project plan

Test Scripts/Cases Contractor

Describes the detailed test scripts and test cases that will be used to validate that the system functions as expected.

The contractor will work with the business owners to ensure that the test cases developed exercise all of the business areas/functions of the system.

Based upon project plan

Test Phase

User Acceptance Test Cases

Contractor Detailed scripts that describe the functionality supported in the system will be available on the day of the UAT.

On the day of

UAT

Test Summary Report

Contractor

A detailed report will be provided showing the results of the testing efforts and will be used by the contractor and HAB to determine if the system is ready to go into production.

Based upon project plan

Testing Defects Resolution Report

Contractor

An export of the issues from the issue tracker will be provided so the stakeholders can get the insight into the issues found during contractor’s internal testing and their latest status.

Based upon project plan

Implementation/ Deployment Plan

Contractor

The implementation plan will provide details about how the system will be installed and made operational in the production environment for each of the major releases.

Based upon project plan

Implementation Phase

Training Materials Contractor

Based upon the training plan, a variety of training materials will be provided to ensure that users will be able to effectively use the system.

Based upon project plan

User Guides Contractor Based upon the agreed to upon requirements, user guides and other reference material will be developed.

Based upon project plan

Additional Help Materials

Contractor

System help using EHBs Wiki will be integrated within the module, allowing appropriate reviews and feedback from the stakeholders.

Two weeks after the release

Release Notes Contractor

Detailed release notes for this release will be provided; functional, technical, data and document changes will be tracked along with all dependencies.

Within two days of release

Pre-Deployment Site Readiness Results

Contractor

A report containing the results of the pre-deployment site readiness testing to verify that the site is ready for production implementation will be provided.

Based upon project plan

Operations & Maintenance Phase

Lessons Learned Project Lead, Contractor

A lessons learned document will be created to understand what worked well (and what didn’t) in the last release so that this experience can be used to improve the techniques used to develop future releases/systems.

45 days after production implementation

Patch Release/Deployment Plan

Contractor

This plan will provide the details about potential impacts/dependencies, and how to apply the patch in the production environment.

Based upon project plan