From zero to hero, avoiding monkey work!

Every professional developer has had formative experiences that have contributed to their growth after suffering various existential crises. In this talk I want to tell about my experience as a developer that brought me and my team to implement a Continuous Delivery process and that led us all the way to the realization of an Open Source tool that automates so many monkey tasks. We will see a real case of use and how we will be able to deploy to production from the very first commit.

Transcript

1. From Zero to Hero, avoiding monkey work! Raffaele Colace
6. Raffaele Colace COO/CIO, Co-Founder @ 20tab srl • Python senior developer • PHP, Java, Swift, C#, Dart, … • Agile Passionate • DevOps, Lean, Growth Hacking, … • Community leader @ #StopCoding • Founder @ Product Management Day 20tab.com
7. Poll 1 2 3 Agile / Lean / DevOps CI/CD Product Management
8. WHY?
9. © Lise Gagne/iStockphoto
10. Agenda 1 Waterfall © Nathan Anderson
11. Agenda 1 2 Waterfall Needs and opportunities © Greg Rosenke
12. Agenda 1 2 3 Waterfall Needs and opportunities Why/What © Jason Goodman
13. Agenda 1 2 3 Waterfall Needs and opportunities Why/What 4 How © Markus Spiske
14. 3 2 1
15. 20tab.com | Raffaele Colace 15 © Mery Nunez/Barcroft Media Me (17 years ago) New project
16. Process Requirements Analysis Design Coding Testing Deployment Maintenance
17. Process Requirements Analysis Design Coding Testing Deployment Maintenance
18. The Waterfall Model Requirements Analysis Design Coding Deployment Testing Maintenance
19. The Waterfall Model Requirements Analysis Design Coding Deployment Testing Maintenance ✖
20. © ron dyar Problems 1 Budget
21. Problems 1 2 Budget Wasted time © insung yoon
22. Problems 1 2 3 Budget Wasted time Low quality © Chris Ried
23. Problems 1 2 3 Budget Wasted time Low quality 4 Dissatisfaction © Sebastian Herrmann
26. The Waterfall Model Requirements Analysis Design Coding Deployment Testing Maintenance
27. The Waterfall Model Requirements Analysis Design Coding Deployment Testing Maintenance
28. The Waterfall Model Requirements Analysis Design Coding Deployment Testing Maintenance
30. ?
32. Agile Manifesto Principi “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.” Agile Manifesto
33. Product - Marty Cagan Valuable Usable Feasible Viable
37. 1. Discover Why are we doing this? At this stage, workshops are proposed to help visualize the high-level motivations, the impact we want to generate, who are the actors involved and why, what is the context, what is going to be successful and what a failure. OUTCOME → Defining strategies and priorities → Product overview → View different actors involved TOOL: Stakeholder Mapping, Impact Mapping, Product Vision board, Lean Canvas.
38. 2. Define What do we have now? Once the motivations, the goals, the users involved have been framed, let’s consider the existing ones. Finally, we collect all the information about the brand in order to give continuity to the design. OUTCOME → Pre-existing products and brand definition → Identification and description of the main workflow → Understanding who the user is and what they need TOOL: Product Vision Board, User Journey, UX heuristic, User Personas, Opportunity Solution Tree, Non Functional Requirements, Risk Management.
39. 3. Ideate We give shape to ideas Understood the challenge that we face and the landscape in which we start, we begin to suggest concrete solutions to achieve the desired goals. This is the most complex phase, where we seek for the validation of workflows and wireframes through prototypes to be tested with users/clients, until picking up what will seem to be more convincing. OUTCOME → Design of different solutions to compare, prototype and test → Confirmation of workflow TOOL: User Journey, Workflow, Wireframe, User test.
40. 4. Design We define the details After we chose the path to follow, which will be constantly questioned anyway, we move on to set up the operational phase, with the User Story Mapping and the creation of a Mockup for the first interfaces, the study of the less certain technical issues and the choice of general architecture. OUTCOME → The map of tasks to be implemented, based on the goals of the users → Main design of the user interface → Evaluation of a possible architecture and any critical issues TOOL: User Story Map, Mockup.
41. 5. Plan We define a plan of action We are all set to start developing.All we need to do is to estimate the US created, picture a roadmap and set up the first sprint. OUTCOME → Operative proposal → Evaluation of the ‘weight’ of each User Story and projections of the work to be done. TOOL: Adaptive estimation, Roadmap.
43. Lean Product Development
44. © Lise Gagne/iStockphoto
45. Deliver valuable software continuously © Nattanan Kanchanaprat Need
46. Continuous Delivery and every related practice. How
47. Cultural change and application of good practices Mindset DevOps
48. Talos https://github.com/20tab/talos
49. Talos 1 Setup 2 Gitlab 3 Provisioning 4 CI Pipelines 5 Deployment https://github.com/20tab/talos
50. Talos Architecture
51. Recap 1 2 3 Continuous Learning Collaboration Transparency 4 5 6 Best Practices Feedback Vision
53. Thank you 20tab.com raffaele@20tab.com rafleze / 20tab raffaele-colace