-
·
How Computrain Drives Growth Using DASA’s DevOps Courses
DASA is continually developing the DevOps course curriculum and refreshing the materials. You get more than just ‘here’s the course and good luck.’ They really want to build the market together. Sjon Post, Computrain Portfolio Manager About Computrain is a leading Dutch IT training organization with a rich 40-year history and broad portfolio of digital…
-
·
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.
-
·
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…
-
·
Why Shared Accountability of Teams is Crucial for High-performing Teams
Joined team responsibility is a primary characteristic of high-performing teams. In a DevOps team, the shared responsibility for Development and Operations is also a defining characteristic. It is easy for the Development team not to be interested in the operation and maintenance of a system when handed over to another team. However, if the Development…
-
·
The Business Benefits of DevOps
We live in interesting times in which innovations emerge at an increasing pace. Many startups and new companies have completely displaced or destabilized existing industries. Many organizations have started to tear down the walls between business and IT, and even thicker walls between technical departments within IT. They have replaced their technical departments with organizational…
-
·
Developing the Right Context in Workspaces
Are you in healthy or unhealthy soil? It is human nature to behave differently in different situations. Therefore, developing the right smell or context in the workspace is essential to improve individuals for the success of the business. However, it involves changing the attitude of the people. Changing someone’s attitude is not an easy task.…
-
·
The Three Ts of DevOps
Daniel Pink’s three aspects to drive people are Purpose, Autonomy, and Mastery. The three aspects are essential elements that help individuals to carry out effective team behavior. Mastery, Purpose, and Autonomy are based upon building Trust, promoting Transparency, and stimulating Teamplay. The three elements or the three Ts of DevOps are: Source: DASA DevOps Professional…
