Manage Complexity With Agility

Software development is complex business. In order to deal with this complexity, agile practices have been developed to break development into manageable cycles of development called iterations. We examine the use of user stories to gather requirements. We examine ways to automate our build and deployment process in order to produce more frequent releases. Finally we look at ways to implement each of these practices in existing projects.

Transcript

1. Manage Complexity With Agility Alan Stevens
2. Contact Me Email/IM: alanstevens@gmail.com Blog: http://halanstevens.com Twitter: @alanstevens
3. The Straw Man
4. Software is Complex
5. You Are Already Succeeding
6. Pomposity
7. Use What Works (For You)
8. Avoid Dogma
9. It’s a process It takes Time
11. Release Regularly (Every two to four weeks)
12. Release: Even Internally
13. Constant Velocity “Heroism is Failure” H. Alan Stevens
14. Short Horizons
15. Frequent Course Corrections
17. User Goals Not Technical Requirements
18. Reminder of a Future Conversation
19. SWAG Sophisticated Wild Ass Arbitrary Guess
20. User Story Template As a: (Role) I want: (Something) So that: (Benefit)
21. Documented in Acceptance Tests
22. Avoid BDUF (Big Design Up Front)
23. The Last Responsible Moment
25. Do the simplest thing that could possibly work
26. YAGNI You Ain’t Gonna’ Need It!
27. Loose Coupling
28. High Cohesion & Low Coupling
29. Law of Demeter A class should only communicate with its immediate neighbors
30. Manage Technical Debt
31. I thought that rushing software out the door to get some experience with it was a good idea, but that of course, you would eventually go back and as you learned things about that software you would repay that loan by refactoring the program to reflect your experience as you acquired it. Ward Cunningham “Ward Explains Debt Metaphor” http://c2.com/cgi/wiki?WardExplainsDebtMetaphor
33. Code Smells a hint that something might be wrong
34. Follow the “Boy Scout Principle”
35. Enable Change
36. Common Refactorings Rename Class Extract Variable Extract Method Extract Class
38. DRY Don’t Repeat Yourself
39. See it once: do it See it twice: notice it See it a third time: Automate It! The Rule of Three
40. Optimize Bottlenecks
41. Reduce Friction
42. Enable Flow
43. Reduce Ceremony
44. Automate the BFDs (Big Friggin’ Deals)
46. As applications mature, they should become more maintainable, not less.
47. Continuous Improvement
48. “With every mistake, I must surely be learning” George Harrison
49. Work on your process, not just in your process
50. Value Developer Cycles Over CPU Cycles
51. Eliminate Waste
52. Prevention is the best cure
53. Avoid Complacency
54. LEAN
57. Thanks For Listening! Email/IM: alanstevens@gmail.com Blog: http://halanstevens.com Twitter: @alanstevens