risk management | TechWell

risk management

Risk management checklist A Checklist for Managing Go-Live Decisions and Risks

If you have to replace a complex existing data system in production, decisions about when and whether to go live should be treated with gravity and care. One process that can help keep you honest is developing checklists that describe very clearly what is expected to be accomplished and verified at each milestone.

Payson Hall's picture
Payson Hall
Locks on a red fence, photo by Jon Moore A Definition of Done for DevSecOps

In DevOps, we have a software delivery pipeline that checks, deploys, and tests every build. The goal is to produce a viable candidate for production, so we have to look at many different aspects of quality, including security. To be sure we hit all the crucial marks, we should have a definition of done for DevSecOps.

Gene Gotimer's picture
Gene Gotimer
Climbing tower on a playground, photo by Basil Lade 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.

Steve Berczuk's picture
Steve Berczuk
Plane coming in for a landing, photo by Sebastian Grochowicz 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.

Payson Hall's picture
Payson Hall
Arrows pointing to old way and new way 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.

Steve Berczuk's picture
Steve Berczuk
Arrow expanding testing 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.

Ingo Philipp's picture
Ingo Philipp
On-off switch 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?

James Espie's picture
James Espie
Cyber security 4 Cyber-Security Actions to Protect from Attacks

With breaches and computer hacks, companies constantly need to keep information safe. If there are loopholes in your security process, you are putting your product—and customers—at risk. Here are four actions every security-conscious company and individual should implement to avoid becoming a victim of cyber attacks.

Ray Parker's picture
Ray Parker