Kingdom of Saudi Arabia

Ministry of Higher Education

Al-Imam Muhammad Ibn Saud Islamic University
College of Computer and Information Sciences

Lecture 2:
project lifecycle & project management PROCESS GROUPS

IT301– Projects Management

1
Objectives

 Understand & describe the project life cycle

 Describe system development life cycle

 Describe some SDLC models

 Describe the project management process groups

2
 PROJECT PHASES AND THE PROJECT LIFE
CYCLE

Project Phase:
A project is divided into
several phases.

3
PROJECT PHASES AND THE PROJECT LIFE
CYCLE

Why?
Project Phase:
A project is divided into
several phases.

Projects operate as part of a system

and involves uncertainty
4
 THE PROJECT LIFE CYCLE

:Defines
 What work will be performed
in each phase?

What deliverables will be

produced and when?
5
 System Development Lifecycle
Deliverable
A product or service produced or provided as
part of a project, such as:
 Technical report
 Training session
 Piece of hardware
 Segment of software code
6
 THE PROJECT LIFE CYCLE
:Defines

 Who is involved in each

phase?

 How management will control and

approve work produced in each phase?

7
Phases of the Traditional Project Life Cycle
Planning Deliverind the actual work

8
System Development Life Cycle

 SDLC is a framework for describing

the phases of developing information
systems – product life cycle

 Consists of 4 general phases.

9
System Development Life Cycle

Planning

Analysis

Design

Implementation
10
SDLC - Planning
The planning phase is the fundamental process
of:
 Understanding why an information system
should be built

Determining how the project team will go

about building it.

Output: project plan 11

SDLC - Analysis
The analysis phase answers the
questions of:
 Who will use the system?
 What the system will do?
 Where and when it will be used?

12
SDLC - Analysis

Investigate the current system (called

the as-is system) and its problems and
the ways to design a new system
(called the to-be system).

13
 SDLC - Analysis
The analysis of the information produced from
requirements gathering (e.g., through interviews or
questionnaires). —in conjunction with input from the
project sponsor and many other people—leads to the
development of a concept for a new system.

Output: a system proposal

14
 SDLC - Design
The design phase decides how the system will
operate, in terms of :
The hardware, software, and network infrastructure
The user interface, forms and reports
The specific programs, databases, and files that will
be needed.

15
 SDLC - Design

The design phase determine

exactly how the system will
operate.

16
SDLC - Design
The design strategy is first developed to clarify:
 Whether the system will be developed by the company’s own
programmers

Whether the system will be outsourced to another firm (usually a

consulting firm)

Whether the company will buy an existing software package.

17
 SDLC - Design
This leads to the development of:

The basic architecture design for the system, which

describes the hardware, software, and network infrastructure to be used.

The interface design specifies how the users will move

through the system (e.g., navigation methods such as menus and on-
screen buttons) and the forms and reports that the system will use.

18
 SDLC - Design
This leads to the development of:

The database and file specifications are developed. These define

exactly what data will be stored and where they will be stored.

The program design, which defines the programs that need to be

written and exactly what each program will do.

Output: system specification (architecture design, interface design,

database design, program design)

19
SDLC - Implementation
 The final phase in the SDLC is the
implementation phase, during which the system
is actually built.

 This is the phase that usually gets the most

attention, because for most systems it is the
longest and most expensive single part of the
development process.
20
SDLC - Implementation

System construction - The system is

built and tested to ensure it performs as
designed.
The system is installed and users are
trained on how to use the new system

21
SDLC - Implementation

Establishes a support plan for the system. This

plan usually includes a formal or informal post-
implementation review as well as a systematic way for
identifying major and minor changes needed for the
system.

22
SDLC - Implementation

What are the major outputs for

this final phase?

23
SDLC Models

1. Predictive Life Cycle

2. Adaptive software
development (ASD) - Agile

24
 SDLC Models
Predictive life cycle
The scope of the project can be articulated clearly
and the schedule and cost can be predicted
accurately.

The project team spends a large portion of the

project attempting to clarify the requirements of
the entire system and then producing a design.

25
SDLC Models
Predictive life cycle

 Users are often unable to see any tangible

results in terms of working software for an
extended period.

 Eg. Waterfall, incremental, iterative, spiral,

prototyping

26
 Waterfall Model
The waterfall model (known as the one-shot
or once-through approach) is the basic
phased model of a development cycle.

From where come the name for the

model?

What is the best feature in this model?

When we can use it?

What are the Drawback?

27
Waterfall Model

From where come the name for the

model?

The model takes its name from the

way each phase cascades into the
next.

28
Waterfall Model
What is the best feature in this model?

This approach provides for

feedback loops which are
activated when there is a
need to revisit an earlier
stage to redesign, recode
and so forth.
29
Waterfall Model

When we can use it?

This model is best used on

projects where requirements
have been clearly defined
and agreed.
30
Waterfall Model

What are the Drawback?

The amount of project documentation
which can be created.

