A while ago I was running a session on the basics of Agile and Lean, which I largely based on my two bibles on the subject, Learning Agile and Lean UX: designing great products with Agile teams. This is a summary:
The basics:
- Agile was created to improve the way we develop software
- Traditionally, organisations use less effective ‘Waterfall’ methods
- Much of the challenge with adopting Agile is changing mindsets, as well as practices
The Agile manifesto:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
Agile practices:
- Daily standups
- User stories
- Backlogs
- Sprints
- Burndown charts
- UAT
- Retrospection
- Iteration
The composition of a team:
- Scrum master
- Product owner
- Team
Lean UX:
- Eliminate waste
- Test persona assumptions
- Test needs assumptions
- Rapid prototyping (paper, static, interactive)
- MVP
- Test and learn
