Successfully reported this slideshow.
Your SlideShare is downloading. ×

How Agile changed Software Development

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Upcoming SlideShare
Innovation in the Agile Age
Innovation in the Agile Age
Loading in …3
×

Check these out next

1 of 73 Ad

How Agile changed Software Development

Download to read offline

Slides of my talk at the Feb 20th 2020 PMI NIC Event on Requirement Management at Wartsila in Trieste, Italy. I'm highlighting what worked well and what did not during my career, also taking into account recent paradigms such as Cloud and DevOps. I'm also dissecting some of main agile principles and sharing my opinion on how to benefit from them.

Slides of my talk at the Feb 20th 2020 PMI NIC Event on Requirement Management at Wartsila in Trieste, Italy. I'm highlighting what worked well and what did not during my career, also taking into account recent paradigms such as Cloud and DevOps. I'm also dissecting some of main agile principles and sharing my opinion on how to benefit from them.

Advertisement
Advertisement

More Related Content

Slideshows for you (20)

Similar to How Agile changed Software Development (20)

Advertisement

More from Steve Maraspin (20)

Recently uploaded (20)

Advertisement

How Agile changed Software Development

  1. 1. How Agile changed Software Development Steve Maraspin <s.maraspin@mvlabs.it> CC BY-NC-SA 3.0 - http://creativecommons.org/licenses/by-nc-sa/3.0/
  2. 2. If you’ve enjoyed this presentation and want to learn more, you can find useful references at the end of this slide deck.
  3. 3. Waterfall software development
  4. 4. • Requirements (Analysis) • Design • Module Development • Module Integration • Maintenance Sequential software development
  5. 5. • Requirements (Analysis) • Design • Module Development • Module Integration • Maintenance Sequential software development Months
  6. 6. • Requirements (Analysis) • Design • Module Development • Module Integration • Maintenance Agile software development Weeks (or even days)
  7. 7. • Requirements (Analysis) • Design • Module Development • Module Integration • Maintenance Agile software development Weeks (or even days)
  8. 8. • Requirements (Analysis) • Design • Module Development • Module Integration • Feedback Agile software development Weeks (or even days)
  9. 9. Project Scope
  10. 10. Requirement Analysis
  11. 11. Software Design
  12. 12. Module implementation & integration
  13. 13. Backlog Items On to agile…
  14. 14. Timeline
  15. 15. Timeline
  16. 16. ATOMIC REQUIREMENTS
  17. 17. EMERGENT REQUIREMENTS
  18. 18. CODE & FIX
  19. 19. Where sequential fails in bureaucracy, Agile fails in anarchy - Steve McConnell
  20. 20. • Automated testing • Frequent integration
  21. 21. INTEGRATION ISSUES Works on my machine! Interface contract whaaat?!?
  22. 22. Virtualization Containerization Cloud
  23. 23. DevOps
  24. 24. DevOps • Same environments on different hosts
  25. 25. DevOps • Same environments on different hosts • Continuous (automated) deployment
  26. 26. DevOps • Same environments on different hosts • Continuous (automated) Deployment • Infrastructure as code
  27. 27. AGILE ENABLERS
  28. 28. Agile: the good • Short iterations → feedback value
  29. 29. Agile: the good • Short iterations → feedback value • JIT planning → plan adjustments
  30. 30. Agile: the good • Short iterations → feedback value • JIT planning → plan adjustments • JIT requirements → avoiding waste
  31. 31. Imagen taken from “Skateboard, Bike, Car” by Andrew Wilkinson https://medium.com/@awilkinson/skateboard-bike-car-6bec841ed96e
  32. 32. Are we sure users will tolerate having to adapt so often?
  33. 33. Agile: the risks • Poor User Experience
  34. 34. Agile: the risks • Poor User Experience • Expensive architectural mistakes
  35. 35. Agile: the risks • Poor User Experience • Expensive architectural mistakes • Loss of focus
  36. 36. Agile: the risks • Poor User Experience • Expensive architectural mistakes • Loss of focus …beware of Availability Heuristic!
  37. 37. • Agile is no cowboy development Takeaways
  38. 38. • Agile is no cowboy development • Cloud and DevOps are Agile enablers Takeaways
  39. 39. • Agile is no cowboy development • Cloud and DevOps are Agile enablers • Beware of project goals and User Experience Takeaways
  40. 40. CROSS FUNCTIONAL TEAMS
  41. 41. Upfront Activities • Vision & Scope Definition
  42. 42. Upfront Activities • Vision & Scope Definition • High Level Analysis
  43. 43. Upfront Activities • Vision & Scope Definition • High Level Analysis • Subsystem Decomposition
  44. 44. Upfront Activities • Vision & Scope Definition • High Level Analysis • Subsystem Decomposition • Main Architectural Design
  45. 45. AGILE SPRINTS
  46. 46. THINK GLOBAL, ACT LOCAL Make choiches. Identify goals upfont. And make some plans. Be then prepared and deal with reality. With the unexpected. And changing contexts.
  47. 47. Thank you for your attention Stefano Maraspin s.maraspin@mvlabs.it
  48. 48. References Royalty free pictures used in this presentation are from https://pixabay.com/
  49. 49. Don’t miss our next open events… Join our Mailing List http://eepurl.com/s3Kab @mvlabsitwww.facebook.com/mvlabst.me/mvlabs_events don’t miss the underscore too!
  50. 50. s.maraspin@mvlabs.it GOT FEEDBACK? QUESTIONS? WRITE ME @maraspin

×