Related Content
 |
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. |
|
 |
Insider Threats: What’s the Biggest IT Security Risk in Your Organization? Any modern company should give the line-of-business teams the ability to provision self-service, on-demand resources, but to ensure security, you have to do so in a way that has the necessary monitoring built in via automation. One good way is to use a cloud management platform that helps you keep your app secure. |
|
 |
On Your Software Team, Who Should Own Automation? There is a prevalent question in the software world these days: Who should be working on automation—developers or testers? Justin Rohrman says it can be everyone's responsibility. It’s more important to look at the structure of your technical team, what skill sets are available, and what the skill distribution is. |
|
 |
What’s in the Fall 2017 Issue of Better Software Magazine Better Software magazine editor Ken Whitaker highlights content from the latest issue, including articles on bridging the divide between agile and waterfall, scaling agile through empowered teams, DevOps and IoT, and continuous development. |
|
 |
Use Continuous Backlog Grooming to Refine Agile Requirements Continuous backlog grooming means systematically refining your user stories: breaking up larger stories, obtaining detailed requirements, writing the requirements in terms of acceptance criteria and acceptance tests, and sharing and refining these details with the team. Acceptance test-driven development can help. |
