What is Agile? Minimalistic Introduction
Download as PPTX, PDF0 likes87 views
The document introduces agile methodology as a better approach to software development compared to traditional methods, highlighting its focus on collaboration and adaptability. It contrasts agile frameworks, specifically Scrum and Kanban, outlining their environments of suitability and key metrics. Additionally, it dispels common agile myths and encourages the adoption of agile practices within teams.
What is Agile? Minimalistic Introduction
- 1. What is Agile? Minimalistic introduction by Daria Trainor (@DariaTrainor)
- 2. A better way of building software
- 3. Why not traditional software management? Sequence of: -user requirements definition -system requirements definition -analysis and system design -system development -testing -delivery -maintenance • Comprehensive documentation does not meet business needs. • Hard to add changes mid- process (update documentation, update contract, rewrite, retest) • Little interaction with end user during the process • Strictly defined process kills creativity • Budget gets used upfront
- 4. Agile Manifesto • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiations • Responding to change over following plan
- 5. Agile myths False • Agile makes teams go faster • Agile = Scrum • Agile processes are lightweight True • Agile helps teams to adapt and deliver value • Scrum is one approach to agile • Agile is designed to drive collaboration
- 6. Scrum (iterative flow) Team • Scrum Master • Product Owner • Development team Metrics Velocity Events • Sprint • Sprint Planning • Daily Scrum • Backlog refinement • Sprint Review • Retrospective
- 9. Which environments is Scrum best suited for? • Well suited: • High amount of complexity • Aggressive deadlines • High level of risk • Not Well Suited • Priorities change often • Team composition changes regularly • Transparency is not encouraged
- 10. Kanban (continuous flow) • Visualise Workflow • Limit Work In Progress • Focus on flow • Continuously Improve
- 11. Which environments is Kanban best Suited for? • Well Suited: • Small teams • Frequent priority changes • Maintenance projects • Not Well Suited • No defined project management process • Diversity in sizes of tasks
- 12. Scrum vs. Kanban Scrum Kanban Rhythm Fixed sprints Continuous flow Release method At the end of the sprint Continuous delivery Roles Scrum Master, Product Owner, Development team No defined roles Key Metrics Velocity Cycle Time Change Strive to not make changes mid sprint Change can happen any time
- 13. • Introducing agile to teams https://app.pluralsight.com/library/courses/play-by-play-agile-teams- doc-norton-jeremy-jarrell • The Scrum Framework path https://app.pluralsight.com/paths/skills/the-scrum-framework • Kanban Fundamentals https://app.pluralsight.com/library/courses/kanban- fundamentals/table-of-contents • Scrum Master and Product Owner Certification