Firefighting as a Service

As a volunteer Firefighter with 20 years of experience and in my Job as "DevOps" Engineer I found some similarities between the two. I like to give an insight of what the core principles of a fire brigade are to provide "customer value" fast.

Transcript

1. Industrial DevOps Meetup 2019-11-25
2. Intro  WIIFW  Today you will learn how to organize yourself in chaotic situations.  That you know me a little bit better, here are some background information.  Since almost ~ 20 years volunteer fire fighter  and software developer 2 Industrial DevOps Meetup © 2019 Belimo
3. Intro  Fire service is present in your daily life  (slide 4) May you self was involved in an incident  (slide 5) May you are closely related to an incident  (slide 6) May you see our your own company  (slide 7) or May you self feel like this 3 Industrial DevOps Meetup © 2019 Belimo
5. https://www.20min.ch/schweiz/ostschweiz/story/Riesige-Rauchwolken-ueber-Schmerikon-20585579#showid=275875
6. https://tenor.com/view/fireman-fire-fighter-mickey-mouse-gif-5944541
7. https://tenor.com/view/spongebob-squarepants-fire-panic-blow-gif-4531289
8. Intro II  I will show you how SW-Development or even yourself can profit from the principles & methods used in fire fighting.  The text in the pictures are in German as the fire fighting material is in German. 8 Industrial DevOps Meetup © 2019 Belimo
9. Mission  (slide 10) But how to accomplish this mission if everything seems chaotic?  the mission priorities are ordered like this:  Secure (click 1)  Rescue (click 2)  Save (click 3)  Protect (click 4)  Master (click 5) 9 Industrial DevOps Meetup © 2019 Belimo
10. Mission 10 Industrial DevOps Meetup © 2019 Belimo
11. Iteration  But how does a mission stage looks like in detail?  (slide 12) During each mission step one or more iterations are made to accomplish the stage.  An iteration consist of the following phases  (click 1) Determine - Feststellen  (click 2) Assess - Beurteilen  (click 3) Decide - Entscheiden  (click 4) Act - Handeln  (click 5) Check – Kontrolliern  Where each iteration allows to go for- or backwards in the mission stage.  e.g. find a unconscious person while your on the way to extinguish a fire 11 Industrial DevOps Meetup © 2019 Belimo
12. Iteration 12 Industrial DevOps Meetup © 2019 Belimo
13. Chronology & Iterations  (slide 14) The chronology of a fire service call and the iterations of a mission are combined in the following way.  Example  Approach. Smoke from the building. Put on respirator in the engine  on the way to the fire with the hose. and you recognize a gas bottle. cooling it down and remove it. 13 Industrial DevOps Meetup © 2019 Belimo
14. Chronology & Iterations 14 Industrial DevOps Meetup © 2019 Belimo
15. Decision  (slide 16) But how does the fire chief run the mission if there is actually “no time” left?  Simplified it can be boiled down to answer the following three questions:  (click 1) What - Was?  (click 2) Where - Wo?  (click 3) With which - Womit?  e.g.  extinguish the fire in the second floor with the red hose.  rescue the person on the first floor balcony with the ladder. 15 Industrial DevOps Meetup © 2019 Belimo
16. Decision 16 Industrial DevOps Meetup © 2019 Belimo
17. Responsibility  (slide 18) Initially there is one person in charge and decides.  But with the first command he delegates responsibility to smaller teams. He is still in charge for the whole run but responsibility is delegated to a smaller teams  Such a team consist of 1-4 people  with a clear task and the mission priorities in mind. => example.  They do act autonomously but communicate their state and progress frequently 17 Industrial DevOps Meetup © 2019 Belimo
18. Responsibility 18 Industrial DevOps Meetup © 2019 Belimo
19. Check  (slide 20) The task and decisions are that small to have fast feedback and check the result. and decide for additional tasks. 19 Industrial DevOps Meetup © 2019 Belimo
20. Check 20 Industrial DevOps Meetup © 2019 Belimo
21. Software Development  (slide 20) So far those are the most important methods & principles to organize chaos.  But how can those improve software development?  Some are obvious, like the iterations. 21 Industrial DevOps Meetup © 2019 Belimo
23. Resume 23  Now you know the basic principles of the fire service  the permanent mission  How the Chronology iteration looks like  Decision  Responsibility  Check  I’d like to pick two topics to take a closer look and compare it with software development  The first Topic is Decision or deciding and the second is responsibility. Industrial DevOps Meetup © 2019 Belimo
24. Deciding  Deciding is the most important part in software development as well in your personal life (slide 25)  free after Paul Watzlawik (click 1)  But why? You can  Decide on the scope of your project and its components, or not  Decide on the responsibility of your components, or not  Decide on how to react in case of failure, or not  Decide on the efficient way by now to solve your challenges, or not  Each decision allows you to act instead of react, this allows you to be ahead of upcoming events or incidents in your software projects.  Remember. Decide on:  What - Was?  Where - Wo?  With which resources - Womit? 24 Industrial DevOps Meetup © 2019 Belimo
25. Deciding “one cannot not communicate" ~ Paul Watzlawick “one cannot not decide" (adapted from Paul Watzlawick) 25 Industrial DevOps Meetup © 2019 Belimo
26. Responsibility  The second topic I like to compare with SW development is responsibility (slide 27) WAIT  With decision comes responsibility (click 1)  Decide and Responsibility used in the right way is an enabler.  small, clear, tasks which are not interfering tasks of other teams.  Responsibility of the task is on the team  If something doesn’t work out as expected -> the team provides a solution oriented suggestion to resolve the task  The team is only interfered in case of emergency or requesting info if necessary. so the team can do its job. 26 Industrial DevOps Meetup © 2019 Belimo
27. Responsibility “Look at the word responsibility – “response-ability” – the ability to choose your response. Highly proactive people recognize that responsibility. They do not blame circumstances, conditions, or conditioning for their behavior. Their behavior is a product of their own conscious choice, based on values, rather than a product of their conditions, based on feeling.” ~ Stephen Covey, author of “The 7 Habits of Highly Effective People” decide 27 Industrial DevOps Meetup © 2019 Belimo
28. Closing  Now you had a short and interesting insight in to the methods & principles of a fire service.  So next time you feel like (slide 29) in your project!  Decide how you want to cope with the situation with the capabilities in your hands.  Thank you! 28 Industrial DevOps Meetup © 2019 Belimo
29. https://tenor.com/view/spongebob-squarepants-fire-panic-blow-gif-4531289
30. https://www.linkedin.com/in/markusboos/ 30 Industrial DevOps Meetup © 2019 Belimo
32. Sources  All fire service drawings  no changes have been made  Source: http://docs.feukos.ch/Einsatzfuehrung/BehelfEinsatzfuehrung/#/  Picture (slide 4)  Fire service Pfäffikon ZH 32 Industrial DevOps Meetup © 2019 Belimo