Related Content
 |
Think through System Changes to Anticipate Quality Issues When you replace or significantly modify components of a larger system, too frequently we focus on whether the code we are building functions correctly. This is important, but it’s also short-sighted. It’s easy to introduce errors because we are changing interactions. Coding bugs are only one quality problem. |
|
 |
5 Tips for Choosing Your First Agile Project When transitioning to agile, applying agile methods to a single project is a great way to get started. However, care must be taken to ensure the project you choose is appropriate—it shouldn't be too large, take too long, or be too risky. Here are five tips to help you pick the right project for your agile pilot. |
|
 |
Driving Continuous Improvement to the Entire Organization In traditional agile approaches, retrospectives are valuable to team improvement. However, when teams encounter organizational issues beyond their control, such as project structure, interorganizational communication, or resources, it's more difficult. Here's how to expand continuous improvement to the whole company. |
|
 |
Integrating Code in Agile Software Development: Start with the Goal in Mind Agile software development works because of continuous feedback at various levels, and the most important form of feedback is working software. One way to achieve rapid feedback is to integrate and deploy code frequently. Rather than starting with the process, first decide what "frequently" should mean for your team. |
|
 |
Using Feature Flags to Boost Testing and Deployment A feature flag is a configuration setting that lets you turn a given feature on or off. There is no need for a feature to be complete before you can start testing—as soon as the first piece of code is merged, you can turn the flag on in your test environment and begin. This also reduces risk. Do you use feature flags? |
|
 |
Testers, It’s Time to Become Best Friends with Your Developers If you want to create software in the modern era and maximize the skills of your entire team, you can’t do things the way they’ve always been done. And going back to the late-stage testing example, you just can’t do things the traditional way anymore. |
|
 |
The Role of Testers on Agile Teams Some agile teams have so fully embraced the idea of the development team owning quality that they don't hire anyone with a testing background, instead making software engineers responsible for all phases of quality. Still, testers add value to a team in many ways that don’t involve test execution. Where do they fit in? |
|
 |
3 Major Continuous Delivery Hurdles Teams Need to Overcome Teams that leverage continuous delivery and continuous integration are playing an entirely different game than software teams of the past—instead of mapping out this major, ridged timeline, data is being both gathered and used more frequently (and effectively) than before. |
