Fredrik Ha Carleson: Unlocking Agile Efficiency: From Days to Minutes

This talk delves into the importance of culture in driving agile efficiency and how companies can leverage DevOps principles to enhance their software development processes. The speaker emphasizes that having cross-functional, multi-skilled teams is key to achieving faster cycle times and continuous deployment. He illustrates these concepts through storytelling, using a fictional character, Jackson Star Strider, whose journey reflects the transformation from traditional, siloed development practices to more innovative and collaborative approaches. By comparing rigid structures with flexible team dynamics, the speaker highlights that mere adherence to Scrum mechanics without a supporting culture can impede true progress. Ultimately, the discussion advocates for fostering an environment of continuous improvement and adaptive practices to navigate the ever-changing tech landscape.

[Music] ladies and Gentlemen please welcome our next speaker Frederick Haw Carlson presenting the topic unlocking agile efficiency from days to minutes the power of multis skull teams and continuous deployment greetings everyone today actually will not be Frederick I will be Obi One Frederick you can see I'm a Jedi um it's a bit funny because in the first keynote you talked about you know the importance of wearing

the right clothes and I just feel so stupid you know because this might not be the best way to give a serious impression but I do think maybe I should wear this at work you know it it could be quite interesting you know because then I could just walk up to all the product owners I will tell them you these is the technical depth that you're looking

for you will fix it you will prioritize it to do some Jedi Mind Tricks on on that part um in a littleit minute I would tell you the story about Jackson star strider um he's a Padawan of me but first let's go through some some background so you can see that for the next five years or so the amount of money to be invested in devups is

going to grow by about 20% per year and this is driven by a need to have faster cycle times and faster delivery and why are companies why do they want to invest so much money in this is it just to be more efficient to be faster no I think it's on the next level basically because if you can be fast and you can get something into production

very fast you can learn all the time and then you can adapt to become better so in this session we will look at some of the elements needed in order to do this so we will look at the role of culture that will be part one shaping how we work and then we'll look at the power of multikill teams collaborating effectively and lastly we look at how

devops principle can help us improve our flow and it can be a little bit challenging to B all of these elements into something that works but when you manage to do it it's actually quite powerful so let's dive into part one out of three and it's about culture and we all want to be successful right and today scrum or other agile Frameworks are everywhere so if everyone

runs scrum then what's the differ C for you what is the element that makes you stick out that gives you a Competitive Edge I think one of these elements is culture and culture for me is your idea of how the word Works your idea of how the world works if you believe that the Earth is flat you will not dare to take action to sayil too far

out because you will be afraid of falling off the edge so what we believe decides how we act what do you believe decides how you act and here's the main point your company's culture will decide how you will run scrum or any other framework for that matter so let's start with a big question then will culture beat structure and I kind of believe that changing a company

structure but not this culture it's a little bit like putting Wings on a stormtrooper it might look different but it's still the same beneath so when scrum became popular we changed the way that we worked previously we used to have a team of only requirement specialist we could have a team of only testers a team of only programmers then with agile Revolution we changed that to have

cross functional teams where we put you know testers and programmers and business analysts together into one team and that definitely made us better but today I don't think that's enough and you know despite all the claims and linked in that agile is dead and people are not very fond of it you know at least on my LinkedIn you know flow that's the only thing I see most

service say that still about 80% of old companies use scrum or some similar framework and what is it that makes companies successful it's usually that to have a Competitive Edge something that makes you different from anyone else now if everybody runs scrum then what certain Fator what is it that makes successful I don't believe that 80% of the companies that you know change to use scrum have

had success with scrum changing the idea or changing how you think is very difficult it's not unlike you know the transformation that a butterfly does when it goes from larva to adult and did you know that when that happens for butterfly about 80% of its internals are moved around that's pretty amazing but and the same might be needed for a company but the difference is that once

you have transformed you have different capabilities you have some new skills you have for example wings and you should remember to use them because they're not the Lara anymore so let's investigate a little bit between the interplay between mechanics and culture many have tried to copy Toyota success of course I will bring up Toyota because everybody does that but it's such a good company to to to

