UXDX Dublin - The Conjoined Triangle of Success, By Fabrizio Fortunato, May 23rd 2018
- 2. ME Fabrizio Fortunato Lead Frontend Developer @izifortune izifortune.com
- 3. Welcome to the Madhouse
- 4. Abandon all hope ye who enter here
- 5. Contents ● Deliveries ● Teams ● Quality ● Tools ● Compromise
- 6. The conjoined triangle of success
- 7. INTRO ● www.ryanair.com ● rooms.ryanair.com ● Lesson learned
- 10. What changed www.ryanair.com ● Redesign ● API first approach rooms.ryanair.com ● New website launch ● Latest technology ● Cloud based
- 11. Lesson learned ● Avoid big releases ● Focus on MVP ● Do not play “hot potato” with other teams ● Brooks's law
- 12. 9 pregnant women can’t make a baby in one month
- 13. DELIVERIES ● Big bang/incremental ● Infrastructure
- 14. Finally all our hard work paid off
- 15. Big bang/incremental ● Never goes well - Big bang survivor ● Dark/soft releases ● Fast feedback
- 16. Infrastructure ● Infrastructure as code ● Responsible for your infrastructure ● Continuously improve it
- 17. My servers can handle 10 times the traffic if they weren’t busy apologising for your shit codebase
- 18. TEAMS ● Delivery pods ● Vision
- 19. It's weird. They always travel in groups of five. These programmers
- 20. Delivery pods ● Autonomous ● Heterogeneous ● Boundaries
- 21. Vision ● Context to the team ○ Empowering Autonomous Teams from the Top Down - Bryan Dove UXDX17 ● Phases of the team - Roy Osherove, Elastic Leadership: ○ Survival mode ○ Learning mode ○ Self-organization mode
- 22. QUALITY ● Metrics ● Comparison
- 23. How many data could one guy manipulate at once
- 24. Metrics ● Performance ● Best practices
- 25. Comparison
- 26. TOOLS ● Correct tools ● Example tools ● Monitor
- 27. It’s not magic it’s talent and sweat
- 28. Correct tools ● Enable your team to achieve your vision
- 29. Do you wanna know what i have? A f****** car whose doors open like this!
- 30. Example tools ● Styleguide ● Common components
- 31. Monitor ● Performance budgets ○ https://goo.gl/6og3B2 ● Lighthouse audits ● Analytics
- 33. The conjoined triangle of success
- 34. Now what did those 2 triangles makes to together? A box! you can’t make that shit up
- 35. Deliveries/Quality ● Technical debt ● User satisfaction & value ● Team satisfaction
- 36. There are no expert is only us
- 37. Thank you
Editor's Notes
- #8: I've created the conjoined triangle of success based upon the experiences that we gained while delivering two large products for Ryanair.
- #13: Key points of the two product deliveries, we are what we are based upon your experiences also
- #16: We went through different changes of our delivery approach over the course of this 3 years, generally speaking we are always trying to reduce the scope of the deliveries and this caused a fundamental shift on our approach.
- #21: The quality of your product can also be measured by the quality and balance of your teams as well. Teams are the foundation of your products. I like to think that a lot of the software problems that you encounter can be brought back to people problems or team problems.
- #23: S. If your team is constantly chasing its own tail and putting out fires, instead of having time to sit down and experiment, learn new things L. You can tell you’re in the learning phase when your team has enough slack time to learn and experiment and you’re using that slack time. S. You can tell you’re in the self-organizing phase if you can leave work for a few days without being afraid to turn off your cell phone and laptop.
- #27: Quality is an inclusive term to use especially in software development, what we tend to focus in Ryanair in the frontend team is the quality for the user. We put the user first while defining the quality of our deliveries.
- #37: by tools I mean everything that can help your team achieve your vision or your goal. You can have the smartest people around and growth at an enormous rate but still lacking the proper tools can have a huge impact.
- #39: That problems that we solve in software development or specifically in frontend are more or less the same across different projects. You don’t want your teams to repeat themselves over and over again. You want your teams to be a focus on their deliveries so that they can deliver their best all the time.
- #45: A box they make a box, the expression to make a box, if you watch silicon valley, refers to compromise with the business or stakeholders.