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.

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. If you’ve enjoyed this presentation and want to learn more,
you can find useful references at the end of this slide deck.

3. Waterfall software development

4. • Requirements (Analysis)
• Design
• Module Development
• Module Integration
• Maintenance
Sequential software development

5. • Requirements (Analysis)
• Design
• Module Development
• Module Integration
• Maintenance
Sequential software development
Months

6. • Requirements (Analysis)
• Design
• Module Development
• Module Integration
• Maintenance
Agile software development
Weeks
(or even days)

7. • Requirements (Analysis)
• Design
• Module Development
• Module Integration
• Maintenance
Agile software development
Weeks
(or even days)

8. • Requirements (Analysis)
• Design
• Module Development
• Module Integration
• Feedback
Agile software development
Weeks
(or even days)

9. Project Scope

10. Requirement Analysis

12. Software Design

14. Module implementation & integration

19. Backlog Items
On to agile…

20. Timeline

23. Timeline

32. ATOMIC REQUIREMENTS

33. EMERGENT REQUIREMENTS

34. CODE & FIX

35. Where sequential fails
in bureaucracy,
Agile fails in anarchy
- Steve McConnell

36. • Automated testing
• Frequent integration

38. INTEGRATION ISSUES
Works on my machine!
Interface contract whaaat?!?

42. Virtualization Containerization Cloud

45. DevOps

46. DevOps
• Same environments on different hosts

47. DevOps
• Same environments on different hosts
• Continuous (automated) deployment

48. DevOps
• Same environments on different hosts
• Continuous (automated) Deployment
• Infrastructure as code

49. AGILE ENABLERS

50. Agile: the good
• Short iterations → feedback value

51. Agile: the good
• Short iterations → feedback value
• JIT planning → plan adjustments

52. Agile: the good
• Short iterations → feedback value
• JIT planning → plan adjustments
• JIT requirements → avoiding waste

53. Imagen taken from “Skateboard, Bike, Car” by Andrew Wilkinson
https://medium.com/@awilkinson/skateboard-bike-car-6bec841ed96e

54. Are we sure users will tolerate having to adapt so often?

55. Agile: the risks
• Poor User Experience

56. Agile: the risks
• Poor User Experience
• Expensive architectural mistakes

57. Agile: the risks
• Poor User Experience
• Expensive architectural mistakes
• Loss of focus

58. Agile: the risks
• Poor User Experience
• Expensive architectural mistakes
• Loss of focus
…beware of Availability Heuristic!

60. • Agile is no cowboy development
Takeaways

61. • Agile is no cowboy development
• Cloud and DevOps are Agile enablers
Takeaways

62. • Agile is no cowboy development
• Cloud and DevOps are Agile enablers
• Beware of project goals and User Experience
Takeaways

63. CROSS FUNCTIONAL TEAMS

64. Upfront Activities
• Vision & Scope Definition

65. Upfront Activities
• Vision & Scope Definition
• High Level Analysis

66. Upfront Activities
• Vision & Scope Definition
• High Level Analysis
• Subsystem Decomposition

67. Upfront Activities
• Vision & Scope Definition
• High Level Analysis
• Subsystem Decomposition
• Main Architectural Design

68. AGILE SPRINTS

69. 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.

70. Thank you for your attention
Stefano Maraspin
s.maraspin@mvlabs.it

71. References
Royalty free pictures used in this presentation are from https://pixabay.com/

72. 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!

73. s.maraspin@mvlabs.it
GOT FEEDBACK?
QUESTIONS?
WRITE ME
@maraspin