-
·
Why T-Shaped Professionals Are Desirable
A T-shaped person has deep knowledge/skills in one area and a broad base of general supporting knowledge/skills. If you represent this depth and breadth visually, you get a “T” shape: Source: https://collegeinfogeek.com/become-t-shaped-person/ The exact details will vary from person to person. The T-shaped person is an improvement on the classic saying “Jack of all trades,…
-
·
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.”…
-
·
DevOps: A Boy Named Sue
Everyone has an opinion about DevOps. Similar to what has happened to cloud, Agile, Lean and Scrum, this unavoidably leads to cult behavior. Strong beliefs, not only on what it really is but also how it should be integrated with current organizational and technological practices, lead to fierce discussions and multipolar behaviors. But does it…
-
·
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…
-
·
Competing in the Digital Age With Lean Startup, Agile Software Development, and DevOps
To compete in the digital age, it is becoming increasingly important to move away from an activity based functional teams to multidisciplinary product teams consisting of business ( product owners, designers, UX, business analysts… ) and IT (developers, testers, security, operations …. ) folks. However, for the newly created product based teams to become successful…
-
·
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…
-
·
The Benefits & Pitfalls of Collaboration You Should Be Aware Of
The success key of any team is teamwork, and the most important behavior of teamwork is collaboration. The meaning of collaboration is working together to achieve a goal. It is the central theme for DevOps Teams. Collaboration offers a number of benefits but also brings with it a number of pitfalls if not implemented effectively,…
-
·
Getting DevOps Right (It Is Not Just About Technology, Leadership and Management Matters)
It is a truism that to realize the benefits of technology has driven change initiative the focus has to be on deliberate leadership and management of the initiative, rather than an exclusive focus on technology and tools. However, that obvious truth gets lost, in the euphoria and excitement about the latest technology, especially in technologically…
