PROJECT

MANGMENT
LECTURE 01
 WHAT IS PROJECT MANGMENT
2

Projects have specific objectives.

Project objectives begin with analyzing
current conditions.
Based on the analysis, we design an
ideal process, specify targets and design
plan to achieve the
targets. Project manager’s (PM) task is
to run a project according to a plan and
achieve
objectives by applying knowledge and
skills about project management.
3
WHAT IS PROJECT MANGMENT

Stakeholders are the people involved in and

having interest in the project.
Stakeholders consist of PM, executives of your
organization/company, project team members
and vendors (suppliers).
Project managers must interact with those
stakeholders throughout the project
management life cycle.
One of the factors for a successful project is to
ultimately meet stakeholders’ requirements.
Therefore, we need to identify stakeholders at the
beginning of the project.
4
QCD-BASED PROJECT MANAGEMENT

Project Management Framework

QCD is an abbreviation of “Quality, Cost, Delivery”

QCD includes the following meanings:

•Q: Quality (quality of the project)

•C: Cost (cost to develop the project)
•D: Delivery (schedule to develop the project)
Since there are trade-offs among QCD conditions, it is
important to maintain a balance of the
conditions, knowing which of them are fixed and variable for
the target project.
In a QCD-based project management framework, PM’s
mission is to develop a quality product within a defined budget
and schedule. When a project is completed within
planned QCD conditions, it is a successful project.
5

THE 9 KNOWLEDGE AREAS OF PMBOK

6

9 KNOWLEDGE AREAS OF PMBOK

Project Integration Management: the processes required to ensure that the various elements of the
project are properly coordinated.
Project Scope Management: the processes required to ensure that the project includes all the work
required, and only the work required, to complete the project successfully.
Project Time Management: the processes required to ensure timely completion of the project.
Project Cost Management: the processes required to ensure that the project is completed within the
approved budget.
Project Quality Management: the processes required to ensure that the project will satisfy the needs
for which it was undertaken.
7

9 KNOWLEDGE AREAS OF PMBOK

Project Human Resource Management: the processes required to make the most effective use of the
people involved with the project.
Project Communications Management: the processes required to ensure timely and appropriate
generation, collection, dissemination, storage, and ultimate disposition of project information.
Project Risk Management: the systematic process of identifying, analyzing, and responding to project risk.
Project Procurement Management: the processes required to acquire goods and services, to attain the
project scope, from outside the performing organization.
8

WHAT IS A PROJECT MANAGEMENT

METHODOLOGY?
A project management methodology is a system of guided procedures for
managing a project. In other words, it’s a set of rules that you use to get your
project finished in the most productive way possible.

The reason there are different project management methodologies is because

there are different kinds of projects and different kinds of teams. These factors,
and more, will help determine which is the best methodology for you.
9

Waterfall Method
The Waterfall methodology is a linear, sequential
approach to project management. Each step of the
project must be completed before moving onto the next,
and progress flows downwards - like a waterfall.
It sounds pretty similar to Agile, but they differ in Waterfall
projects can be broken down into 7 steps, but not all
projects will pass through all of these

A key component of the Waterfall methodology is Pros:

documentation. Before moving on to the next step, team Expectations are clear from the outset
members are required to complete an extensive review, Documentation gives everyone a better
documenting anything of importance. This is crucial as there is understanding of the project
no going back to previous stages once they have been Progress is easy to measure
approved. Cons:
Lack of flexibility
Great for: Manufacturing and construction Requirements need to be determined
before the project starts
10

Agile Method

Agile project management allows team members

to break projects into small pieces, or
‘increments’ and review each one before moving
forward to the next.
This is great for complex and/or large scale
projects because it gives team members a
chance to respond to issues as they arise. By
making changes at the right time, resources can Pros:
be saved and teams can feel more confident that Changes can be made easily and with less risk
projects will fit within the allocated budget. Communication between team members is encouraged
Agile projects are typically split into six Increased productivity
increments Cons:
Great for: Software development Deadlines need to be flexible - as unexpected changes
can extend different increment times
Team members must work closely together and wear
many hats
11

Critical Path Method

The Critical Path method is all about efficiency. To start,

you list all of the tasks that need to be completed. Then
you map the duration of each task, and note whether one
task is dependent on another - for example, if you’re
making a video then you can’t start filming or animation
without first completing the script.

By mapping out these tasks you can then find out which
can be completed simultaneously, in order to save time.
Pros:
You’ll also know when to start and finish tasks that can’t
Better scheduling
be completed simultaneously in order to stay on track.
Better forecasting
•Complete your projects faster
Great for: Projects with multiple working parts Cons:
Reduced flexibility
It won't work for every project
12

Scrum Method

That Scrum project management revolves around teamwork.

Like Agile, projects are broken down into small increments.
These are called ‘Sprints’ and typically last for around two
weeks. During each sprint, teams are encouraged to be creative
and self-organised.
At the end of the sprint, there is a debrief meeting with
stakeholders. Here, everything is reassessed and next steps are
planned.
Scrum is a methodology that focuses on getting projects Pros:
right, not complete. So there is no fixed deadline in place Creativity is encouraged
and, as you can see from the above diagram, some steps Teamwork is encouraged
may be repeated. Changes are easy to implement
Cons:
Great for: Product development
Lack of a clear deadline
A lot is expected of team members
13

Lean Method

Lean, as the name suggests, is a methodology that focuses

on minimising waste. The idea is that by using fewer
resources you can increase customer value. This would
involve looking at your full process, and critically evaluating
opportunities to reduce waste.
Waste is grouped into three different categories: Muda,
Mura, and Muri.
Pros:
Muda refers to an activity or process that doesn’t add value, Projects remain in-budget
Mura refers to variations between stages, Perfection is the goal
Muri is all about getting rid of unnecessary overload Less waste
Cons:
•t requires a lot of reworking of existing
Great for: Manufacturing processes
It's an ongoing practice
14

Six Sigma Method

Six Sigma is a methodology that focuses on defect reduction, by
identifying errors in a process and removing them. It was originated by
Motorola in the mid 80s, then adopted at General Electric in the 1990s -
and subsequently by many organisations in different industries.

To sum it up in short, Six Sigma is all about reducing variation, which is

why it’s proved so popular in the manufacturing industry (and not so
much in software development.)

The goal of the Six Sigma methodology is, quite simply, a defect-free Pros:
process. This means that, in contrast to Agile methodologies which Increased chance of success
promote iteration and creative variation from stakeholders throughout Processes are more valuable
the process, Six Sigma is a highly structured methodology. It prizes Less waste
organisation, efficiency and scientific data at each stage, since the end Cons:
goal is precision and reliability. Difficult to implement
Requires people to get Six Sigma
Great for: Large companies with big projects to manage
certified
15

Hybrid Method

Hybrid take qualities from each and make a new methodology

Hybrid takes the in-depth analysis and documentation of

Waterfall and combines it with the flexibility of Agile to create a
methodology that will suit most businesses.

So you benefit from the clear planning and structure of Waterfall,

with the increased flexibility of Agile. The only difference Pros:
between this and Agile is that the planning stage is structured Increased flexibility
and thought-out first - leaving less room for changes and/or More structured
errors at later stages. The best of both worlds
Cons:
There is no clear structure
The compromise means you'll be
between two sets of rules
16

Assignment 01
Search examples of Project Management methods
Their advantages and disadvantages
What type of project they are best used for ?

What is the role of the project manager?

17

THANK YOU