Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

The Agony and the Ecstasy of being Agile when the Schedule is Not

278 views

Published on

Slides from my talk at Agile Lean Ireland 2019

Published in: Software
  • Be the first to comment

The Agony and the Ecstasy of being Agile when the Schedule is Not

  1. 1. “The Agony and the Ecstasy of being Agile when the Schedule is Not.”
  2. 2. Aidan Casey Head Of Engineering - Johnson Controls Cork @aidanjcasey https://medium.com/@aidanjcasey
  3. 3. Connected Converged Security
  4. 4. Typical Customer Profile ● large organisation with many offices across the globe (50-1000 buildings) ● dedicated security operations centre’s (SOC) ● billion(s) alarms annually ● different building and security platforms in different offices ● highly regulated and security conscious
  5. 5. Team Structure
  6. 6. Team Mercury Team Mariner Team Beara Team Torc Data Science DevOps UX cross functional teams specialist teams event processing & machine learning alarm handling workflows & editors Incident & alarm management data ingestion & mediation other roles product management lead architect security champion
  7. 7. Team Mercury Team Mariner Team Beara Team Torc Data Science DevOps UX 2 week sprint 2 week sprint continuous 4 week milestones end of sprint demo end of milestone demo Team Mercury
  8. 8. Team Mercury Team Mariner Team Beara Team Torc Data Science DevOps UX
  9. 9. Team Mercury Team Mariner Team Beara Team Torc Data Science DevOps UX
  10. 10. Team Mercury Team Mariner Team Beara Team Torc Data Science DevOps UX
  11. 11. Team Mercury Team Mariner Team Beara Team Torc Data Science DevOps UX short lived team
  12. 12. Backlog Grooming - single shared backlog continually groomed - weekly sync between product owners and product managers - 3 month horizon - team’s follow the work
  13. 13. - each monthly milestone start with a team huddle at the physical team wall - combined end of sprint demo to close out each software release Our Organisational Heartbeat
  14. 14. Evolving Product Architecture ● microservices architecture ● ongoing rationalisation and simplification ● inherited codebases have been redeveloped ● prematurely scaled microservices ● pivoted from multi-tenant to single tenant
  15. 15. DevOps Practices ● religiously practice continuous delivery everywhere, except production ! ● 30+ microservices ● from zero to full environment in under 60 mins ● shared dev & test environments for all teams ● automated regression test suite runs in in QA each night ● milestone releases promoted to staging & production
  16. 16. Continuous Integration Pipelines ● functional testing ( BDD) ● security testing (static code analysis & container scanning) ● regression testing (hourly & nightly) ● soak testing ● performance & benchmarking
  17. 17. ownership of a shared environments is hard
  18. 18. (In)Sanity Tests ● “as many end to end tests as you can physically run in under 10 mins!” ● runs every 15 mins… everywhere ● fast feedback on failures ● teams self organise to react and fix
  19. 19. UX Community ● early on the UX designs got ahead of the product ● evolving into a community of practice ● UX epics are first class citizens of the backlog - evenly split between current and futures work
  20. 20. Data Science Community ● machine learning & AI are our secret sauce ● features are discovered using a data first approach ● multiple patents in place for machine learning & anomaly detection techniques ● exploring ways to involve data science tean more in acceptance testing of machine learning algorithms CRISP-DM methodology
  21. 21. Statements of Work
  22. 22. ● enabled incremental revenue before product has been fully built ● pain point when SOW don’t align with product roadmap ● if not articulated well - the customer will expect more !
  23. 23. Culture of Continuous Innovation
  24. 24. 10 Lessons Learned
  25. 25. t-shaped teams counteract siloed thinking #1
  26. 26. if you aren’t good at something do it more often #2
  27. 27. don’t let team boundaries limit how you work together #3
  28. 28. refer to frameworks but don’t rely on them #4
  29. 29. ownership of a shared environments is hard #5
  30. 30. follow the yellow brick road #6
  31. 31. the best teams lunch together #7
  32. 32. statements of work are awesome and awful #8
  33. 33. if your business isn’t ready for continuous delivery practice it anyway #9
  34. 34. make space for innovation & hack days #10

×