Presentation that shows "What is Agile Project Management" and compares Agile to traditional project management methods. Also describes the key benefits that Agile can provide, common errors with Agile and what it uses at its core to deliver projects in a less risky way.

1. What is Agile Project
Management?
This presentation will show you
the main differences between
Agile and traditional project
management

2. © PMIS Consulting Limited: all rights reserved
Traditional Project Management:
pmis-consulting.com
Define the
Project &
Requirements
Plan the
Project
Design &
Develop
Users test and
accept the
deliverable.
Implementation
and Close out

3. © PMIS Consulting Limited: all rights reserved
Traditional PM
• Try’s to define all requirements
up front
• Hands all those requirements to
developers
• Developers then produce their
interpretation of those same
requirements
• End-product is given back to end
users, big-bang style
• Everyone hopes the product
meets the need !
What Agile tries to do:
• Deliver the whole project in multiple
discrete increments
• Define detailed requirements in an
evolving way, per increment
• Deliver shippable Product to end
Users, per increment
• Take feedback from key users and
customers, per increment
• Therefore
– De-risk the project, via early feedback
on the interpretation of requirements
and fitness-for-purpose of product per
increment.
Traditional –v – Agile Projects:

4. © PMIS Consulting Limited: all rights reserved
So what is Agile?
pmis-consulting.com
Agile was
developed by a
group of Software
Developers.
Agile is not a
method; but can be
combined with
methods, e.g.
Scrum.
Agile uses a single
‘team’ including
users and
developers.
Agile relies on
frequent, face-to-
face
communication.
Agile delivers
increments of
working software
usually sequentially.

5. © PMIS Consulting Limited: all rights reserved
So how should Agile work?
pmis-consulting.com
Most common
method is
Scrum/ Sprints.
Priorities &
Product Backlog
drive sprint
planning.
The Business
picks the ‘user’
items in the
Sprint
Each Sprint is
managed using
daily
communication.
Delivery of
Sprints enables
new releases.

6. © PMIS Consulting Limited: all rights reserved
Key Attributers of an Agile Project:
pmis-consulting.com
Sprints are
sequential –
totally sequential.
Sprints finish with
‘shippable’
product’ - tested
etc.
All team members
work on the Sprint
at hand until it’s
done
Then you define
and plan the next
Sprint.
If you can’t meet
all the above, you
may not be able
to adopt Agile.

7. © PMIS Consulting Limited: all rights reserved
Is Agile Easy to do?:
pmis-consulting.com
In principle, yes,
in practice, not
always.
It requires,
careful planning
per iteration.
It requires the
right people be
available to do
that.
It requires
commitment.
It needs to be
understood, and
improved until it
works for you.

8. © PMIS Consulting Limited: all rights reserved
Common mistakes using Agile:
pmis-consulting.com
‘projects start
with the Product
Backlog’.
Agile projects
don’t need to
plan.
Agile projects
don’t need
Project
management
No-one should
be accountable
on an Agile
project.
Agile projects
don’t need
things like
budgets, risk etc.

9. © PMIS Consulting Limited: all rights reserved
Types of Projects will Agile work on?
pmis-consulting.com
Product can be
delivered and
accepted in
increments.
Requirements
are tough to
define at the
start.
Where technical
complexity is
manageable to
low.
Where face-to-
face
communication is
freely available.
Where there is
commitment to
the approach by
all .

10. © PMIS Consulting Limited: all rights reserved
Click for more info’ on Agile
Article
Online
Training
Consulting Blog
Classroom
Training