PMPs vs Agile Project Managers: Clash of the Titans
1. PMP vs Agile
Project
Managers:
Clash of the
Titans
Juan Banda, MSc, CSP, ACP, PMP
juan.banda@percella.com
Fotografía por http://japan-web-magazine.com/japan-sumo/japan-sumo0.html
2. The contenders
are part of the
same team,
they have
similar
objectives but
different
visions of how
to achieve
Fotografía por http://en.wikipedia.org/wiki/File:Sumo_ceremony.jpg
them
3. One
competitor
whish to
always impose
his will –
typical of
projectalized
organizations
Fotografía por http://www.metro.co.uk/news/52596-kids-take-on-sumo-wrestlers
4. Each side is
looking for the
ultimate
weapon to
defeat the
other – Could
Agile be this
weapon?
Fotografía por http://uncyclopedia.wikia.com/wiki/File:Sumo_wrestling.jpg
5. There is no small
adversary, only
small mind – but is
there really a fight?
Fotografía por http://amusis.wordpress.com/2010/05/19/
6. Dress for battle –
each side only have
“frameworks” but
not “silver bullets
Fotografía por http://funsolutions.com.au/1_10_Sumo-Suits.html
7. •Project Managers
can wear different
hats, but the
objective is always
having successful
projects
•The “framework”
is just the vehicle
Fotografía por Carlos Castillo
8. •Teams transform to
“Agile”
•With luck organizations
can also transform
•Transforming
organizations is a more
ambitious goal, we talk
here about Enterprise
Agile
Fotografía por babka_babka
9. •“Being” Agile vs
“using” Agile
•“Transforming” to
Agile vs “adopting”
Agile
•PMPs think in
“adopting” Agile
because they think this
is just about new
processes
Fotografía por Darko Sikman Photography
10. •A traditional PMO
can help to keep
the “Agile bubble”
•Inside the bubble
Agile can flourish
and eventually
infect other teams
in the organization
Fotografía por http://good-wallpapers.com/cartoons/1049
11. •One risk thought
is that the PMO
tries to “clone”
Agile
•Agile is a mindset,
not easily
achievable and
hard to be
replicated
Fotografía por http://scienceonthego.blogspot.com/2010/12/human-
cloning-make-new-human-without.html
12. •“Rolling wave” and
“Progressive
elaboration” are
planning techniques, not
principles and values
•They sound link Agile
but Agile is much deeper
•Agile does not define
“how” should I work, it
defines principles and
values
Fotografía porSundust_L
13. •The Agile teams enter
into a “trance” state of
the mind as a result of
their transformation to
Agile
•This “trance”
disconnect them from
many mundane details
Fotografía por useitinfo
14. •It is possible to find a
right balance though,
but for that we’ll need
“adapters”
•These “adapter” are
people (Project
Managers) no
processes that help to
keep the “trance”
Fotografía por Maxin Kuschpel
15. -¿Can the Scrum
Master be this
adapter?
-No, because as
part of the team
his is also in
“trance”
Fotografía por mattek
16. •¿Can the
Product Owner
be the
adapter?
•No, because
he focuses on
the product
and doesn’t
have time for
mundane
Fotografía por Digital Stability things
17. •We need
somebody that
take care of
contracts,
evaluations,
procurement,
hiring, budgets,
and other facets
of a project
Fotografía por traqair57
18. •Project
Managers
should be
always
pragmatical
•“Use
everything that
works”
•“Do not repeat
the same attack
Fotografía por naeemcallaway plan”
19. •”Fight with one
sword in each
hand. Do not
stick to a single
fighting style”
•PMPs do not
need to
“transform”,
they need to
“adapt”
Fotografía por fifoescudero
20. •¿As a PMP do I
rather join to
the “flower
power”
movement or I
stay outside?
•Better to stay
outside because
somebody
needs to take
care of the
money
Fotografía por Aleeph
21. •Being outside
means keeping an
“objective” vision
that helps to
interface with the
rest of the
organization
•Do not force the
team to share this
vision
Fotografía por pasukaru76
22. •If I’m a PMP, do I
need to become
an Agile Project
Manager to keep
me competitive?
•If I’m an Scrum
Master and I want
a promotion, do I
become an Agile
Project Manager?
Fotografía por Logan Fulford
23. •As a PMP just
by switch titles
I won’t be
more
competitive
•PMPs are not
a thing from
the past, their
skills will
always be
required
Fotografía por abc photography01
24. •It is required
though that
PMPs adapt
to Agile
(adapt means
becoming
and
“adapter”)
Fotografía por JPLAGES
25. •As an Scrum Master
supposedly I don’t
believe in hierarchies
but in roles
•Being an Agile Project
Manager means being
a manager that
manages -with an
Agile style- Agile
teams inside and
organization that can
or can not be Agile
Fotografía por Begga_H
26. Initiation, Planning, Executing,
Monitoring & Controlling, Closing
Project, Release, Iteration, Daily
Work
The process groups can be
executed in each level
Fotografía por photophilde
27. •I = Business case
•P = Kickoff
meeting, release
road map planning
•E = Iterative and
incremental
deliverables
•M&C = Periodic
reviews of the
deliverables, progr
ess and process
•C = Project
retrospective
Fotografía por torbenbotts
28. •I = Road map and
release definition
•P = Release
planning meeting
•E = Iterative and
incremental
deliverables
•M&C = Periodic
reviews of the
deliverables,
progress and
process
•C = Release
retrospective
Fotografía por dpicton
29. •I = Iteration
planning meeting
•P = Iteration
planning meeting
•E = Work in features
until completing
them
•M&C = Tasks
boards, burndown
charts, daily stand-
ups, accepting
completed features
•C = Iteration demo,
review and
Fotografía por Praveen M Tomy retrospective
30. •I = Morning
coffee
•P = Daily stand-
up meeting
•E = Work on tasks
•M&C = Remove
impediments
•C = Update the
taskboard and the
burndown chart
Fotografía por deathtiny42
31. Agility is the
right balance
between
flexibility and
stability
(Highsmith
2002)
Fotografía por http://lisadelay.com/blog/2011/01/02/ha-poetry-in-motion-sumo-style/