Agile values
Download as PPT, PDF0 likes48 views
The document discusses Agile methodology and Scrum framework. It defines key Scrum roles like Product Owner, Team, and Scrum Master. It also covers Scrum principles like working in sprints, prioritizing business value, and continuous improvement. The document emphasizes that Agile requires commitment, effective communication, and ability to deliver working software frequently in short iterations to gain customer feedback. It provides steps to get started with Scrum including defining sprint cycles, slicing work into discreet deliverables, holding daily standups and retrospectives.
Agile values
- 1. Agile How Agile works (Scrum method) Principles How to Adopt Agile
- 2. The Agile Manifesto A Statement of Values http://agilemanifesto.org Individuals and interactions over Working software Customer Collaboration Responding to change over over over Process and tools Comprehensive documentation Contract negotiation Following a plan
- 3. Scrum in a Nutshell
- 4. Scrum Roles • Product Owner • Product Vision • Supplies the $$ • Owns the Backlog • Team • Builds the features • Scrum Master • Remove obstacles • Coaches/Enforces Scrum • Sprint Safety
- 5. Scrum Principles • Team Based • Quality is not negotiable • Sustainable Pace • Business Value Driven
- 6. Scrum is Hard • Requires a responsive organization • Active team members • Disciplined adherence to Definition of Done • Continuous improvement • Effective (not efficient)
- 7. Scrum is Hard • Commitment and Accountability to team • Ability to ‘slice’ product into small features • Take the user’s perspective • Prioritize work based on value • Managers are supporters
- 8. Communication! • Communication is NOT overhead • Inclusive (over-communicates) • Effective meetings (have objectives, agendas) • Removes go-betweens • Ensures business involvement (partner model)
- 9. Do we need Agile? • Customer Satisfaction – Good End Product (No Quick and Dirty) – Reasonable Cost – Customer Trust • Team Satisfaction – Engagement – Synergy • Predictability
- 10. How to Get Started 1. Define a Sprint cycle duration (<30 days) 2. Sushi – Define discreet deliverables (ideally releasable) 3. Add deliverables QA or review tasks 4. Hold Retrospectives (after each sprint) 5. Add Daily Scrums 6. Hold Sprint Reviews (demo deliverables) 7. Find a Product Owner and a Scrum Master
Editor's Notes
- #6: Team based: Cross Functional, Measured as a team, Self-Organized Quality is not negotiable: No corner cutting to meet deadlines Sustainable pace: Overtime = bad planning, no commitment games Business value driven: Makes sense for the customer