Related Content
 |
Application Release Automation: Why the QA Pro Should Care The speed of testing depends on a consistent software release process that can provide critical information when reporting issues. QA pros will benefit from a new set of DevOps tooling called application release automation, which drives continuous release deployment and provides visibility about what was deployed. |
|
 |
During Times of Major Change, Keep People Informed During times of major change, readily available information can help reduce the fears of those affected about what it means for them. If you’re involved in implementing change, it’s wise to keep people informed—not just about the change itself, but also about its impact on processes, responsibilities, and expectations. |
|
 |
What's in the Winter 2018 Issue of Better Software Magazine As Better Software magazine continues to publish articles that propel our industry forward with great tips and techniques, TechWell sees the future focused on continuous processes. Three of this issue's feature articles will help you improve how enterprise software is planned, developed, validated, and released. |
|
 |
An Agile Approach to Change Management Many organizations are reluctant to introduce new tools or technologies, or even to update existing ones. The reason is often framed in terms of risk management, but agile teams already have the tools to manage the risk of change: testing and experiments. These approaches together eliminate gaps in risk identification. |
|
 |
Continuous Exploratory Testing: Expanding Critical Testing across the Delivery Cycle Continuous testing entails executing automated tests to obtain rapid feedback on business risks. Where does that leave exploratory testing? Obviously, it doesn’t make sense to repeat the same exploratory tests across and beyond a sprint, but exploratory testing can be a continuous part of each software delivery cycle. |
|
 |
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. |
|
 |
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? |
|
 |
Something to Remember When Managing Change at Work Grieving is usually associated with the loss of a loved one, but it’s equally relevant to loss triggered by changes in the workplace. If you are introducing or overseeing a change, it’s a mistake to belittle people’s reaction to the loss or excessively tout the benefits of the new way. Be sensitive to those affected. |
