-
·
Skills to Remain Relevant in 21st Century and Enabling High-Performance Digital Organizations
To stay relevant in today’s fast-paced and ever-changing world, organizations are looking for ways to decrease their time to market and become more customer-centric. This requires new ways of working like Agile, DevOps, and new 21st century skills. The Agile/DevOps movement began in 2001 and so far has been largely IT-driven. When you look at…
-
·
From Slogans and Buzzwords to Behaviors and Value
The CEO rubs his throbbing temples. Digital disruption is giving him a headache. All this talk about digital transformation and how competitors are stealing business away with their new ‘DevOps’ ways of working – whatever that ‘DevOps’ means. Never mind all of this transformation stuff, he’d be happy if IT could start delivering what we…
-
·
How DevOps and CI/CD Contribute to Antifragility
I started exploring DevOps back in 2013. After my upstream journey from programming via designing and requirements engineering to strategy development, I started my downstream journey to examine how strategy can be implemented more quickly and what obstacles need to be overcome in order to do so. I came across literally all the waste that…
-
·
Building Cross-Functional Teams in the DevOps Transformation Process
Being able to position members with cross-functional competencies within the team is one of the critical issues for Agile and DevOps transformation processes. However, no matter how much time you spend, it is unlikely that each member of the team will have every competency needed at the top level. In order to create high performing…
-
·
Why You Should Improve the Flow of Work
The most important aspect of working with DevOps principles is to improve the flow of work through the organization. In the course of automating, solving problems, increasing deployment frequency, and shortening processes, you need to inevitably remove waste from the service creation and delivery system. As a result of removing waste, you will be able…
-
·
How to Define DevOps
Hundreds of definitions exist for DevOps. Here, we have captured three in which we highlighted essential elements by underlying them. As you can see, these elements stand for something larger than an intangible but also applicable to enterprise-wide IT improvement and continuous innovation of the IT capability. Key points: Source: DASA DevOps Fundamentals coursebook.
-
·
DevOps Delivers, but Requires New Skills – And a Whole New Mindset
DevOps ‘requires multiple teams to work closely with each other, side by side, on a day-to-day basis, to meet the significantly shrunken delivery timelines.’ Just about every organization with a functioning IT department has been attempting to finesse some variation of DevOps into its software delivery flow. When done right, DevOps is powerful stuff, and…
-
·
How Do DevOps Product Owners Actually Monitor Progress?
The team and the Product Owner have together understood and confirmed the Product Backlog. They have created the Team Backlog for the next iteration. We know that the Team Backlog consists of more than just new features to be developed. Solving incidents, answering user queries, giving advice, and carrying out operational activities are all examples…
-
·
When Do You Need More Teams to Deliver Value?
You might have found yourself asking when are more teams needed to deliver value. In a DevOps environment, we prefer teams to be as autonomous as possible. This is not always possible. In these cases, the Product Owners must coordinate the delivery of value. Teams must tune the delivery of value to one another. If…
-
·
Defining Boundaries to Ensure Team Autonomy in DevOps
The autonomy of teams is a core value in DevOps. A team can fulfill that responsibility and conduct everything necessary only by defining certain boundaries to limit responsibility. Some of the dimensions that you should consider while defining boundaries are: Dimension 1: Determining in what ways services or (parts of) the system are manageable for…
