For most projects, their origin is linked to the identification of a need (for example 'a

project responding to new government safety legislation'), a problem (for example 'a

project to install a new machine to remove a bottleneck') or an opportunity within the

organization (for example projects originating from the creative ideas of individual

employees.
Needs & Demands of Projects……
Needs & Demands of Projects……
 Class Case study
The need, problem or opportunity

 Background Info
Star Achievement (SA) is a nonprofit education organization
that inspires young people to value free enterprise, business
and economics to improve the quality of their
lives…………………………………………
Project Life Cycles (PLC)
 A project life cycle refers to the stages in a project’s
development.
 Life cycles are important because they demonstrate the
logic that governs a project.
 They also help us develop our plans for carrying out the
project.
 Four distinct phases:
 Conceptualization /Initiation
 Planning
 execution,
 and termination.
Project life cycle Stages
 Project Life Cycle

Concept/Initiation Planning Execution/Control Closing

Definition | Analysis |Design|Build|Test|Accept| Implement|
Operation 20% 60%

5% 15%

Percentages and graph refer to the amount of effort (people)

In IT projects = 90-95% of cost!

8
 Stage 1
Conceptualization/Initiation

 Conceptualization refers
to the development of
the initial goal and
technical specifications
for a project.
 Stage 2
Planning

 Planning is the stage in which all detailed

specifications, schematics, schedules, and
other plans are developed.
 The individual pieces of the project, often
called work packages, are broken down,
individual assignments made, and the process
for completion clearly delineated.
 For example, in planning our approach to
complete the term paper, we determine all
the necessary steps (research, drafts, editing,
etc.) in the process.
 Stage 3
Execution

 During execution, the

actual “work” of the project
is performed, the system
developed, or the product
created and fabricated.
 It is during the execution
phase that the bulk of
project team labor is
performed.
 Stage 4
Termination/Closure

 Termination occurs when the

completed project is
transferred to the customer,
its resources reassigned, and
the project formally closed
out.

 As specific sub-activities are

completed, the project shrinks
in scope and costs decline
rapidly.
Project lifecycle Approaches
 The PMBOK® Guide defines a few patterns of work that
projects follow. Those patterns are called lifecycles, and
thinking about the lifecycle your project will follow
determines a lot about the approach you’ll take to
delivering the product you set out to create.
Predictive Project Lifecycle
 First of all, this is traditional project life cycle used
commonly.
 Project scope, time and cost are fixed and will be
determined as early as possible in the life cycle of the
project.
 Projects divide into multiple phases. Each phase runs
sequentially or in a overlapping fashion based on the
dependencies.
 The current project life cycle stage must complete, before
starting the next project life cycle stage.
Predictive Life Cycle….
 Certainly changes are expensive in this project life cycle.
 If the changes occur in the later stages, it will become even more
expensive due to rework that will increase.
 Product or the final result will deliver at the end of the project after
completing all the phases.
 Most importantly defects only found during testing phase or after
producing the end result. Hence they may become expensive to the
project.
 Customer engagement in this case would be very limited. Especially,
customer would be engaged more during requirements phase (in
the beginning) and in the testing/acceptance phase (in the end).
 This makes the predictive life cycle inefficient, as the projects and
changes are becoming very dynamic in nature.
 The best example of the predictive life cycle that we all have heard
is water fall model.
Iterative project lifecycle

 Unlike in the predictive life cycle, in the iterative project

life cycle, projects run in multiple iterations.
 The project divides into multiple phases. Every phase can
be run sequentially or overlapping fashion based on the
dependencies. Each phase can run through multiple
iterations.
 Each iteration goes through all software development life
cycle (Requirements, design, coding, testing, deployment
and support) phases.
 Every iteration produce output for that iteration. In case,
if there a change in any of the iteration, the change will
move in to the next iteration depending on its priority.
Iteration Life cycle….
 Customer will receive the value early in the project, as
the partial output is produced at the end of iteration.
Customer will have more confidence by looking at the
completed part of the output.
 And if there are any gaps, customer can provide his
feedback, which can be considered for any required
changes in the subsequent iterations.
 Customer involvement is more here, as every iteration
goes through the entire SDLC.
Adaptive Project Lifecycle

Adaptive lifecycles are all about change.

 Furthermore, Adaptive life cycle is also similar to iterative life cycle,
except that
 When you expect high number of changes, adaptive life cycle is best to
use
 And scope is not clear in the beginning of the project.
 Compared to iterative, adaptive life cycle have more iterations.
 In adaptive project life cycle, every iteration may produce a usable
product (with partial features). So customer can also work in
parallel to test and accept the work packages after every iteration,
so as to save huge amount of project lead time.
 So adaptive life cycle is more agile in nature and is more responsive
to changes.
 Changes handle naturally as they occur. Hence it is very less risky.
 Customer involvement is there all the time, during the course of the
complete project.
Incremental Project Life Cycle

 Teams that use incremental lifecycles deliver small, usable

pieces of work to their stakeholders for feedback through
a series of iterations.
 Incremental development lifecycles are much closer to
adaptive ones but differ in that the increments produced
here cannot be considered final products but must be
combined in a final iteration to be considered complete.
 Hybrid Project Life Cycle

 The term hybrid describes any combination of predictive

and adaptive approaches.
 Project managers often have an important role in helping
the team decide which approach to take.
 You can follow one of the lifecycles defined here, or make
a new combination of predictive and adaptive practices
that better suits your organization.
 Changes Evolve during project Life cycle
 The project life cycle is also a useful means of visualizing
the activities required and challenges to be faced during
the life of a project.

 Five components of a project may change over the course

of its life cycle:
 Client interest: The level of enthusiasm or concern
expressed by the project’s intended customer. (Clients)
can be either internal to the organization or external.
 Project stake: The amount of corporate investment in
the project. The longer the life of the project, the greater
the investment.
 ---
 Resources: The commitment of financial, human, and
technical resources over the life of the project.
• Creativity: The degree of innovation required by the
project, especially during certain development phases.
• Uncertainty: The degree of risk associated with the
project. Riskiness here reflects the number of unknowns,
including technical challenges that the project is likely to
face. Uncertainty is highest at the beginning because many
challenges have yet to be identified, let alone addressed
Project Life Cycles and Their Effects

Client
Interest

Project Stake

Resources

Creativity

Uncertainty

Conceptualizatio Planning Execution Termination

n
The Triple Constraint

Successful project
management means
meeting all three
goals (scope, time,
and cost) – and
satisfying the
project’s sponsor!

33
 Time

 Time – This refers to the actual

time required to produce a
deliverable. Which in this case, would
be the end result of the project.
Naturally, the amount of time
required to produce the deliverable
will be directly related to the
amount of requirements that are
part of the end result (scope) along
with the amount of resources
allocated to the project (cost).
 COST

 Cost – This is the estimation of the

amount of money that will be
required to complete the project.
Cost itself encompasses various
things, such as: resources, labor
rates for contractors, risk
estimates, bills of materials, et
cetera. All aspects of the project
that have a monetary component
are made part of the overall cost
structure.
 SCOPE

 Scope – These are the functional

elements that, when completed, make
up the end deliverable for the project.
The scope itself is generally identified
up front so as to give the project the
best chance of success. (Although scope
can potentially change during the
project life-cycle, a concept known as
‘scope creep’) Note that the common
success measure for the scope aspect of
a project is its inherent quality upon
delivery.
Quadruple Constraint of Project
Success

Client
Budget Acceptance

Success

Schedule Performance