Stakeholder Management

Stakeholder
The people involved in project activities or affected
by them.
Internal
Project Sponsor
Project team
Support staff
Internal customers
Top management
Functional managers
Other project
managers

External
Project customers
Competitors
Suppliers

The Importance of Top Management

Commitment
Top Management the person or group of people
who directs and controls an organization at the
highest level.

Responsibilities of Top Management

To set and communicate policies and objectives
throughout the organization, raising awareness,
motivation and involvement.
To ensure a focus on customer requirements
throughout the organization.
To ensure that appropriate processes are
implemented to meet customer requirements and
organizational objectives.
To ensure that adequate resources are provided to
meet the organizations objectives.

 To ensure that an effective and efficient quality

management system is established, implemented
and maintained to achieve these quality
objectives.
To regularly review the effectiveness of the
management system, its policies and objectives.
To decide on actions regarding the quality policy
and quality objectives.
To decide on actions for improvement of the
quality management system.

Reasons why top management

commitment is crucial:
Project managers need adequate resources.
Project managers often require approval for
unique project needs in a timely manner.
Project managers must have cooperation from
people in other parts of the organization.
Project managers often need someone to
mentor and coach them on leadership issues.

PROJECT PHASES AND

PROJECT LIFE CYCLE

 Project Life Cycle a collection of project

phases, which also define what work will be
performed in each phase, what deliverables
will be produced and when, who is involved
in each phase.
Deliverable a product or service, such as
technical report, a training session, a piece
of hardware, or a segment of software code,
produced or provided as part of a project.

Early phase in PLC:

Resource needs are usually lowest and
the level of uncertainty is highest.
Project stakeholders have the greatest
opportunity to influence the final
characteristics of the projects products,
services, or results.

 Project Managers view at the beginning.

Middle phase in PLC:

Certainty of completing the project
improves as it continues.
More information is known about the
project requirements and objectives.
More resources needed.

 More clearer objectives about the project,

more resources are identified for the
project.

Final phase in PLC:

Focuses on ensuring that project
requirements were met.
Projects sponsor approves completion of
the project.

General Phases in Traditional Project

Management
Concept
(starting the project)
Development
(organizing and preparing)
Implementation
(carrying out the project work)
Close-out
(finishing the project)

Project
Feasibility

Project
Acquisition

Note:
A project should successfully complete
each phase before moving on to the
next.

Phases of a traditional Project Life Cycle

Concept Phase:
Business Case include an initial, smaller project
to investigate alternative ways of increasing
the use of technology.
Preliminary Cost Estimate 6 months and $20,000
to conduct a detailed technology study.
WBS study might have 3 levels and partition the
work to include a competitive analysis of what
five similar campuses were doing, a survey of
local students, staff, and faculty, and a rough
assessment of how using more technology
would affect costs and enrollments.

 Concept phase report

A. Requiring students to have tablets was one
means of increasing the use of technology
on campus.
B. Tablets were not a good idea for the college.

Development Phase:
A.

B.

The team would have to decide if students

would purchase or lease the tablets, what type
of hardware and software the tablets would
require, how much to charge students, how to
handle training and maintenance, and how to
integrate the use of the new technology with
the current courses.
The project team would no longer consider
increasing the use of technology by requiring
tablets in the development phase and would
cancel the project before development.

Implementation Phase:
A.

The project team would need to obtain the

required hardware and software, install the
necessary network equipment, deliver the
tablets to the students, creates process for
collecting fees, and provide training to
students, faculty and staff.

Close-out Phase:
In it, all the work is completed, and customers
should accept the entire project.
Project team should document its experiences on
the project in a lessons-learned report.
Team members might administer survey to
students, faculty, and staff to gather opinions on
how the project fared.
They would ensure that any contracts with
suppliers were completed and that appropriate
payments were made.

Product Life Cycle

The process for building information
systems in a very deliberate, structured
and methodical way, reiterating each
stage of the products life.

Systems Development Life

Cycle (SDLC)
A framework for describing the phases of
developing information systems.
A conceptual model used in project
management that descries the stages
involved in an information system
development project.

Relationship between PLC and SDLC

The systems development life cycle
(SDLC) becomes part of the project life
cycle (PLC).
The PLC focuses on the project management
phases, processes, tools and techniques for
effectively managing the project.
The SDLC focuses on the software
engineering phases, processes, tools and
techniques for building and/or implementing
the IT solution.

Relationship Between the PLC & SDLC

Concept

Planning

Development

Analysis

Design

Implementation

Implementation

Closing

Maintenance and
Support

Predictive life cycle

The scope of the project can be articulated
clearly and the schedule and cost can be
predicted accurately.
Waterfall model
Spiral model
Incremental build model
Prototyping model
RAD (Rapid Application Development)
model

Waterfall life cycle model

Has a well-defined, linear stages of
systems analysis, design, construction,
testing, and support.
Used in many large-scale systems
projects where complexity and cost are so
high that the more rigid steps of the
approach help to ensure careful
completion of all deliverables.

Waterfall model
Analysis

Design

Construction

Testing

Support

Prototyping life cycle model

Used for developing software prototypes
to clarify user requirements for operational
software.
Often used in systems that involve a great
deal of user interface design, such as Web
site projects, in systems that automate
previously manual functions, or in systems
that change the nature of how something
is done, such as mobile applications.

Diagram for SDLC with prototyping

Identify User
Requirements

Analyze Prototype
(Input- Processing
Output)

Implement Prototype

Revised through
iterative process

Post Implementation

Final Conversion

Spiral life cycle model

Developed based on refinements of the
waterfall model as applied to large
government software projects.
Suitable for projects in which changes can
be incorporated with reasonable cost
increases or with acceptable time delays.

Incremental Build life cycle

model
Provides for progressive development of
operational software, with each release
providing added capabilities.
Helps to stage the priorities of the
packages features and functions with user
priorities or the costs, time, and scope of
the system revisions.

RAD life cycle model

Uses an approach in which developers
work with an evolving prototype and
requires heavy user involvement and
helps produce systems quickly without
sacrificing quality.

 Requirements planning phase

combines elements of the system
planning and systems analysis phases of
the SDLC.
User design phase user interact with
systems analysts and develop models and
prototypes that represent all system
processes, inputs, and outputs. It is a
continuous interactive process that allows
users to understand, modify, and
eventually approve a working model of the
system that meets their needs.

 Construction phase focuses on

program and application development task
similar to the SDLC.
Cutover resembles the final tasks in the
SDLC implementation phase, including
data conversion, testing, changeover to
the new system, and user training.

Adaptive Software Development (ASD)

Used to provide more freedom than the
prescriptive approaches, that allows
development using a more free-form
approach to create components that
provide the functionality specified by the
business group.

Agile software development

Group of software development
methodologies based on iterative and
incremental development.
Requirements and solutions evolve
through collaboration between self
organizing, cross functional teams.

Adaptive vs. Predictive

Adaptive methods focus on adapting
quickly to change.
When the project requirement change, the
adapted team also change.
An adaptive team can not report exactly
what tasks are being done next week.

Adaptive vs. Predictive

Predictive method focus on planning the
future in details.
Predictive team can report exactly what
features and tasks are planned for the
entire length of the development process.
Predictive team have difficulty changing
direction, the plan is typically optimized for
the original destination and changing
direction can require completed work to be
started over.