Agile vs traditional project management overview

Agile vs traditional project management

1. Agile vs. Traditional Project Management
Created by: Saqib Javed John (PMP, ACP, ITIL, SCJP, SCWCD)
Traditional Project Management
Agile Project Management

2. Difference between Agile and Traditional
Project Management
Cookbook Innovation
Waterfall Agile
Structured
Adaptability

3. More Rigid and Directions coming Top
to Down
Team may conduct dozens of
experiments to see which works best
More Commanding and Controlling
style of Leadership
Communication flowing freely
between all the team members
Spoon Feeding; Management tell
everyone “What to Do”
Self-Organizing; work is distributed
with consensus by the Team itself
Planning Centric and Plan Driven
Plan could be very fluid in Agile world
as Agile projects are more fluid then
waterfall projects
Document Oriented and Document
Driven
Cross functional, Self-Contained
and Agile is ultimately pragmatic
Resistant to Change
Agile Projects are welcoming to
change; true even changes are
introduced late in the project
Traditional Framework Agile Framework

4. Customer get involved early in the
processes but tended to keep at arm’s
length once the project begins
Customer involvement is the key here
as more closely involved at the time of
work being performed
Escalation to managers when problem
arise
When problems occur, team works
together resolve them internally
Heavy upfront analysis and design
Daily stand-up meetings are held to
discuss work done yesterday, plan of
today and impediments if any
More serious about processes than
the product
Agile methods less focus on formal
and directive processes
Product is planned extensively and
then executed and tested
Work is delivered to client in small and
frequent releases to get rapid
feedback loops
Traditional models favors
“Anticipation”
Agile model favors “Adaption”
Traditional Framework Agile Framework

5. Team Commits so early in the project
before they can put their hands on
Daily Stand-Up meetings are held to
discuss work done yesterday, plan of
today and impediments if any
Heavy documentation before
executing the work packages
Agile Projects are highly democratic
and implement a series of short and
repeatable practices
Slow and structured development
process usually focus on one time
release
Agile is built on the concept of
frequent and small releases known as
“Incremental Delivery” in small chunks
More focus on How than Why
Agile more focus on Why and
retrospective is held at the end of
each Iteration or Release
Ownership belongs only to the Project
Manager
Shared ownership
Traditional Framework Agile Framework

6. oTraditional
oPredictive
oUnplanned
oUndisciplined
oInefficient
oWild
oAdhoc
oChaotic
oProcedure based
oPizza box methodology
oBlack and White proposition
oJust a development
methodology
oDepartmentalized
oPerspective by design
oAnalysis up front
oDesign up front
What Agile is Notor hasn’t

7. oMindset, Philosophy, Culture,
Lifestyle, Approach and
Thinking
oUnique Project Management
oIterative & Incremental
Framework
oVisionary, Evolutionary and
Adaptive
oWhere everybody understand
the vision
oEfficient and Effective
oBusiness Focused
oDelivery Focused
oCustomer Value Focused
oFaster
oBetter
oReliable
oCooler
oCollaborative
What Agile isor has

8. oInnovation
oSelf-Managing
oSelf-Organizing
oSelf-Contained
oSelf-Commitment
oMore Feedback Oriented
oMore Satisfaction
oMore Customer Involvement
oLess confusion
oMore Visible and
Transparent
oImproved Time-to-Market
oLess emphasis on designing
and documentation
oDecreased Risk
oBusiness-Driven
oMission-Drive
oFeature-Driven
What Agile isor has

9. oConsensus-Driven
oTest-Driven
oQuality-Driven
oValue-Driven
oFour Eye Technique
oBuild-In Quality
oCombined ownership
oShared ownership
oFreedom to move
oPragmatic
oContinuous user involvement
oRapid Feedback Loops
oShort feedback loops
oPlanning based on High-
level business view point
What Agile isor has

10. oJust Enough Project
Management
oHas focus of project
Requirements only (Build
only what asked for)
oProject Specific (don’t build
more than the Bare-Minimum
or Bare Sufficient )
oLight weight
oTime boxed
oResponsive to Business
oBecome main-stream
oIs an approach which can be
applied on Waterfall
What Agile isor has

11. Created by:
Saqib Javed John
MSc CS, PMP, ACP, ITIL v3F, SCJP, SCWCD
Email: [email protected]
Skype: saqibjohn76
LinkedIn: pk.linkedin.com/pub/saqib-javed-john/b/125/1b1
Thanks….