use and most companies have tried to copy Toyota success by copying the mechanics of how Toyota works for example copying the way they work the processes or building identical factories or for example introducing an andon chord if you don't know what an andon cord is listen a little bit carefully now because we'll come back to this an andon chord is a rope that you can pull when

you pull this rope the entire production line stops and then everybody comes rushing to see why it was stopped it could be because of a quality to measure or you have an idea of how to improve the idea is that you should get quick feedback take action learn and continuously improve and system but if no one pulls the cord it doesn't matter how well you have copied

mechanics one of my favorite examples exemplifying Toyota's culture is when an reporter interviewed a manager at Toyota and he said aren't you afraid now that your competitors have stolen a very important blueprint that they will be as efficient as you are but the manager just looked very calmly and he said I'm not worried at all because by the time they have figured out how to assemble all

of these mechanics and how to use it we have already improved so much that they will still be behind that's continuous Improvement so many companies have tried to copy Toyota success but very few have succeeded despite you know Toyota being very open about their TPS system so mechanics can be copied culture is however very challenging to reproduce and it's the same with scrum or basically any other

framework doesn't matter what you use if you only follow the mechanics you're probably missed the real benefit so now scrum has ruled for the last 15 years or so and many developers today have never worked with anything else and for me that is a dangerous situation for me scrum was an eyeopener it's a different way of thinking of working if I've only done things in the same

way all the time it's hard to think of a different way of doing it but once you have tried various ways of doing the same thing you actually get insights into why does it work or why does it not work so that's essential to finding out and getting inspiration I think there was someone famous who said you know insan is doing the same thing over and over

again and expecting different results so the isolated mechanics of scrum or any other framework or any future framework for that matter is not the key to success and you can think of for example the scrum retrospective as an andon chord if it's not used effectively it's useful so now if you believe that a manager would be very mad at you if you pull the andon cord you

will of course not do it and if you believe that the framework and its Essence is events or its mechanics you will not challenge them and from my experience very few actually challenge the system and very rarely does the retrospect persective lead to solve any problems outside of the team and I think that's a shame because today most teams are effective they are very good they have

experience and still most managers focus on making the team better what they should be focusing on is the things that really make the team not being able to work as good as they could and those are constraints um that could be dependencies and things stopping the flow outside the team's control and it's also a shame that if a team should suggest such a change outside of the

team's control usually the organization or the system resists this and usually it's the management that resists this because management has been bred up and talked that efficiency that is standardization efficiency is when everybody works in the same way efficiency is optimizing the work process to make sure everything goes in the same way and keep this thing about standardization a little bit in the back of your head

as we will talk and listen to the story about team alpab later on so we need to understand how company culture affects the way teams or companies can approve and that will bring us to the concept of shua sorry should have broke some water here so have you experienced teams that get stuck you know doing the same thing over and over all the time year out and

in they get stuck in sermones as I call it when they do the events the same thing or all over the place so Alisa Cogburn perfect thank you introduced Adult Community to the concept of Shu Hai and this comes from martial arts Japanese martial arts originally and it describes the stage on your path to Mastery for example in aidu and this progression it underscores the importance of

moving beyond just following the rules shu to understanding the underlying principles huh and inventing your own practices experimenting re and many teams get stuck in the shoe process merely mimicking and following the rules and I think that's the same as trying to copying Toyota success yes you only follow the mechanics and the rules but you need to move on to the next stage again as someone famous

said insanity is doing the same thing over and over and expecting a different result I'm watching a documentary right now it's called life on our planet basically the life you know the basic for for survival uh is that the most adaptive survive competition drives adaptability and the word always changes meaning the battlefield is constantly changing and I think you know that's exactly the same for any company

they have to adapt to survive and to be fair all Frameworks and methodologist know about that even in ISO they know this about continuous Improvement you have Denning he says plan do check act you have in the US military the UDA Loop observe Orient side act you have in scrum inspect and we have in oh sorry Alis cogs who says um collaborate deliver reflect improve um you

