0% found this document useful (0 votes)
82 views13 pages

0X. - Agile Project Management - OUT

The document discusses key differences between agile and traditional waterfall project management approaches. It states that agility is more about mindset than practices, focusing on collaboration, adaptation to change, and working software over documentation and strict plans. It provides tips for deciding between agile and waterfall based on a project's requirements, budget, risks and timelines. The document also outlines principles of the agile manifesto and compares characteristics of traditional vs agile teams.

Uploaded by

Nanang Zarma
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
82 views13 pages

0X. - Agile Project Management - OUT

The document discusses key differences between agile and traditional waterfall project management approaches. It states that agility is more about mindset than practices, focusing on collaboration, adaptation to change, and working software over documentation and strict plans. It provides tips for deciding between agile and waterfall based on a project's requirements, budget, risks and timelines. The document also outlines principles of the agile manifesto and compares characteristics of traditional vs agile teams.

Uploaded by

Nanang Zarma
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13

R-EDUCATION

“Agility is principally about


mindset, not practices.”
Agile Project Management

- Jim Highsmith, Agile Project Management: Creating Innovative Products-

R-EDUCATION
R-EDUCATION
Changes Oriented Carefully Oriented
Product Mindset Project Mindset
Iteration, all processes Fixed and Separated Staged
Short Feedback Loop No Feedback Until Testing
Unit Testing End Product Testing
Unclear Requirement Fixed Requirement
Minimal Paperwork Extensive Documentation
Collaboration Team Works in Turns
Full Transparency Lack Transparency
Easy to Incorporate Changes Difficult to Enable Changes
Support Changing Requirement End Product is Defined

Agile Project Management 2


R-EDUCATION
R-EDUCATION
How to decide Between Agile and Waterfall

1. When your project has strict regulatory requirements and many initial product requirements Waterfall
2. If your project has few initial requirements and doesn't need to meet strict regulations Agile
3. If you're in an organization that has strict processes that you must adhere to Waterfall
4. If your organization doesn't have strict processes to follow & you can work flexibly Agile
5. When you are working on projects with budget constraints, period, and fixed scope Waterfall
6. When you are working on projects with high interdependencies and risks Waterfall
7. When you are working on projects with unclear requirements and project deliverables Agile
8. If your team is delivering an enhancement to an existing legacy product Waterfall
9. If your team is trying to build something innovative that does not exist in any form today Agile
10. When you have fixed and firm timeline Waterfall
11. If you need to get the project delivered in a short amount of time Agile
12. If the project budget is fixed and can not be increased Waterfall

Agile Project Management 3


R-EDUCATION
R-EDUCATION
The Agile Manifesto and Mindset

We are uncovering better ways of developing


software by doing it and helping others do it.
Through this work we have come to value:

Individuals and interactions over processes and tools


Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.

Agile Project Management 4


R-EDUCATION
R-EDUCATION
Traditional Teams vs Agile Teams

Traditional Teams Agile Teams

Traditional teams follows a top-down approach 01 Agile teams are self-organized and self-managed

Possible bottlenecks in the product release cycle due to Agile teams are cross-functional, interdisciplinary, and
multiple component teams 02 complete tasks without external dependencies

Organization evaluates individual performance 03 Organization evaluates team performance

There are distinct job roles, title, and importance is given Agile teams are cross-functional, and skills matter more
to hierarchy 04 than titles

Traditional teams are not of fixed size 05 Agile teams are usually small (3 to 9 persons)

Agile Project Management 5


R-EDUCATION
R-EDUCATION
When to Use Agile or Waterfall

Simple = easily knowable.


Complicated = not simple, but still knowable.
Complex = not fully knowable, but reasonably predictable.
Chaotic = neither knowable nor predictable.

Adapted Stacey Matrix for technology / software development environment

Agile Project Management 6


R-EDUCATION
R-EDUCATION
“Agility is principally about mindset, not
practices.”
- Jim Highsmith, Agile Project Management: Creating Innovative Products-

Agile Project Management 7


R-EDUCATION
R-EDUCATION
Agile approaches, frameworks and methods

Source: thedigitalprojectmanager.com

Agile Project Management 8


R-EDUCATION
R-EDUCATION
SCRUM Framework at a glance

Scrum Master
Daily Scrum
Meeting
24H

Product Owner
Development
Team Sprint
Ranked list of Sprint Review
what is Sprint
(1-4 Week)
required: Planning Sprint Retrospective
feature, etc Meeting

Product Backlog Sprint Backlog Increment

R-EDUCATION
R-EDUCATION
Scrum Board

Agile Project Management 10


R-EDUCATION
R-EDUCATION
How is EPC Project?

Agile Project Management 11


R-EDUCATION
R-EDUCATION
Source: www.codetiburon.com

Agile Project Management 12


R-EDUCATION
R-EDUCATION
Thank You

Agile Project Management 13


R-EDUCATION

You might also like