SDLC Phase Deliverable

Initiation
Project Charter

Action Item Log

Agile Implementation Plan

Agile Maturity Matrix (Assessment)

Decision Log

Issues Log

Iteration Schedule

Meeting Agenda and Minutes

Monthly Health Assessment Report

Project Management Plan

Project Status Report

Requirements

Requirements Traceability Matrix (RTM)

Responsibility Assignment Matrix (RACI)

Risk Log
 Solution Roadmap

Test Case Specification

Test Plan

Training Plan

Data Conversion Plan

Disaster Recovery Plan

Disposition Plan

Interface Control Document

Execution Operational Readiness Assessment

System Administration Manual

System Design Document

System Security Plan

Test Summary Report

User Manual

Change Log
Control
Change Request Form

Close Out
MITDP Closeout Guide
 Description

A Project Charter is an elevator pitch of your project objectives, project scope, and project responsibilities
in order to get approval from key project stakeholders. In the charter, you should provide a short, succinct
explanation of the main elements of your project before you get started.

The Action Item Log is a kind of joint project team to-do list. It is used to record tasks that the project team
members are going to do so that they don't forget to do them. Typically, this list doesn't include things that
need to be done months in advance.
An Agile Implementation Plan outlines the process of executing a flexible project plan based on developing
small portions of a project at a time.
An Agile Maturity Assessment is a way to evaluate how a team is improving their ability to be agile over
time.

The Decision Log makes information available to people who were not present when the decision was
made, and also to provide easy access to key information about past decisions when questions arise.

An issue log is an important tool used to manage these issues and more, by helping the project team to
record issues that require resolution. Along with each issue, the person or team responsible for resolving
the problem is also documented

An iteration schedule is a series of fixed-length development periods, typically ranging from two to six
weeks, called iterations. Planning an iteration involves scheduling the work to be done during an iteration
and assigning individual work items to members of the team.
An agenda gives the meeting structure and also provides you with an outline for crafting your meeting
minutes and notes.
The Monthly Health Assessment Report provides a monthly update on the project status/accomplishments,
program increments, progress, budget, milestones, risks etc.

A Project management Plan is a formal, approved document that defines how the project is executed,
monitored, and controlled. It may be a summary or a detailed document and may include baselines,
subsidiary management plans, and other planning documents. This document is used to define the
approach the project team takes to deliver the intended project management scope of the project.

A Project Status report is a collection of information about the current status of a project. Project status
reports are used to communicate the current progress on a project to the project team and stakeholders.
A Requirements Document defines what is needed from the product. It states the product's purpose and
what it must achieve. It does not define how to deliver or build what is needed

The RTM is a document used to ensure that the requirements defined for a system are linked at every
point during the verification process. It also ensures that they are duly tested with respect to test
parameters and protocols.
A table that lists all stakeholders on a project and their level involvement in each task, denoted with the
letters R, A, C or I. Once these roles are defined, assignments can be attributed to the roles and work can
begin.

The Risk Register provides a means of recording the identified risks, the analysis of their severity and the
necessary management actions to be taken.
The Solution Roadmap provides a longer-term—often multiyear—view, showing the key milestones and
deliverables needed to achieve the solution vision over time. While most solutions require a 1-3 year view,
some larger solutions may extend this timeframe to many years.
The Test Case Specification Document outlines the details of what scenarios will be tested, how they will be
tested, how often they will be tested for a given feature.

A Test Plan refers to a detailed document that catalogs the test strategy, objectives, schedule, estimations,
deadlines, and the resources required for completing that particular project. Think of it as a blueprint for
running the tests needed to ensure the software is working properly – controlled by test managers.
The Training Plan is a document that communicates to management and stakeholders details of
the proposed training program.

The Data Conversion Plan describes the strategies involved in converting data from an existing system to
another hardware or software environment.
A Disaster Recovery Plan is a recorded policy and/or process that is designed to assist an organization in
executing recovery processes in response to a disaster to protect business IT infrastructure and more
generally promote recovery.

The Disposition Plan addresses how the various components of the system are handled at the completion
of operations, including software, data, hardware, communications, and documentation. The plan also
notes any future access to the system.

An Interface Control Document (ICD) provides a record of all interface information (such as drawings,
diagrams, tables, and textual information) generated for a project.
An Operational Readiness Assessment ensures the operating environment is prepared to effectively
support and accept the changes resulting from the project.
The Systems Administration Manual contains key information and Standard Operating Procedures (SOPs)
necessary to maintain the system effectively.

A System Design Document is a detailed description of the system requirements, operating environment,
architecture, files and database design. It also describes the input format, different interfaces, output
layouts, processing logic and detailed design.
The System Security Plan provides an overview of the security requirements of the system and describe the
controls in place or planned for meeting those requirements.
A Test Summary report is a quality work product/test document that formally summarizes the results of all
testing.
The User Manual is a document that assists end-users with using a particular system, product or service
seamlessly. It is also known as an instruction manual or a user guide.
A Change Log is a record of requests for change (RFCs) submitted for all changes in a project. It tracks the
progress of each
The Change change
Request from
Form submission
is the through
primary tool usedreview, approval,
for requesting, implementation
approving, and closure.
and documenting changes to
the project and is an important piece of the change management process

The MITDP Closeout Guide is a document used to assess the effectiveness of the system after it has been in
production for a period of at least six months and ensures all final project information is documented.
ITPR Phase Required for
(MITDPs) MITDPs

Planning X

N/A N/A

Planning X

Planning X

N/A N/A

N/A N/A

Planning X

N/A N/A

Planning X

Planning X

N/A N/A

Planning X

Planning X

Planning X

N/A N/A
 Planning X

N/A N/A

N/A N/A

N/A N/A

Implementation X

Implementation X

Implementation X

Implementation X

N/A N/A

Implementation X

Implementation X

Implementation X

N/A N/A

N/A N/A

N/A N/A
N/A N/A

Implementation X