have devops which is get flow um get quick feedback and continuously improve so this is not something new and if we can improve all the time we might actually end up with something completely different than what we started with something different than scrum for example and I think that's fine I think that's a little bit like the butterfly you know moving from larva adult so the main

point I wish to convey here is actually the danger of not improving and that applies to janit as well and that's what we will talk about next so now with the idea of culture and shua in mind let me tell you the story of about Jackson starrider and we will see how culture creates two very different ways of working with scrum video can load it great could

it be that I have no internet connection yeah I have no see good the kind of drink some water meanwhile at last year's conference um the ending talk was about from person they actually did some deep fake Imaging in in real time um and I thought that was so interesting so I actually had to to try and experiment a little bit um with that so let's see

when the video can start when we have internet connection again maybe you can guess the famous character from Star Wars that is in the video and let's see can move back on the lonely empty land of jaku a planet covered in Endless sand and old spaceship left to Decay Jackson star strider holds his sister on a St night they are barely surviving in a place where only

rich people have access to technology sitting close together Jackson's sister is struggling to gath her lofter which used to fill the arrow is now quiet because of a serious illness in the quiet desert her Lively spirit is fading away Jackson who is only 12 years old but looks like he has experienced a lot of sadness look up at the sky hoping for a miracle he desperately wants

to save his sister but he knows it's impossible his hands they shake with grief and his face is pale with sadness Jackson search the guy not for Hope but for an explanation of why he couldn't save his sister with advanced technology that was out of his reach Jackson makes a silent promise to himself as his sister's life slips away he will overcome the poverty that keeps his

family down he will learn to use technology like the rich people do he will Master the science that he feels let him down 10 years later jaxon's determination has changed his life the boy who grew up in the desert is now studying Engineering in a school filled with Advanced machines and smart students his hard work and sleepless nights have paid off as he gradate graduates from this

program Jackson's hand they now create an innovate his promise to himself and his history is finally coming true and so the story of Jackson Stars Rider begins not with excitement and joy but with a quiet determination of a boy who fac challenges and decided to make his own destroy Jo me and I will complete your train so Jackson graduating as a top five student he travels to

he's get recognized by the Empire and the Empire offer him a position in a top secret project it's called project Stardust it's a project to end all wars they say he hops on board on the shuttle and he travels to the planet of IDU which is a watery planet with lot of jungles very different from the desert Planet he grew up on and arriving at Ado he

is escorted stormtrooper to meet with a high ranking officer an official overseeing the Stardust project and he welcomes Jackson welcome Jackson you have been chosen for a critical role in ensuring the success of the Empire your programming skills are unparalleled thank you sir I'm honored to contribute to the Empire's cause your task is crucial you will be responsible for developing the software that controls the defense of

our DS1 orbital battle station efficiency and precision are Paramount this data pad will contain all the schematics and blueprints you need but you will find reality more impressive follow me and I will show you the battle station in all its Glory as Jackson sees the destructive potential of the battle station he has an internal monologue this is not what I expected what have I gotten myself into

meanwhile the Imperial officer continues outlining the rigorous processes and timelines that must be followed Jackson nods in apparent agreement masking his internal turmoil as the Imperial officers leave the room leaving Jackson with the schematics Jackson can't help but feel cold so Jackson he joins the Empire's it Department the Team Alpha led by scrum Welter and the scrum Master tells Jackson we are using a well oiled Machinery

of a framework called scrum imagine that right you didn't know that it would survive so many years now what I will tell you is of course a fictional story of how the Empire uses scrum and how they use scrum is just a logical deduction based on their culture this is not really how I would recommend you know running scrum as such you know so the scrum was

Bel it tells you know Jackson everybody in the Empire follows very strict scrum rules or protocols and each member is a specialist and he's or her own area Jackson is a programmer and he's a specialist in that for example and they start the first planning meeting and Jack oh sorry valter he says welcome everyone I'm leading this as your scrum Master our goal is to complete all

the user source as outlined by the product owner and we'll use planning poker for estimations and one story point will be one days work under ideal conditions and after estimating and doing all the capacity tning um he says so now our Sprint goal will be to finish all the US of stories that's our Sprint right so valter then looks at each team member and he says make

