Agile overview
Download as PPTX, PDF1 like1,807 views
The document provides an overview of Agile methodology compared to the traditional Waterfall model. It discusses some of the pain points of Waterfall like frequent requirement changes and estimation inaccuracies. Agile is presented as an alternative that allows for more flexibility through short iterative sprints, prioritized backlogs, and responding quickly to changes. Specific Agile practices like Scrum, user stories, and daily stand-ups are explained. The document concludes with best practices in Agile and a call for questions.
Agile overview
- 2. Agenda • Introduction • Waterfall model • Agile Overview • Best Practices in Agile • Summary • Questions
- 3. About myself
- 4. Water fall model Requirement Analysis Design Implementation Deployment TimeDay 14 Day 28 Day 42 Day n
- 5. Pain Points • Frequent requirement change • Estimation inaccuracy • Too many documentation • Cascading effect in schedule impact
- 6. Agile model Requirement Analysis Design Implementation Deployment Requirement Analysis Design Implementation Deployment Requirement Analysis Design Implementation Deployment Requirement Analysis Design Implementation Deployment SPRINT nSPRINT 2 SPRINT 3SPRINT 1 TimeDay 14 Day 28 Day 42 Day n
- 7. Agile Overview • Agility - The power of moving quickly and easily • Fail early and recover soon • Wastage is minimum • Minimal documentation • Constant effort
- 8. Agile Manifesto Processes and tools Individuals and interactions Comprehensive documentation Working software Contract negotiation Customer collaboration Following a plan Responding to change
- 9. Waterfall vs Agile Fixed Scope / Features Resources Time Scope / FeaturesEstimated Resources Time Plan Driven Value Driven
- 10. What kind of project is Agile suited • Business is very Dynamic • High complexity • Uniqueness • Yield business value more quickly Months have turned into weeks. Weeks have turned into days. The world of IT is a fast-paced world and if a project is carried out too slowly, it is simply no longer relevant. - Author unknown
- 11. Slicing the cake GUI Layer Application Layer Business logic layer DB interface layer Database Layer
- 12. US 1 Slicing the cake (contd..) GUI Layer Application Layer Business logic layer DB interface layer Database Layer US # US 3 US 2
- 13. Types of Agile Methodologies Agile Methodologies Scrum Kanban Test-driven development Extreme Programming Feature Driven development
- 14. Scrum – How it works
- 15. WBS in SCRUM Epics Product backlog User stories High level task Low level task User stories High level task Low level task Product backlog User stories High level task Low level task User stories High level task Low level task
- 16. Scrum • A scrum team can consist of 7±2 Product Owner Scrum master Dev engineers Test engineers
- 17. Product Owner • Responsibilities – Write user stories – Prioritize them – Negotiate with the team and client Product Owner
- 18. Scrum Master • Servant - Leader • Not a SPOC • Need not be a dedicated resource • Facilitator Scrum master
- 19. Ceremonies in Scrum • Release planning • Sprint planning • Poker planning • Daily standup meeting • Retrospection • Product backlog grooming
- 20. Agile best practices • Test driven development • Short releases • Continuous Integration • Collective Ownership • Cross-team integration • Daily standup • Code Refactoring
- 21. Summary
- 22. What’s in for me • Adapt some of the best practices • Try Agile methodology to pursue in-house projects • Try to write user stories from requirements and break them into smaller tasks • Try the poker planning method for estimation
- 23. Known is a drop unknown is an ocean
- 24. Questions