-
·
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…
-
·
The Importance of Behaviour in a DevOps Environment
The behavior of people shows the culture of an organization. Which behaviors can you define, which would fit a DevOps environment? Did you think of these terms? These are all relevant statements, but none of them is real behavior. Try to define behavior in terms of “what you see someone do or hear someone say.”…
-
·
Using the Stakeholder Map to Guarantee Involvement in the Process
One way of analyzing your stakeholders is the Stakeholder Map. Plot your stakeholders on a graph, considering their influence on and their interest in your initiative. A Stakeholder Map is a tool that helps you categorize stakeholders into the following four categories: The position of stakeholders on the map depicts their value to the project.…
-
·
Why the Cultural Element of DevOps Is Crucial
The core of the DevOps culture is the emphasis on service. The following figure shows how this mindset helps to deliver a high-quality product. The focus on service is not just limited to ensuring a product is available for use by the customer. A service mindset ensures that a high-quality product is not only available…
-
·
Story Maps and Business Value
The two approaches to developing products or services are incremental and iterative. The following figures depict the difference between the two approaches. In an Agile DevOps environment, both approaches are used to develop a product. You might need to build upon the existing parts or functionality (iterative). There can also be a situation where you…
-
·
Multitasking Impact on Productivity in a DevOps Environment
Multitasking makes each and every task to take a longer time to complete than required. The cause of delay is due to the time lost when switching between multiple tasks, as shown in the following figure. According to Gerald Weinberg (Quality Software Management: Systems Thinking), there is a loss of around 20% of the total…