sure we have something useful by the end of the Sprint and remember our motto which is analyze understand standardize remember what I said about previously so all all the teams in the entire Empire operate in exactly the same way now if you think about Shu Hari again you know Shu following the rules do you think it's easy or hard for this team to move on to the

ha or the resear now as Jackson works with his team he can see how organized but inflexible their approaches or Machinery I should say so one person breaks all down all the you know features the uses s and task these are handed over to a single isolated programmer who works on his or her own task and when they are done they hand it over to a tester

and then the tester does all the testing and when that is done it's merged into Main and the configuration manager comes into play and he actually you know does the continues merging and it packes everything and then it's sent to operations with instructions of how to deployment and Jackson he wonders why am I even on a team because we all work in isolation on our own small

task why why should we be in a even so the process is frustrating for Jackson he quickly finishes his task and then is handed over to a tester and it might take a day or two before the tester have time to actually test his user story and if there's a problem is being sent back to him Days Later disrupting his current Focus remember in one of the

talks they said 23 minutes right to get back again once you have lost your focus and because of long deployment times only work done in the first week can actually make it into production everything that is finished programming in the second week will have to wait for the next Sprint so Jackson he feels you know the system is holding me back and he sees the need for

a more flexible collaborative approach however in the Empire change is achieve but Jackson he can't stop thinking couldn't we make things better another frustration is the team's lack of understanding of the broader mission's value because they don't understand what the end result will be there is a lot of rework so Jackson he goes to the product owner and says couldn't you at least tell us you know

the Big Goal so we understand what we're working towards so we don't have to make all of these mistakes and do the rework again but a product owner he looks at Jackson and says hey I'm accountable for maximizing the value of this product and you are responsible for programming let's stick to that we have our roles so frustration continues to stir within Jackson he feels like a

cog in a machinery and Jackson he thinks he will scream if there is another daily meeting where we would have to answer the same free questions or another retrospective that never leads to any change anyway so he voices his concerns to his grandmas and says you know I don't think this is very efficient can we work in a better way and the SW looks at him and

say you're right we should be more efficient so from now on our Sprints will be only one week long that will make us much faster mhm actually it just makes things much worse because the Sprint planning is still four hours half a day out of five days the story points are still 5 days and because of this Rush of time jaon now has to really lower his

quality of the code in order to be able to finish it by Friday and every Friday the tester just panics because then all the usess s come to him to test in one day so of course all the bugs is Skyrocket but I don't learn about it until two weeks later because it takes more than a week to move it into production and then it comes back

and completely ruins their commitment because their commitment is to how many user service they can complete so management sees this and it says well this is not good so you have three months in three months there is a deadline and then you need to show something a demo that show us you know live so three hectic months later it's time for the demo Jackson he hears the

other team member saying that you know that because of lack of time we haven't had time to do unit tests so this first test will have to be a live test so they're all invited to the control room to look so in the heart of the Empire's technology division Jackson stands in a dimly lit room full of control panels and blinking lights he watches heart pounding as

the weapon he unknowingly helped build up is aimed at a distant sacred Jedi Temple a symbol of peace and hope as the weapon fires a brilliant beam of intensive light hits the temple obliterating it into dust Jackson's breath is caued within his throat memories of jaku and Warth Throne landscape and his sister fills him and he feels a deep aching guilt he has helped to create the

monster despite mastering programming skills he is still helpless his folks are disrupted as he hear his scrum say something and he looks up and the scrum says good work Jackson now it's time for retrospective so as Jackson continues to work on this his struggles between his responsibilities and what he feels is right or wrong but his exceptional skills they get noticed and he's given a task to

take all the code you can see he's holding it in his hands and take it to the Imperial backup Vault on a different planet following backup protocols but as he is about to embark on the mission Jackson is beset by doubt and this is a significant moment for him it's time for him to choose his path and in a minute we'll play an interactive game and in

this game you will make the choices that it will either take Jackson down the dark path to become a scrum SI Lord or as a Jedi scrum night so I need and you know and so I'm just going to see if I can start up and and change this again it's so difficult with this one and I need different glasses to be honest this What's happen when

