0X. - Agile Project Management - OUT
0X. - Agile Project Management - OUT
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
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
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
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)
Source: thedigitalprojectmanager.com
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
R-EDUCATION
R-EDUCATION
Scrum Board