Tag: Building High-Performance Software Teams

  • Thank You DASA Partners and Best Wishes for 2020!

    Thank You DASA Partners and Best Wishes for 2020!

    2019 was a successful year for DASA. Thanks to all of you around the world for contributing to our fast-growing DevOps community! Building on the momentum of the previous years, 2019 continued with strong growth and adoption of DASA DevOps in the global marketplace. DASA expanded its footprint into new markets and introduced new certifications…

  • When Do You Need More Teams to Deliver Value?

    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

    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

    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

    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

    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

    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…

  • Why T-Shaped Professionals Are Desirable

    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 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

    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…