you get old you can't see anything um and I suck at multitasking okay um anyway there is a story about this because when I started to do this interactive Adventure I wanted to do it in cahoot or you know with um uh with server monkey and that just didn't work for me because it didn't have the functionality that I wanted and and also became very expensive so

I fored myself how hard can this be so I actually download a visual studio and uh opened up you know a c program uh project um with web forms and um um then I started to program it with shut GPT and I as I was doing this I was thinking to myself I need somewhere to publish this solution it's good I haven't stress tested this and it

seems to be working quite well um and and and that brought me back you know in memory link because in visual stud it's quite easy to publish to you know uh to to production you just click the publish button it automatically happens and you know in the beginning of the 2000 I was working as a programmer on on a e procurement site um and it was only

two programmers and we sat with the procurement officers and every day we came into office and we asked the procurement officers what do you want for functionality today and they told us what they wanted and we actually built it so it was very fast and lightweight process and at that time the way you move something into production is that you took the compiled code and you fped

it into a physical server that actually was in the middle of our internet which had a static public ID exposed to the internet and that's how things were at that time but anyway we just fed it was tedious so we decided let's create a script to do this automatically so we created a script so I had one click deploy 20 years ago um going fast forward to

today things haven't changed very much to be honest in Visual Studio still click the publish and I guess behind the scenes it might do an FTP to you know a server in ass sure but the thing that really struck me is how come a process that is so easy to do for one or two programmer suddenly becomes so complicated and takes such a long time when it

become more than five teams anyway I can see the counter has stopped this 38 here um so and Jackson he has landed on the other planet where the codt is he has entered the building and now it is time to play this um adventure and I hope bit will work now if you have played um Lone Wolf in in a book you will kind of recognize how

this work so I will play some text here and then you will choose alternative one or Jackson is hurrying through the corridors to back up the code in the vault when his Communicator beeps it's time for the daily scrum meeting he knows everyone expects him to be there but his task is very important should he go to the meeting or continue his mission so now you make

sure you and you can see the green bar and the other bar you know just races so yeah so most of you think you should continue to go to Vault okay that's great oh it's becoming a little bit more even there is some you know between Rebels and and and not so much Rebels I think we just move it so Jackson he actually then decides to skip

the daily meeting and as he moves on and turns off in his Communicator his focus on his go and as he moves further up in the corridor suddenly there's a big blast from a wall where he stood just seconds ago luckily he had skipped the daily scrum so good choice from you otherwise he might have just exploded and you can see up here you have some stats

and now you can see that actually Jackson is alignment is towards the good side now and you can see we still have 20 hit points for of you who still you know play these kind of games so the next choice here Jackson is lost in the facility as he tries to avoid the worst battle areas he stumbles upon an old terminal in a deserted section sounding warning

alerts it's running on Legacy code similar to the outdated Tech he grew up with on jaku a janitor nearby tells him that the Droid who specialized in maintaining that code has retired the terminal controls the environmental systems for the entire sector which is about to break down fixing it could prevent catastrophic life support failures for staff in the complex so which Choice have you made you uh

it seems like Choice number two alternative two is the choice which is the focus on the mission by locating his whereabouts and take the fastest route let's see what happens oh maybe I clicked too quickly because that now it was very anyway reasoning that it's not his responsibility Lea moves on and the live system support fails and that's leads to emergency throughout the sector and as Jackson

opens a sliding door all air is sucked from him and Jackson struggles onto the next Corridor closing airlock but he's injured so Jackson moves a little bit closer to the dark side as Jackson moves through the Maze of corridors the rebel attack intensifies there is Battle everywhere his Communicator beeps again a stress tester finally managed to test Jackson's code and noticed a critical bug Jackson could quickly

fix it yet protocol dictates that any change has to be merged by the configuration manager which takes so should Jackson fix the bug merch remain and update the code immediately or should they fix the bug follow protocol and wait for the configuration manag to changes most of you think you should up immediately that's alternative one right so Jackson fixes the bug and checks It Out by merging

