#DevSecOps for kids

Hey there, kids! Have you ever heard of something called “DevSecOps”? It might sound like a strange and complicated word, but don’t worry, we’re here to explain it in a way you can understand.

Imagine you have a special secret box where you keep all your toys, and you want to make sure it stays safe. DevSecOps is like taking care of that secret box, but for computer programs and apps.

Let’s break it down into three parts: “Dev,” “Sec,” and “Ops.”

1. Dev (Development):
When people create computer programs and apps, they are like toy builders. They design, create, and build these digital toys. In the world of DevSecOps, this is where everything starts.

2. Sec (Security):
Just like you want to keep your toys safe in your secret box, computer programs need to be safe too. This part of DevSecOps is all about making sure the digital toys are protected from bad things, like hackers. Think of it as putting locks on your secret box or having guards to watch over your toys.

3. Ops (Operations):
Now, after building and securing the digital toys, we need to make sure they work smoothly. This is like making sure your toys are ready to play with whenever you want. It’s all about taking care of your toys and keeping them in good shape.

DevSecOps is like a team of grown-ups working together to create, secure, and take care of these digital toys. They build them, make sure they’re safe, and keep them running well. This way, people can use these digital toys without worrying about any problems.

So, in simple words, DevSecOps is about creating, protecting, and taking care of computer programs and apps, just like you do with your toys. It’s a way to make sure everything works well and stays safe in the digital world.

Now you know what DevSecOps is, and you can think of it as a big group of helpers making sure your digital toys are awesome, secure, and ready to play with!



Fix the system not the individual…#pmot…#in

systems-thinkingOn a recent business trip to Geneva I flew from Leeds Bradford Airport in the North of England. I checked through on time and headed for the gate to be met by a scene of organised chaos. The queue was very long and heaving with Schoolkids on exchange visits, holidaymakers and business people. At the very end of this long queue we were given a tray into which we had to load our laptops, keys, belts etc as part of the security screening process. This was undoubtedly the bottleneck and by the time I got through security to the Gate I was informed by an attendant that I may well have missed the flight. I was then subjected to admonishment, had I not heard the attendants calling people through for the Geneva flight – “No” , I hadn’t heard anything in melee – anyway to cut a long story short I caught my flight but not without a lot of hassle and stress.

Contrast this experience with the return journey – same plane, same loading, same mixture of people.

Here, at Geneva, the queuing system was completely different. Rather than joining  a long “snake” we joined the end of two queues where we were given a tray on a conveyor belt at the START of the queue. This gave us plenty time to put all our valuables into the tray before we reached the end of the queue and the X-ray machine. Consequenly there was no rush or panic, we all got through in plenty time & enjoyed a less stressful experience.

The difference was one of Systems Thinking. The system at Geneva was designed to speed the security process, eliminate bottlenecks and make thing easy for the customer. The system at Leeds-Bradford did the opposite.

If we employ Systems Thinking to our Business Processes, adopting the spirit of Kaizen, we will encourage the smooth flow of people and materials to aid maximum efficiency and process capability. If we ignore the system and blame the individual we will never achieve maximum efficiency & are doomed to fail.



Follow projectsguru on Twitter

View Chris Robinson's profile on LinkedIn

; Keep up to date by becoming a  facebook

project managers and business consultants