Agile 101

A presentation given to new recruits or clients to describe the basics of agile software development

Transcript

1. Agile 101
2. Kanban Scrum XP Lean Sprints Iterative DSDM Timebox
3. Why agile?
4. Traditional   methods   aren’t  good     enough
8. ‘Big  Design  Up  Front’:   based  on  three     main  assumptions
9. The  customer  knows   what  they  want We  know  how  to  build  it Nothing  will  change   along  the  way
10. The Agile Manifesto
11. Individuals     and  Interactions   Processes   and  Tools   Working  Software Comprehensive   Documentation Customer   Collaboration Contract   Negotiation   Responding   to  Change Following     a  Plan over over over over www.agilemanifesto.org
12. Twelve  Principles  of  Agile  Development 1.  Early  &  Continuous  Delivery   2.  Embrace  Change   3.  Frequent  Delivery  on  Short  Timescales   4.  Business  &  Developer  Collaboration   5.  Empower  the  Team   6.  Face  to  Face  Communication  is  Best www.agilemanifesto.org/principles.html
13. Twelve  Principles  of  Agile  Development 7.  Progress  Measured  by  Working  Software   8.  Maintain  a  Sustainable  Pace   9.  Technical  Excellence   10.  Simplicity  is  Essential   11.  Teams  Self-­‐Organise   12.  Inspect  &  Adapt www.agilemanifesto.org/principles.html
19. The  three  main   assumptions  change
20. The  customer  discovers   what  they  want We  discover  how  to  build  it We  will  embrace  change   along  the  way
21. “But  we  already  know     what  they  want”
22. What  about   unused  features?
23. 7% 13% 16% 19% 45% Never Seldom Some`mes Oaen Always Standish  Group  CHAOS  Report  2002 Actual  Use  of  Requested  Features
24. “But  are  agile   projects  actually   more  successful?”
25. Agile 9% 49% 42% Successful Challenged Failed Standish  Group  CHAOS  Manifesto  2012 Waterfall 29% 57% 14%
26. “Isn’t  it  just  some   new  fad?”
27. Many  of  our  projects  are   using  it  and  many  in   industry  have  been  using   it  since  even  before   2001’s  Agile  Manifesto
28. Scrum
29. Manage  complexity,   uncertainty  and   change  through   visibility,  inspection   and  adaptation
30. Divide  product   into  features
31. Prioritise   for  highest  value $$$ $
32. Divide  schedule   into  iterations January May 1 2 3 4 5 6 7 8 Sprint
33. Do  these     ones  first
34. Deliver   incrementally January May Working   Software
35. Product   Owner
36. Scrum
 Master
37. The   Team
38. Structure  of  Scrum
39. Kanban
40. A  method  for   evolutionary   process  change
41. Start  with  what  you  do  now   Agree  to  pursue  evolutionary  change   Respect  current  responsibilities  &  titles   Encourage  leadership  at  all  levels 4  Principles
42. Visualise  Workflow   Limit  Work-­‐in-­‐Progress   Manage  &  Measure  Flow   Make  Policies  Explicit   Implement  Feedback  Loops   Collaborate  &  Evolve  Using  Models 6  Practices
43. Design Dev Test Deploy Start  With  Current  Process
44. Design Dev Test Deploy E D C B A F G Visualise  Workflow
45. Design Dev Test Deploy E D C B A F G Ready In  Progress Ready In  Progress (Max  2) (Max  1) Limit  WIP
46. Design Dev Test Deploy E D C B A F G Ready In  Progress Ready In  Progress (Max  2) (Max  1) Identify  Bottlenecks
47. A  process  of   ongoing   improvement,  not   software   development
48. Design Dev Test Deploy G D E A F B C Often  used  with  Scrum
49. Application Phone Interview Contract Gerard Dave Emma Alice Fiona Ben Claire Can  even  be  used  for  recruiting
50. Myths
51. Agile  is   undisciplined  and   unpredictable
52. Agile  is  only  for   software   development
53. Agile  is  always   cheaper
54. Agile  doesn’t  scale
55. Remember     principles   not  processes