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.
Agile is still on the rise, with many organizations that have been successful at the team level looking to scale their adoption. Consequently, it's important for testers to have practical application of agile techniques. You should know how to create tests to optimize maximum test coverage, have interpersonal skills, and successfully build relationships within the team.
When a company makes the move from software as a service (SaaS) to an API-first platform, a change in mindset is required. The successful transitions come from those who shift from features to flexibility. Technology teams should look to remove constraints and broaden the possibilities of their platform by constantly exploring ways to make their platform as flexible as possible.
Prioritizing stories for an upcoming sprint can lead to confusion and miscommunication between the product owner and agile teams. But putting that exercise into financial terms, such as purchase, budget, cost, and investment—a set of words that everyone understands, no matter what their area of expertise is—gets everyone thinking about value.
You can learn all the theoretical agile principles and best practices, but you still may not be agile. To be truly agile, you must also communicate and collaborate with your team—and this means speaking up. Even if you're not a natural extrovert, there are plenty of ways you can contribute during planning, sprints, and retrospectives to make your product and process better.
If you want secure, reliable systems, you need all stakeholders actively communicating. This means involving both IT operations and developers in discussions after deployments, to ascertain if anything went wrong and can be avoided, and what went well or could be refined. Integrating your postmortems and retrospectives facilitates collaboration and improves processes.
When companies adopt agile internally, they often forget to extend the concepts and values to their partners. You have to look at your outsourced delivery components as part of the process that needs to be included as an extended team. Collaboration, reflection, and improvement is at the heart of agile, and it should look that way from the perspective of all elements in the delivery chain.
Making the transition to agile can be difficult for teams that are used to working in large groups and reporting to a single manager. Kris Hatcher suggests a new way to work: in smaller teams called code factories, which are created to stick with a specific product throughout its lifetime.
Overloaded operators exist when an operator or operation has different meanings in different contexts. This usually applies to variables and sets, but it can be true for people, too. These people try to do the work of many different roles—and usually fail. If you have an overloaded people operator, analyze the work and try to divide it up.
Being aware of risk is good project management common sense. But to address risk quickly and effectively when you encounter it, the best method is to establish clear, agreed-upon, communicated responses to risk before it even happens. Dave Browett suggests some tactics to mitigate and confront risk you can use with your team.