Professional Documents
Culture Documents
Phase 1: Problem Definition: Document: The Life Cycle of An IT Project
Phase 1: Problem Definition: Document: The Life Cycle of An IT Project
Phase 1: Problem Definition: Document: The Life Cycle of An IT Project
The idea has to be translated into a documented form and agreed upon by the
project team. In the problem definition phase, the project team lays down the
foundation of the project in terms of:
Objectives
Scope
Acceptance Criteria
Activities Deliverables
Conceptualization Concept Paper
Broad Scoping
Creation of Acceptance Criteria
During this phase, the team gets into high gear and an increase in project effort will
be noticed. The details for the general agreements on the concept and scope of the
project are created.
Project designs are also created during this phase. Depending on its nature, and IT
project may require various types of designs. A simple Web project, for example,
would only necessitate the creation of a Web page/interface design. For a project
that involves rolling out an employee information system, however, systems
architecture and database designs will have to be created.
Activities Deliverables
Project Team identification and Project Team Composition
mobilization Project Timetable
Detailed Project Scoping Detailed Scope (Functional
Project Requirements Analysis Specifications, Use Cases)
Project Designing Design Documents (Web Design,
Database Design, etc.)
For complex projects, the application being developed is broken down into smaller
programs called modules. An IT project that aims to develop a computer Black
Jack game, for example, may have the following modules:
Each of these modules would need to have a specific development schedule which
will be reflected as a separate item in the timetable. As the development phase
windows down and nears completion, all the separate modules are integrated to
form the application.
Activities Deliverables
Code Development Software for Testing
Module Testing
Module Integration
Phase 4: Testing
A consolidated testing occurs after phase 3 has been accomplished. In Phase 4,
codes are tested to make sure that they address the defined user requirements and
that they are bug-free.
Activities Deliverables
Testing/Debugging Acceptance Documents
Revisions System for Deployment
Phase 5: Deployment
Once the system has been accepted by the stakeholders, the project is launched
and exposed to the targeted users. There are still some activities that have to
occur before the project is closed. These activities may range from simple
announcements informing users that they system is ready for use, to migrating a
system/website into live servers, to filling up a database with content. Deployment
may also include user training and the creation of user manuals.
Activities Deliverables
Migration Live System/Website
Training User Training
Documentation User Manuals
Phase 6: Maintenance
After deployment, the need to maintain the delivered system arises. In this phase,
the developers of the system should be able to provide technical support for the
users of the system. It is even possible that bugs may be discovered in this stage,
thus, developers need to fix them as they occur. Also, users may require the
developers to make changes to the system as needed.
Activities Deliverables
Debugging of newly discovered Technical Support
errors Reports (status of the system, bugs,
Monitoring the system etc.)
Software
Operating System
Graphics Software
Programming Languages
Database Management System
Human Resources
Project Manager
Information Architect
Web Designers/Developers
Testers & Maintenance
Content Writers