it to the main branch bypassing configuration manager and this caus a little bit of extra work and frustration for the configuration manager but you know the thing is so what's the Lessons Learned here well it's hard to say which is the right thing or not the right thing you know I think the main lesson is that not having you know F ability to deploy into production easily

fast you know creates problems no matter what so therefore the alignment stays more or less the same Jackson is on his way to the Vault when he hears a team arguing in a meeting room a newly implemented security protocol has drastically increased the time it takes to log on to systems and they're working furiously to fix the issue Jackson fixed the same issue with his team a

few Sprints ago so what should Jackson do should it help the team to fix the issue or should it focus on his own critical Mission and move on oh we do have some helpful or let's see yeah I think it it it's stays there that we should help yeah so Jackson decides to help and together they find a way to deploy the solution and Jackson helps make

him a good team player but this where will cost him some time on his mission but luckily you know when he approaches the Cod world to log in the newly security routine that he has implemented helps him to quickly get to the Vault so this is a little bit you know about working in isolation and not helping each other usually we might have component teams or we

not talking to each other and therefore we don't see the big picture of how helping others can actually help us so I can see that yeah Jackson is leaning toward the good side let's see one finally arriving at the Vault Jackson's mission is clear upload his code to ensure the Empire's dominance yet as he initiates the sequence he's haunted by memories of jaku the helplessness the loss

the promised to to use technology for good now he holds the power to change the tide to give the rebels a chance with a few Strokes of keyboard so what should Jackson do should it upload a Koda plan saying Lo loyal to the Empire in his mission or should he put a secret back door in the code to help the rebels oh we have evil people in

this audience well this is of course you know a choice as software developers we have a responsibility for what we do and it's sometimes hard to choose the right path even though we you know should so let's move on to the final part here so adding the back jaon chooses to do what he believes is the right thing even if it's risky and the brave Choice shows

that he's will to stand up for what's fair moving to be a Jedi great good work [Applause] everyone so I think you can skip that and let's see let's read it um now of course in this interactive story you know the idea was to my wish to show our culture tapes how we use Frameworks as as scrum for example and now we will move on to the

final part of story where actually Jackson will join the rebel side team Bravo and and and um you know here he has brok all the wisdom that you talked him in this game to team Bravo to make a difference and make it a little bit change Jackson is in a hurry because a death s a a weapon he unwittingly held to Crate is closing on in on

the rebel base it has already destroyed alderan and now it's coming for the rebel base where Jackson is so Jackson now works on upgrading the software of the X-Wing Fighters he works together with other rebel engineers and they work hard every day they work together they become friends and he works hard and every line of code he feels can change you know the future of other planets

to not have the faith of elderon and each day they meet for about 15 minutes to plan together how they can easier reach goal it's an eff effective meeting that helps them to avoid other meetings as well and stay focused and Jackson's work is now very different from his time in the Empire and he likes how team Bravo Works they don't stick to the job description everyone

helps with everything and this makes work go faster and when work is checked in automatic builds are automatically triggered and if something goes wrong is notified immediately and Jackson is Amazed by The Continuous deployment without any manual intervention and he watches how code is packaged together with a container and goes to a staging area team bra approach here efficiently you know slashes time to production from days

to minutes compared with the Empire but more importantly and perhaps the most important thing Jackson feels he's doing something important he's working for something important and their Sprint goal is simple is to prevent the Empire's death stars ion cannon from hitting the X-Wing Fighter so they can actually destroy the Death Star so now the Death Star has come to base will Jackson's software work at as intended

or not and I should just give a little bit of a warning here um if you haven't seen the movie it would be a spoiler um and the second thing there might be some flashing lights if you're sensitive to that you might not want to watch as Jackson star strider worked tirelessly with Team Bravo he realized the true power of collaboration and Agility together they transformed his

coding skills into a Force for good his efforts culminated when he saw his code seamlessly integrate with the astr droids making the X-Wing Fighters dance through space with unparalleled Grace your destiny lies with me Sky Falker will be one news to be true There Is No Escape don't make me destroy you join me and I training if you only knew the power power of the dark side

