In order to fully embrace agile and create an environment where individuals want to work together as a team, managers have to move from a role of dictation to one of direction and mentorship. Instead of making all the decisions, managers need to trust their team members and empower them to solve problems on their own, innovate, and fail—or succeed.
Many organizations make the same agile and DevOps scaling mistakes year after year, then attempt to rectify them by putting together a great new strategy—only to miss the reasons causing the failure. If you want to refuse to evolve and, as a result, cause your organization’s agile and DevOps transformation efforts to deliver zero business value, be sure to follow these seven antipatterns.
Leaders in agile organizations should consider adding lean techniques to their DevOps practices. Lean thinking can accelerate DevOps delivery by providing a set of processes and principles to help create more beneficial products, save money, boost productivity, reduce waste, and map to value.
Going bimodal refers to an enterprise supporting two modes of operation: the first, the stable mode, is the secure, robust, reliable one you already know. The second, the agile mode, is a fast path that exists alongside the first and allows you to get results done quickly and without much fuss while not compromising the integrity of your IT.
The ability to stay competitive by adjusting, adopting, and continuously improving is essential to survive in the business world of today. But there are a few common challenges where your intuitive responses actually prevent you from succeeding. Keep these five paradoxes in mind during your DevOps continuous improvement journey.
Agile software development methodologies grew out of lean principles pioneered in business and industry over the past seventy years, and they are now often referred to as lean’s digital counterpart. By better understanding the philosophy behind lean, developers can gain insight into agile and its uses and pitfalls, making the most of its practice for their team.
Testing professionals who are learning about agile often want to know how they can provide traceability among automated tests, features, and bugs and report on their testing progress. Here, Lisa Crispin gives an example of how her previous team worked together to integrate testing with coding and helped everyone see testing progress at a glance.
Developers realize that to meet deadlines may require assembling both proprietary and available open source software components. This article talks about exploiting benefits and managing challenges with reusing code for open source projects, open source code management tools and their integration, and leveraging managed open source software.
Agile teams are supposed to take responsibility for how they work and how they learn. But what if you need to jump-start that learning? Agile transformation is about making this happen rather than waiting for it to happen. You need to get your team to learn the technical side of agile, and soon. Here are some effective approaches.
Sarah Johnson explains the role of writing in an agile world and how to educate your team members. Remember, agile takes into account that each situation is unique, and you need to determine what makes the most sense for your particular Scrum team.