![]() ![]() This makes the DevOps transformation easier. It's a good idea to point out some areas that are siloed. Silos are a bit like “Hydra,” the many-headed serpent or monster in Greek mythology that grew two heads for each one cut off.Įven if we break all the silos, it does not mean we communicate or work together. By definition, any project needs its own time to bloom and prosper, and by default, we humans and teams need our safe places to innovate and experiment. I genuinely believe that silos are and will be a part of any company that will ever exist. If our goal is to work together, let's define it as working together. I believe that DevOps is a path to having better software and better prospects for our business. I feel that working towards the same goals together as an organisation and having joint possible motivations make for better business. I don't think we are here to break the silos in IT and software development. Is the goal of DevOps to break down silos? Or something else? If you look at it from a less binary perspective, silos at certain phases might help teams, and we need to ask ourselves and have some criteria as to when we need to destroy them and when to keep them. If we try and break those areas, we might lose those shelters of creativity. From my perspective and experience, companies and people need silos to create things before going “public” with them. What we call silos is part of the way we operate and think. I think it's a bit of a naive perception of human behaviour. But even from the core meaning of the word, we see the problem silos are designed to shelter grains or rockets, and breaking them is hard physical work. It's a great concept when you hear it first. ![]() ![]() If silos are slowing things down, then let us break the silos and set our people free. Silos can create a situation where coordination is hard or impossible, or where specific teams and departments are fighting for no good reason. If the people in development aren't passing information to the operations team, workflow quickly becomes bottlenecked and productivity suffers. Silos are developed when specific departments work as separate entities with their separate visions, goals, and responsibilities. What does ‘silo’ mean in IT and software development? Let's start with the definition of the word silo:Ī tall tower or pit on a farm used to store grain.Īn underground chamber in which a guided missile is kept ready for firing. I believe I’ve gotten a good view concerning the subject, and I would like to share it.įirst I would like to ask: can we break down silos? Is this our main goal? Is this even possible? If not, what is our primary goal when we undergo a DevOps transformation? I’ve done various assessments where we’ve learned how teams work on their software cycles what kinds of things work, and what kinds of patterns are problematic. We are a consulting company specializing in DevOps I have been breathing and living in DevOps for the last three years. Who am I, you say? I am Yair Etziony, Head of Operations for Polar Squad in Germany. I’ll define what it means in various constellations and consider its feasibility as a goal. In this article, I explore one of the essential ideas of the DevOps movement: the concept of breaking down silos in IT and software development. In the 21st century, we have the tools and experience to release reliable software in very short intervals. The idea of changing the way software is shipped and maintained has gained a considerable fanbase – for a good reason. For the last few years, DevOps transformation has been everywhere in the IT and software development world. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |