Software development is hard

1,645 views

Published on

The latest version of this primer that I sometimes present to groups.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,645
On SlideShare
0
From Embeds
0
Number of Embeds
1,151
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Software development is hard

  1. 1. software development ha rd is A primer on why agile and lean can help.http://www.flickr.com/photos/bobjagendorf/2219031438/ 1
  2. 2. Me• Involved in development of digital applications and platforms since 1997• Australia and the UK• Floppy disks, CD-ROMs!• Then Intranet sites, websites, web applications.• Now. Lean and agile coach & trainer• Organiser of LAST Conference• projectslittlehelper.com 2
  3. 3. Me• Involved in development of digital applications and platforms since 1997• Australia and the UK• Floppy disks, CD-ROMs!• Then Intranet sites, websites, web applications.• Now. Lean and agile coach & trainer• Organiser of LAST Conference• projectslittlehelper.com• Super Power - Sleeping 2
  4. 4. 3
  5. 5. Does any of this sound familiar? 4
  6. 6. Does any of this sound familiar? “We need to add all these essential features...but it still has to come out on the same date.” 5
  7. 7. Does any of this sound familiar? “Sorry, we forgot to tell you that we wanted these changes” 6
  8. 8. Does any of this sound familiar? “I know I said I wanted that functionality…but now that I see it…” 7
  9. 9. Does any of this sound familiar? “Did you read the documentation?” “Of course I did… …well some of it. …actually only the intro.” 8
  10. 10. It can start to feel a bit…Dilbert http://www.flickr.com/photos/smallbox/174532376/ 9
  11. 11. A classic approach... Some call it… Big Design Up Front 10
  12. 12. A classic approach... Detailed planning using up-front documentation. 11
  13. 13. A classic approach...Detailed estimates of every step inthe development. 12
  14. 14. A classic approach... Eventually... Build the software 13
  15. 15. A classic approach... Handover to QA Sign off 14
  16. 16. A classic approach... Maybe a “Lessons Learned” meeting. AKA Post Implementation Review. 15
  17. 17. A classic approach...Strict change controls To make sure what was specified is what is built. 16
  18. 18. Strengths? 17
  19. 19. Strengths? Appears logical, at first. 17
  20. 20. Strengths? Appears logical, at first. Can be good for stable projects, with low technical risk 17
  21. 21. Strengths? Appears logical, at first. Can be good for stable projects, with low technical risk …ones that don’t change much 17
  22. 22. Strengths? Appears logical, at first. Can be good for stable projects, with low technical risk …ones that don’t change much …or ones where you predict 100% of tasks up front 17
  23. 23. Problematic? 18
  24. 24. Problematic? Weighted towards good ideas coming at the start 18
  25. 25. Problematic? Weighted towards good ideas coming at the start Writing things down…can equal “Throwing it over the wall” 18
  26. 26. Problematic? Weighted towards good ideas coming at the start Writing things down…can equal “Throwing it over the wall” Many features end up not being used. 18
  27. 27. Problematic? Weighted towards good ideas coming at the start Writing things down…can equal “Throwing it over the wall” Many features end up not being used. A prescribed process cannot always fit every project 18
  28. 28. Change is a problem, not an opportunity 19
  29. 29. Change is a problem, not an opportunity The thing is… 19
  30. 30. The thing is…Change is inevitable 20
  31. 31. What can we doabout it?? 21
  32. 32. Weapons to add to our armoury User driven product design Prioritise functionality Close & frequent collaboration with representatives of customer value 22
  33. 33. Weapons to add to our armoury Constantly ask “Is this what the user values?” Continuous integration, automated testing and other engineering practices. Regularly inspect process and adjust accordingly 23
  34. 34. Benefits 24
  35. 35. Benefits Sustainable pace 24
  36. 36. Benefits Sustainable pace Self organising teams 24
  37. 37. Benefits Sustainable pace Self organising teams Ability to embrace change 24
  38. 38. Benefits Sustainable pace Self organising teams Ability to embrace change= happier teams 24
  39. 39. Benefits Sustainable pace Self organising teams Ability to embrace change= happier teams The product is what the user wants (it makes money/ creates value) 24
  40. 40. Benefits All the kittens are happy 25 http://www.flickr.com/photos/masochismtango/514736937
  41. 41. Agile and Lean These are techniques to help make kittens happy Perhaps different to things that you might be have done before… …but you may have been doing a lot of this already! 26
  42. 42. “You are not alone” Suncorp Nokia The Economist The Financial Times Google REA Telstra Yahoo! Seek and a whole lot more 27
  43. 43. Where to start? Retrospectives Automated testingExtreme Programming Daily standup Unit testing Card walls ScrumBurndown Charts Sprints IterationsValue Stream Mapping Story points DSDM UX Kanban VelocityContinuous integration User Stories 28
  44. 44. Where to start? Retrospectives Automated testingExtreme Programming Daily standup Unit testing Card walls Scrum Confused?Burndown Charts Sprints IterationsValue Stream Mapping Story points DSDM UX Kanban VelocityContinuous integration User Stories 28
  45. 45. A bit of readingThe Scrum Primer:http://www.scrumprimer.com/InfoQhttp://www.infoq.com/Jim Highsmith“Agile Project Management”PMI, PRINCE 2 Foundation, IIBALeading Answershttp://leadinganswers.typepad.com/ 29
  46. 46. A bit of readingThe Scrum Primer:http://www.scrumprimer.com/InfoQhttp://www.infoq.com/Jim Highsmith“Agile Project Management”PMI, PRINCE 2 Foundation, IIBALeading Answershttp://leadinganswers.typepad.com/ 29
  47. 47. Group therapyMelbourne Agile and Scrum User GroupMelbourne Limited WIP Society (Leanand Kanban)Agile Business Analystshttp://meetup.com 30
  48. 48. http://www.flickr.com/photos/avardwoolaver/7137096221/http://projectslittlehelper.comed@projectslittlehelper.com @littlehelperCreative Commons photos fromFlickr.Hand drawn icons:http://handdrawing.olawolska.com 31This presentation can be reused under a Creative Commons BY-NC-SA licence.

×