An Overview of

Information Technology
Project Management

1-1
Chapter 1

The Nature of
Information Technology
Projects

1-2
Chapter 1 Objectives
Describe the software crisis and how the often
dismal track record for information technology
(IT) projects provides a motivation for changing
how we view and manage IT projects.

Explain the socio-technical, project management,

and knowledge management approaches that
support ITPM.

Define what an IT project is and describe its

attributes.

Define the discipline called project management.

1-3
 Contd.,
Describe the role and impact of IT projects on an
organization.

Identify the different roles and interests of project

stakeholders.

Describe the project life cycle, the systems

development life cycle, and their relationship.

Identify the Project Management Body of

Knowledge (PMBOK) and its core knowledge
areas.
1-4
The Software Crisis
Software crisis is a term used in the early days of
computing science for the difficulty of writing useful and
efficient computer programs in the required time.

The software crisis was due to the rapid increases in

computer power and the complexity of the problems

1-5
 Software Crisis
It was in late 1960s
Many software projects failed.
Many software projects - late, over budget - providing unreliable
software which is expensive to maintain.
Many software projects produced software which did not
satisfy the requirements of the customer.
Complexities of software projects increased as hardware
capability increased.
Larger software system is more difficult and expensive to
maintain.
Demand of new software increased faster than ability to update
the existing software
All the above attributes of what was called a Software Crisis.
So the term Software Engineering first introduced at a
conference in late 1960s to discuss the software crisis.
Why Projects Fail CHAOS
STUDY

1-7
Improving the likelihood of success
Socio-technical Approach
To improve the chances of IT project success by focusing on
the tools , techniques and methodologies of IT
development.
Purely Technical approach.
Improves the active participant and their involvement.

Project Management Approach

The step-by-step activities , processes, tools ,quality
standards ,controls and deliverables.
Also supports
Resources estimation cost and schedules.
Expectations Clients expect quality products and
services in a professional manner.
Competition Competition among consultants
Efficiency And Effectiveness doing the thing right and
doing the right things.

1-8
 Contd.,
Knowledge Management Approach
Is a relatively new area . It s systematic process for
acquiring ,creating, synthesing, sharing and using
information , insights, experiences to transform ideas
into business value.

Lessons Learned
Best Practices

1-9
Chaos Study

1-
10
The context of project
management
Project Definitions
A project is a temporary endeavor undertaken
to accomplish a unique purpose.

Project management is the application of

knowledge, skills, tools, and techniques to
project activities in order to meet or exceed
stakeholder needs and expectations from a
project

1-
11
 The context of project management
Project Attributes:
Time Frame Must have a definite beginning and end.
Purpose projects are undertaken to accomplish something.
Project should have a goal to drive the project in terms of defining
the work to be done, its schedule, its budget and to provide the
project team with a clear direction.
Ownership The project must provide something of value to
an individual or group who will own the product after its
completed.
Resources time , money ,people and technology .
Roles
Risks & Assumptions
Interdependent tasks
Organizational change
Operating Environment
1-
12
The Triple Constraint

1-
13
 Roles
Project Manager -The project manager is the tram leader and is responsible for
ensuring that all of the project management and technical development processes
are in place and are being carried out within a set of specific requirements.

Project Sponsor The project sponsor may ne the client ,customer or

organizational manger .

Subject Matter Expert(s) (SME) - user / client who has specific knowledge
,expertise or insight in a specific functional area needed to support the project.

Technical Expert(s) (TE) - TE is needed to provide a technical solution to an

organizational problem. TEs Can include systems analysts, network specialists ,
programmers , graphic artists , trainers and so forth.

1-
14
Risks & Assumptions
Internal estimation process/ project lead could
leave in the middle of project and etc.
External could arise from contractors or vendors.
Assumptions
Interdependent tasks
Hardware
Certain requirement cant be incorporated into the design
until a key user is interviewed.

1-
15
The Project Life Cycle
and
IT Development

1-
16
Definitions
Project Life Cycle (PLC)
Deliverables
Phase exits, stage gates, or
kill points
Fast tracking

1-
17
Generic Project Life Cycle

1-
18
Phases/Stages of PLC
Define project goal
Plan project
Answer questions (What, why, how, who, et al)
Baseline plan
Baseline plan
Close project
Evaluate project

1-
19
Systems Development Life Cycle

1-
20
Systems Development Life Cycle
SDLC: sequential phases or stages an
information system follows throughout its
useful life.
Phases/Stages
Planning
Analysis
Design
Implementation
Maintenance and Support

1-
21
Implementing SDLC:
Structured Approaches:
Waterfall Method

1-
22
Implementing SDLC:

Rapid Application Development (RAD)

Approaches:

Prototyping
Spiral
Development
Extreme Programming

1-
23
The PLC vs the SDLC

1-
24
Project Management Body of
Knowledge

1-
25
Project Management Knowledge
Areas

1. Project integration management

2. Project scope management
3. Project time management
4. Project cost management
5. Project quality management

1-
26
 Project Management Knowledge
Areas

6. Project human resource management

7. Project communication management
8. Project risk management
9. Project procurement management

1-
27