Category: Uncategorized

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

  • Leadership Starts With You

    As follow up to the successful ‘Fit for the Future’ CIO event organized by CIO Platform Netherlands and DevOps Agile Skills Association (DASA), a CEG Agile/Scrum event was organized and kindly hosted by Rabobank. One of the goals was to further explore the findings from the CIO event. As part of this follow on event…

  • Kaizen Event and Value Stream Mapping as Continuous Improvement Tools

    Continuous improvement tools can support the Kaizen or radical change mindset. Kaizen EventA Kaizen event is a structured problem-solving approach that contributes to purposeful continuous improvement within any organization. DMAIC is a problem-solving approach to facilitate continuous improvement, as shown in the following figure. The primary tasks of the various steps of the DMAIC cycle are:…

  • Why Taking DevOps “Literally” is No Solution

    To create independent and autonomous teams around services, you might be tempted to build teams with full-stack expertise as depicted in the following figure. Although this might be a better setup, it takes the DevOps approach too literally. Each team, now, needs all knowledge and skills, and reuse is almost zero. DevOps is often misunderstood…

  • DevOps: Creating High Performing DevOps Teams Starts With Product Ownership

    Says who? Last year we captured key success factors from hundreds of organizations wanting to create High Performing DevOps Teams. These success factors came from teams who participated in the Phoenix Project simulation as part of their DevOps journey. Some of these organizations were starting up and used the simulation to explore what DevOps is…

  • If You Want to Lead in DevOps, You Gotta Have Game

    As a long-time creator and facilitator of serious gaming for business – simulations, in other words – I have seen first-hand, time after time, how serious gaming provides organizations with an opportunity to shift company culture, and start to create teams where once there were silos. 3 Part Blog The dramatically different leadership needs emerging…

  • Unleashing the Power of the Community — Creating Value With DASA Members

    Key Outcomes of DASA’s First Development Workshop One of the big ideas behind starting DASA was involving the community as a guiding force for building thought leadership. Every certification body or framework owner has a different model for building best practices, but the one that we like best is one where volunteers drive the creation…

  • DevOps Demands a (Re)new(ed) Kind of Leadership

    In this, part one of a three-part blog, I share my 25 years of IT expertise (and some current research) that indicates new leadership skills — including training on the new IT way of working — necessary to meet the new demands of managing DevOps Teams. And this isn’t just for CIOs. Middle management has…