Related Content
 |
How Do We Land This Thing? Planning for Go-Live and Beyond Some project managers have little experience bringing a project in for a landing, so they can be dismayed or just blindsided by organizational change needs and stakeholders’ expectations at delivery. Here is a checklist of some commonly forgotten items to address when a project goes live, so be sure to plan for them. |
|
 |
How Testers Can Collaborate with the ScrumMaster ScrumMasters serve the team by providing facilitation and coaching, but they also have many challenges. Those in testing roles are in a good position to collaborate with the ScrumMaster to improve agile processes. Here are some ways testers can partner with, support, and assist the ScrumMaster—and the rest of the team. |
|
 |
The Relationship between Agile and DevOps Many are touting DevOps as something new and different—just like agile before it. DevOps fixes an age-old conflict between software development and operational teams, but it’s not new. In fact, the DevOps philosophy is ingrained within the Agile Manifesto. So why is DevOps viewed as something different from agile? |
|
 |
Balancing Process and Tools The limits of a tool may lead us to realize that we are not working as effectively as we can, and often, changing a tool is part of the solution. But there are good and bad ways to select a tool and how you use it. In particular there are risks when you focus first on tools before considering the problem. |
|
 |
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? |
