Scribd
Upload
52 views

Module 7 Agile Project Management

This document provides an overview of an Agile project management module. It discusses the differences between traditional and Agile project management, identifies core Agile principles like iterative development and customer collaboration, and recognizes Scrum as a popular Agile methodology. The document also outlines the schedule for an online class on Agile project management and notes some limitations of the Agile approach.

Uploaded by

Sam Alvarez
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
52 views

Module 7 Agile Project Management

This document provides an overview of an Agile project management module. It discusses the differences between traditional and Agile project management, identifies core Agile principles like iterative development and customer collaboration, and recognizes Scrum as a popular Agile methodology. The document also outlines the schedule for an online class on Agile project management and notes some limitations of the Agile approach.

Uploaded by

Sam Alvarez
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 21

AGILE

PROJECT MANAGEMENT
MODULE 7
Module Overview
• Understand what are the differences
between traditional project
management and agile project
management.
• Identify core Agile principles
• Understand the basic methodology
used in Scrum.
• Recognize the limitations of Agile
project management.

2
CLASS SCHEDULE – NOVEMBER 22, 2021
Time Activity
6:00 PM to 7:00 PM Online Discussion and Recitation
7:00 PM to 7:30 PM Quiz 4 (30 minutes)
7:30 PM to 8:00 PM Quiz 5 (30 minutes)
8:00 PM to 9:00 PM Allotted time for the assignment

3
We know less about the project today
than at any time in the future.

CHET HENDRICKSON
TRADITIONAL VS. AGILE

5
TRADITIONAL VS. AGILE

6
TRADITIONAL VS. AGILE

7
TRADITIONAL VS. AGILE

Traditional project management requires a fairly


high degree of predictability to be effective. For
plans to be useful managers have to have a firm
idea on what is to be accomplished and how to do
it. For example, when it comes to building a bridge
across a river, engineers can draw upon proven
technology and design principles to plan and
execute the project. Not all projects enjoy such
certainty. Project uncertainty varies according to
the extent the project scope is known and stable
and the technology to be used is known and proven.

8
CORE AGILE PRINCIPLES

9
CORE AGILE PRINCIPLES
Iterative, Incremental Product Development

10
CORE AGILE PRINCIPLES
Iterative development processes provide the following important advantages:
• Continuous integration, verification, and validation of the evolving product.
• Frequent demonstration of progress to increase the likelihood that the end product
will satisfy customer needs.
• Early detection of defects and problems.

11
CORE AGILE PRINCIPLES
It should be noted that Agile PM is not one set method, but a family of methods
designed to respond to the challenges of unpredictable projects. A few of the more
popular ones are listed here:

• Scrum
• RUP (Rational Unified Process)
• Extreme Programming (XP)
• Crystal Clear
• Agile Modeling
• Dynamic Systems Development Method (DSDM)
• Lean Development
• Rapid Product Development (RPD)
12
CORE AGILE PRINCIPLES
While each of these methods has unique elements and applications, most are based on
the following Agile principles:

Focus on Iterative and Experimentat


Self- Continuous
customer incremental ion and
organization improvement
value delivery adaptation

13
SCRUM

14
SCRUM
Scrum can be traced back to the work of
Hirotaka Takeuchi and Ikujiro Nonaka,
who in 1986 described a new holistic
approach in new commercial product
development efforts. They compare this
approach of a cross-functional team
collaborating to develop a new product
to rugby, where the whole team “tries to
go the distance as a unit, passing the ball
back and forth.”

15
SCRUM
Scrum, like other Agile methods, begins with a high-level scope definition and ballpark
time and cost estimates for the project. The scope and cost estimates should be
complete enough that management is comfortable with the estimates. The theory is
that since requirements evolve over time, detailed up-front planning will be wasted. In
place of a product WBS, Scrum uses product features as deliverables.

Features are prioritized by their perceived highest value. The project team tackles the
highest, feasible priority features first. Priorities are re-evaluated after each iteration.
Iterations are called sprints and should last no longer than four weeks. The goal of each
sprint is to produce fully functional features. This forces the team to tackle tough
decisions early in order to create a workable demo.

16
SCRUM
Scrum Development Process

17
LIMITATIONS OF AGILE

18
LIMITATIONS OF AGILE
• Agile PM does not satisfy top management’s need for budget, scope, and schedule
control.
• One cannot simply install it into an organization overnight; it needs to evolve over
time.
• Agile requires active customer involvement
• Agile PM frameworks, like Scrum, are used exclusively to complete software
development projects from beginning to end.

19
QUESTIONS?

20
THANK YOU!
See you on our next class

21

You might also like