You Can’t Rush Agile Change
Why Software Testing Is Key to DevOps
Too often, organizations try to rush agile change. It is usually because they want to see the business benefits of agile as quickly as possible. Unfortunately, change doesn’t work like that—you can’t rush it. In fact, trying to change too fast often results in no change at all. Here are some examples to avoid.
What is agile, part 3
One of the major reasons organizations adopt DevOps practices is to accelerate delivery of software to production. However, many fail to include quality components in their practices. Continuous deployment without quality is just delivering continuous bugs. Here’s why software testing is an essential part of DevOps.
Implementing Continuous Delivery in the Federal Government
For part 2: https://www.coveros.com/what-is-agile-part-2/ For part 1: https://www.coveros.com/what-is-agile-part-1/ Where I have seen agile implemented properly, practices were followed that were non-intuitive but effective. A couple examples will help: It is a known statistic (2015 Chaos report) that the smaller the project, the higher the likelihood of success – by a significant margin. ” It was […]
Agile and DevOps Bring the Focus Back on Quality
Federal agencies generally have more regulation, slower processes, and a command-and-control style of bureaucracy. How does it work when trying to foster agility and implement a continuous delivery model? Gene Gotimer relates his experiences and challenges with encouraging a culture change in federal government.
Continuous Security in Agile Development
I’ve had the privilege (and the many challenges) of working in IT for more than three decades. Early in my career I tended to accept things as they were presented, following the techniques, processes, guidelines, and approaches I was taught by my peers and managers. As I gained experience and wisdom, I became a better independent thinker and started to connect the dots and ask questions.
What is agile, part 2
The word continuous gets thrown around a lot when talking about agile and DevOps. One area that often doesn’t get enough attention is how to continuously build, test, and deliver secure applications.Just like for quality, you can’t test security in, so you need to have a plan for how to build it in from the ground up. Here are some tips on how to do that.
Continuous Improvement Activities beyond the Retrospective
(for the first part, see https://www.coveros.com/what-is-agile-part-1/ ) Strategies for greater effectiveness had been discussed and applied since the earliest days of software development. What set agile apart was the shared understanding on these techniques by some of the most mindful and collaborative developers of their generation. They convened to decide on the intersection of their […]
The Agile Manifesto Principles: Self-Organizing Teams
One of the principles behind the Agile Manifesto is “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.” Unfortunately, many associate that practice with performing team retrospectives at the end of a sprint, or periodically in kanban. But if you seek to build a high-performing team, there are more improvement activities you should consider adopting.
The Value of Security Testing in QA
The best architectures, requirements, and designs emerge from self-organizing teams. The cultures that are trying to adopt agile are usually command-and-control, because most organizations are. This means that there’s a boss who tells their subordinates what to do, and then those subordinates tell their subordinates what to do. Agile attempts to flip that script upside […]
For many organizations, traditional testing groups are separated from the IT security group. But having traditional testers perform some security testing efforts is a great way of achieving a balanced approach to shifting left while being mindful of staffing and budgetary challenges. It also has some great advantages.