Related Content
 |
Is Your Agile Team Taking Every Opportunity for Communication? Scrum events are well-defined points where team members communicate, but they shouldn't be the only times. If you’re not considering coding, tests, and the delivery process as opportunities for a conversation, you are missing an important chance to leverage individuals and interactions, as the Agile Manifesto states. |
|
 |
Testing Your DevOps Is Just as Important as Testing Your Software Many DevOps engineers fail to test their automation code in the same way they test the software they deploy. It's crucial for software to have tests, and this should apply to infrastructure-as-code software too, if we plan to change and improve this code with no worries about breaking automation in our DevOps pipeline. |
|
 |
A Definition of Done for DevSecOps In DevOps, we have a software delivery pipeline that checks, deploys, and tests every build. The goal is to produce a viable candidate for production, so we have to look at many different aspects of quality, including security. To be sure we hit all the crucial marks, we should have a definition of done for DevSecOps. |
|
 |
The Role of the Test Manager in Agile In traditional software processes, test managers are responsible for all management aspects of their team. Agile, however, is self-directed, so teams handle all the usual duties. Still, there is a role for test managers in agile, and it’s much more strategic than it was before. Here are the opportunities for the role. |
|
 |
Accelerate Your DevOps Transformation by Focusing on Culture The toughest part of a DevOps transformation is the cultural changes required to make it successful, so to accelerate your transformation, figure out what they are as soon as possible. Explore your company's attitude toward innovation and the tools you have and how you use them, and it will make the change easier. |
|
 |
Creating an Environment That Encourages Resilience Creating environments at work that acknowledge that failures will happen—and supporting the efforts team members make to recover—can help your organization become more effective. You cannot predict every challenge, but by embracing risk and providing opportunities for people to experiment, you can be more productive. |
|
 |
What You Can Learn from Failure—and from Success Success and failure teach different lessons. Lessons from failure tend to revolve around what not to do next time around, whereas lessons from success focus on what you can do again, perhaps even better. But whether you experience success or failure, the key is to take the time to learn from what happened. |
|
 |
What's in the Spring 2018 Issue of Better Software Magazine The Spring 2018 issue of Better Software magazine is now available, and it's got a great mix of foundational basics and cutting-edge techniques. This roundup describes the featured articles about DevOps, service virtualization, Scrum, test automation strategies, and testing for the internet of things. |
