Phase 1: Problem Definition: Document: The Life Cycle of An IT Project

You might also like

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 3

Document: The Life Cycle of an IT Project

Phase 1: Problem Definition


In simple terms, this phase involves all the initial activities that will be needed for
the project. One of the first steps in this phase is the conceptualization of the
project itself.

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

Phase 2: Planning and Design


This phase intend to prepare the essentials of the project even before execution.
These essentials include the composition of the project team and the assignment of
each member, a clear timetable, a work breakdown structure, a finite budget, and
ready contingencies. Beyond these essentials, the project team also allocates
enough resources for requirements such as office space, computers, special
peripherals, etc.

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.

As part of this activity, documents such as Functional Specifications are created


and agreed upon. Clients are involved in the decision-making process where
possible, and the output documents are signed off to signify agreement.

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.)

Page 1 of 3 Document: The Life Cycle of an IT Project


Phase 3: Development
This is usually where most of the work is done. In this phase, the actual codes are
put together by the developer, applications are integrated, and databases created.
This phase is responsible for translating the scope and agreements of the previous
phases into working applications.

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:

 Graphics/Animation Module – generates the graphical representations of the


cards and the animation for actions that may be taken.
 Deck Shuffler Module – shuffles the virtual deck.
 Opponent AI Module – player’s opponent’s decision-making program.
 User Interface Module – graphical user controls.

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.

Page 2 of 3 Document: The Life Cycle of an IT Project


After these final tasks have been accomplished, the project is signed off to
officially signify the project’s completion.

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.)

Resources in Creating a Website


Hardware
Development Environment (IDE i.e. Eclipse, Visual Studio,
Expression Web)
Server
Connection to the Internet

Software
Operating System
Graphics Software
Programming Languages
Database Management System

Human Resources
Project Manager
Information Architect
Web Designers/Developers
Testers & Maintenance
Content Writers

Page 3 of 3 Document: The Life Cycle of an IT Project

You might also like