I am your father as the remnants of the Death Star drifted into the void of space Jackson knew that he had played a crucial role in shaping the Galaxy's Destiny it was a journey that had taken him to the farthest reaches of his soul and in the end he had emerged as a hero Jackson had found his path purpose and redemption in a galaxy filled with Darkness

so we have seen how Jackson moved you know from a more restrictive processed Focus team Team Alpha to a more adaptive team Bravo so let's review a little bit about the differences and and also to connect it back to our talk about shuhari so I started by asking you know if everybody runs scrum then what's the differentiator and we discussed how C sure shape our word and

our beliefs and how we act and I told you the story rer and you know both are running scrum in theory um but in very different and some differences of course is the culture they operate in it's also working in Silo versus collaborating it's setting goals versus um following a plan and it's the speed of deployment and I just want to focus a little bit more on

the speed of deployment because this is a devops conference after all when they attend conferences it might sound like everyone can deploy to reduction 100,000 times per minute per day but if you look at the state of CD this is actually figures from 2023 but I have looked at the figures of 2024 and they are more or less the same they're up or minus about 2% so

nothing much have changed between 2023 and 2024 and you can see you know about half of all that developers now use continuous integration or um uh or and and and and monitoring has G up a little bit to 40% making it the top activity um and then we have in you know at thir Place continuous integration for testing code changes the biggest increase is actually in security

testing and that's 28% and that kind of means that only one company in free actually does sest or you know some automatic security testing and I wonder what the rest of the companies do because that must be an enormous bottleneck doing that manually or you might not do it and the top performance also can put code into production unless than a day has vared between 13 and

17% so let's say 14 15% and that's the same in both 2023 and 2024 and it's about 20% that can fully automate everything moving things from code merge it with a container and putting up in in production as so and so on and this might be hard to see you know but it's about 10% of the companies can actually do multiple deploys per day but still about

35% of all the companies investigated do it you know less frequently than once per month and this survey was to let's see if I remember it correctly 26,000 respondents in 100 66 countries so it's quite a large survey now let's think about how Team Alpha works here in Team Alpha everybody has their own work and they work in silus and you first have the ba he breaks

down the requirements to individual use to IND developer who work on their own story and then they hand it over to a tester and then the test to test and they hand it over to configuration manager and then on the next day they might you know merge it and pack solution and then they hand it over to operations with instruction and then it's finally deployed to production

after some time and The crucial Point here is that everything happens in steps and there's a lot of handovers hand happening all the time and it might look efficient but it's not very efficient because you focus on having resource utilization oh I can see I'm running out of time a lot here you know and this is a well-known repeatable process but it's also very sensitive to disruptions

because everybody's working 100% And if something usual happen or something unexpected you know there will be cues and there will be delays and it's essential to understand that because of these lead times you know a two point user story you know will take two days plus six days to reach production a 5 minute bug fix will also take 5 minutes plus 6 days to reach you know

production and that means that we will have slow feedback loops and things will not be able to reach production within a Sprint now team Bravo contains more of team members who are good at both programming and testing and they might prefer one task over the other but you know they all pitch into help where needed and they're motivated by a strong goal instead which is to prevent

X-Wing fighters from the death stars iron cannons so the team they use continuous integration they have automated testing and that approach actually removes five of the steps automatically and a lot of handovers and shortens the production time here now how sharp are we on time is it very sharp or can I go over a few maybe okay I think that actually this is supposed to be another

video about how the continuous integration process works it's a I maybe we'll go through it very quickly I can skip some other things team Bravo has put much effort into writing unit and integration tests code and tests are often written in pairs and often the pilot is present one developer prefers coding and the other writes tests the critical point is that their work overlaps daily and they

work on it together a necessity to avoid long hand over times continuous integration when anyone commits a change a build process is automatically triggered in a pipeline during the build process a series of automated tests are run including unit integration and security tests these tests validate the software's functionality integration and security if any test is not passed the developers are immediately notified s Ste some if all