The distinct testing phase at the end

of the project means major defects

could be undetected until late in the

project, when they are more difficult to

repair.

31
Waterfall Model

What are the

Drawback?
It is easy to misjudge progress:
just because the requirements

have been signed off, it does not

necessarily mean the

requirements have been clearly

understood

32
33
 Incremental model
Incremental model is similar to
the waterfall model, it involves
the development and delivery of
functionality in fragments or
increments.
So what is the different?

34
 Incremental model

So what is the different?

Global requirements are defined

and an overall architecture
designed. Then the product is
developed in increments. After each
increment is designed, developed
and tested, it is system tested and
then becomes operational.

35
 Incremental model

Works best when the requirements

well-known.
 It can work well with larger
projects.

36
 Iterative model
This model is suited to situations in
which the requirements are not clearly
understood and where there is a need
to begin development quickly
To create a version of the product
which will demonstrate its look and
feel.(The first version called……)

37
Iterative model
What is the advantages and
disadvantages?

 A risk associated with this model is

not knowing when to stop iterating.
 The iterative approach is potentially
difficult to monitor and control.

38
 Iterative model

What is the advantages and

disadvantages?

Help the customer identify and refine

requirements and design features.
The customer can make suggestions
for possible changes to be
incorporated into a further version of
the software which is then evaluated.
39
40
Can we use more than one model ? Specify?

The incremental and iterative models work well together.

An application can be broken down into a number of
increments, each of which can be implemented through a
series of iterations

41
SDLC Models

1. Predictive Life Cycle

2. Adaptive software
development (ASD) - Agile

42
Agile in PM

43
SDLC Models
Adaptive software development (ASD) -
Agile

Software requirements cannot be clearly

expressed early in the life cycle

Software is developed using a less

structured, flexible approach.

44
 SDLC Models

Adaptive software development (ASD) - Agile

Software developer focus on the rapid creation of

working code and an evolution of the entire
software system.

Eg. Extreme programming, feature driven

development, dynamic systems development,
scrum.
45
Scrum
A leading agile development method for completing
projects with a complex, innovative scope of work.

46
Scrum

47
48
 PROJECT MANAGEMENT PROCESS GROUPS

A process is a series of actions directed toward a particular result.

The project management process include:
1. Initiating processes.
2. Planning processes.
3. Executing processes.
4. Monitoring and controlling processes.
5. Closing processes.
Process groups can be applied to each phase of the project.

49
 Project Management Process Groups

Monitoring
Initiation Planning Execution Closing
& Control

50
 Active Learning Activity

 Read each point


Please note that :

Some points define the


 Discuss with your process group

group to which process

Some points are
processes or activities
group it should belong. under that process group

51
 Active Learning Activity

Open the envelope and  You can search the


take the points that internet
belong to your process If you have a question


×
groups you can ask me
 Place each point under

each process group
×
 you can not look into
the course lecture notes

52
 What belongs where?
Kingdom of Saudi Arabia
Ministry of Higher Education
Al-Imam Muhammad Ibn Saud Islamic University
College of Computer and Information Sciences

ACTIVE LEARNING ACTIVITY

53
Project Management Process

1. Initiating processes include defining and authorizing a

project or project phase:
 Prepare Project Charter, which is a document that
describe the project and it’s goals.
 Identify stakeholder.
 Take place at the beginning of each phase.
 Re-examine the business need for the project during
every phase of the project life cycle, to determine if the
project is worth continuing, should be redirected, or
canceled. 54
 Project Management Process

2. Planning processes include devising and maintaining a workable

scheme to ensure that the project addresses the organization’s needs.
There are several plans for projects: (Documents)
 Scope plan: define the work that needs to be done.
 Schedule plan: Schedule activities related to the work
 Cost plan: estimate cost for performing the work.
 Quality plan: product meets written specifications and
intended use.
 Procurement plan: decide what resources to produce to
accomplish the work.
55
Project Management Process

2. Planning processes

To account for changing conditions on the project

and in the organization, project teams often revise
plans during each phase of the project life cycle

56
Project Management Process

3. Executing processes include coordinating people and

other resources to carry out the various plans and
produce the products, services, or results of the project or
phase.
 Acquiring and developing the project team.
 Performing quality assurance.
 Managing stakeholder expectations.
 Conducting procurements.
57
Project Management Process

4. Monitoring and controlling processes

 Include measuring and monitoring progress against all
plans to ensure that the project team meets the project
objectives, stakeholder needs, and quality standard.
 Reporting performance is a common controlling and
monitoring process, where project Stakeholders can
identify any necessary changes to keep project on track.

58
Project Management Process

5. Closing processes include formalizing acceptance of

the project or project phase and ending it efficiently:
 Archiving project files.
 Closing out contracts.
 Document lessons learned.
 Receiving Formal acceptance of the delivered
work as part of the phase.

59
MAPPING THE PROCESS
GROUPS TO THE
KNOWLEDGE AREAS

60
Managing project team

61