• DevOps Delivers, but Requires New Skills – And a Whole New Mindset

    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?

    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…

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

  • Digitization or Digital Transformation?

    Digitization or Digital Transformation?

    “What is the difference between automation and digitization?” “What is the difference between digitization and digital transformation?” I often hear from people. I answer briefly, taking into account the differences in people’s knowledge. Automation: Efficient methods to eliminate repeated processing and human error from “manual and toil” states. Digitization: Making it possible for computers to…

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