Basics What is Agile? It’s a method based on iterative development. Why Agile? The goal is not to release things faster for the sake of it. It is to achieve nimbleness and agility to deliver on the company’s strategy as it moves forward and/or tactically changes.
It is about creating more business opportunities for ourselves rather than being cased into a model that requires our resource commitment for a time window that is longer than what the market we’re competing in requires.
The Agile Manifesto – a statement of values Process and tools Individuals and interactions Following a plan Responding to change Comprehensive documentation Working software Contract negotiation Customer collaboration over over over over Source: www.agilemanifesto.org
Iterative development process Product Backlog Product Backlog Product Backlog Product Backlog Sprint Backlog Sprint Backlog Sprint Backlog Sprint Backlog Sprint Backlog Sprint 1 Sprint 2 Sprint 3 Sprint 4 …. Sprint N Features Features Features Features Features Features Features Features Features Features Features Features Features Features Features Features
Agility via Prioritized Backlog
Scrum Framework Daily Scrum Meeting S P R I N T 24 hours Backlog tasks expanded by team Potentially Shippable Product Increment 8 10 days Sprint Backlog Product Backlog As prioritized by Product Owner Product is designed, coded, tested and documented during the sprint.
Ceremonies Scrum Framework Roles Artifacts
Burn down charts
The Scrum Framework - Roles Ceremonies Roles
Daily scrum meeting
Scrum Roles Management: Strategy & Vision Allocate resources Address escalated issues Product Owner: Defines and prioritize features Sets the DONE criteria Scrum Team: Cross functional Commitsto what it can do Manages itself and its work Gives a demo of their work Scrum Master: Ensures team is fully functional Is not a project manager Removes impediments
Who does what?
The chicken and the pig
The Scrum Framework - Ceremonies Roles Artifacts Ceremonies
Sprint Planning – not the meeting meeting Product Backlog Team Capabilities Business Conditions Technology Current Product Product Owner Scrum Team Management Customers Sprint Planning Meeting Sprint Goal Sprint Backlog We should use 5% of our sprint time on this. At most workplaces, 10% of the sprint is time boxed for this meeting.
Sprint Planning board
Sprint Tasks in General
Daily Scrum – Minutes of Meeting
Say it right
Sprint review meeting
Sprint review meeting tasks
Sprint velocity After 3 to 5 sprints, velocity can be used to estimate completion dates.
Burn down Chart Perfect scrum, No one home, Overestimation and Underestimation
Again, why daily? How does a project get to be a year late? One day at a time Can Scrum meetings be replaced by emailed status reports? No Entire team sees the whole picture every day Create peer pressure to do what you say you’ll do
Scrum of Scrums / Meta-Scrum Scrum Master Product Owner Scrum team member
How do I propose Agile in my organization
Basic truth about People
Basic truth about performance
Good reads Agile and Iterative Development: A Manager’s Guide by Craig Larman Agile Estimating and Planning by Mike Cohn Agile Project Management with Scrum by Ken Schwaber Agile Retrospectives by Esther Derby and Diana Larsen Agile Software Development Ecosystems by Jim Highsmith Agile Software Development with Scrum by Ken Schwaber and Mike Beedle Scrum and The Enterprise by Ken Schwaber User Stories Applied for Agile Software Development by Mike Cohn Lots of weekly articles at www.scrumalliance.org BUY BOOKS ONLINE at the AGILE FOR ENTERPRISE ORGANIZATIONS web store (http://astore.amazon.com/agilescrumsoftwaredevelopment-20)
Catch me if you can email@example.com www.gPod.in