the tests passed successfully the CI pipeline triggers a deployment process where both the source code and the configuration for the the container are packaged into an artifact the artifact is automatically deployed to a staging environment undergoing further testing and validation this environment is a copy of the production environment allowing the team to catch any issues that may arise during deployment there are no handovers or need to

involve anyone outside the team to put functionality into production frequent increment delivery whether daily or more often offers several advantages these enable continuous feedback from stakeholders early bug detection adaptability for learning and experimentation enhanced collaboration among developers risk mitigation through smaller increments and prompt addressing of any issues a pipeline is like an automated andon pole so basically what you know team bra have done they looked at

this process they looked at the word what are the constraints what is it that increases cycle time and they remove the steps and they come up with a much more simple process it still takes about 4 days to do any programming because they all work together and it might take a little bit longer uh but actually get good unit in integration tests at the same time and

as the new pilot sits with them they can test requirements in real time to see that they're building the right thing as well so that increases um Quality and that also means that because of this what they can do is that a tway story will take two days plus one night in staging area to get into production a 5 minute bug fix takes 5 minutes to do

and then you wait overnight and it's out in production comparing that to you know a five minute bug fix which takes six days otherwise to to to fix and that means that Sor you know complete even late in the Sprint will make it into um production so what has happened here well you can see that Team Alpha which is influenced you know by their control approach shape

scrum to fit a predictable word so scrum becomes a planning tool for them so experimentation and learning is minimal so leaving the shoe stage is very hard for Team Alpha because any change to how they work must come top down from management deciding that they could change the way they work now team Bravo has a different culture instead they don't really follow a plan they have a

motivating goal and they find a way how to reach the goal and they learn through continuous experimentation they have a bigger zone of control and can decide how they work which means that they can reach the shoa or reage themsel instead so what actually decides how they work is the culture and the situation again Toyota success was you know from having scarce resources of the second world

war so that we're forced to be more lean than the competitors is a little bit the same with the Empire on the rebel team who doesn't have the same resources now you might think that just having pipelines is is just the solution it's not because if the Empire would use pipelines what would it look like probably they would just run it by the end of the Sprint

anyway or when the manager tells them to run it and that's not really how we want pipelines to work because we want the pipelines to give us immediate feedback so we can learn very fast and pipelines cost a lot to maintain and is hard to maintain so we should really use them if we want to invest them I think we actually skip the thing about uh the

technical depth I can send you some information about that if anyone is interested and then we move on to uh the last slide here so again the devops market is you know expected to grow by 20% for the next few year is driven by a need for faster cycle time times and deployments and we have explored some of the elements needed in order to have happen and

we've reflected in all of them and you can see it's in the circle here with the elements so basically it's about cultivating the right culture a culture that you know helps team to become better all the time they have new ideas and to to work together and it's inspired with goals so motivate your teams with goals not detailed plans because this encourage Innovation and empowers teams and

then craftmanship you know give the teams whatever they need to have continuous integration and continuous deployment and pipelines in place and reflect on your impact our technology today can change lives and you have to ask yourself the question am I doing this for a better life or am I unwittingly helping building another star and then lead of course with vision and purpose effective leaders can change the

system to help the teams work better and they can guide the teams towards a common goal and then of course the last one embrace you know the Journey of shuhari create the conditions with teams to move on to the next stage which is Shu or R and let's just end this you know with a quote from obiwan Kenobi which is in my experience there's no such thing

as luck thank you very much Master Frederick thank you so much thank you thank you so much and I don't know do we have time for one or two questions you're not into hurry uh airplanes are not waiting for you yeah sorry for rushing it I tried to time it but I must have very slowly it's cool maybe two two two three questions I love Star Wars

so nothing to add it's cool you too uh when can we realize that the team stopped being a scrum padavan and reached the rank of Master when actually the team improves thems all the time and figure out different ways of working you can see that the experiment they might say you know do things in a different way and still you know become better that that's a kind

of a fluffy ass right I I know but you know if they do you know answer the free question exactly the same day out you know year out and year in you know if if if they do the Sprint planning exactly in the same way we're not experimenting we're not learning a better way you know to to improve so if you always do it in the same

way following a checkbox list then I would say you're probably not into