- Agile is about flexibility and removing friction
- In agile, there’s an assumption that scope will change in one direction or another depending on feedback
- There are no deadlines or estimates
- You aren’t working in terms of time
- You work constantly putting valuable software in the hands of users and getting their feedback
- Agile is based on trusting the people doing the work — they don’t need management or permission because they are trusted
- Agile is a culture based on the core principles
- The culture is more important than anything, and the principles are more important than the practices
- The practices boil down to talking to customers to find out what they need, then break off a small piece of that and give that to them
- Up-front requirements gathering doesn’t work because the requirements you gather are never correct
- If documentation isn’t going to be read, don’t bother writing it
- Collaborate with users, don’t negotiate with them
- A highly-functional agile team no longer needs retros because they huddle whenever necessary and change what’s not working about the process and move on
- An agile team’s role is to serve the needs of the business and its users
- Requirements will change, so any process that resists that won’t work
Original video by DevWeek Events:
Keynote presentation from Software Architect 2014
http://software-architect.co.uk/