Related Content
 |
3 Telltale Signs You’re Scaling Agile Too Quickly When an organization grows quickly, it puts stress on people, processes, and customers. Burnout happens, things fall through the cracks, and defects creep in. Unfortunately, many organizations try to scale agile too quickly, and that often leads to failure. Here are three of the telltale signs you're scaling too fast. |
|
 |
Building a Culture of Continuous Improvement A culture of continuous improvement means you are open to improving how you build and deliver. You don't accept the status quo; you choose how to work and feel empowered to change it if it no longer makes sense. Kevin Goldsmith gives some ideas for frameworks to adopt in order to move toward this people-first culture. |
|
 |
4 Impediments to Nurturing a Feedback-Rich Culture Being able to have open, candid conversations that fuel learning, growth, and improvement is critical to a team’s success, so it is important to look out for impediments that can get in the way of having a feedback-rich culture. Here are four common impediments to watch for, as well as behaviors you should nurture. |
|
 |
The Changing Facets of Integration Testing In the current dynamics of product development and confirming quality in the agile world, the definition (both narrow and broad), significance, and scope of integration testing have increased manifold. Rajini Padmanaban highlights the changing facets of integration testing that teams need to make note of. |
|
 |
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. |
|
 |
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. |
|
 |
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. |
