One doc tagged with "Reliability Risk"

Conducting systematic reviews of work done.

Managing and maintaining configuration settings of the software.

The practice of forecasting, planning, and managing the demand for resources to ensure that the best use is made of them.

Continuous observation and tracking of a system, team or person, perhaps with respect to performance, security or availability.

Ensuring backup systems are in place to prevent failure.

Deploying the software to production.

Identifying and fixing defects in the software.

Two developers working together on the same code.

Designing the high-level structure of the software.

Defining the Minimum Viable Product, planning development priorities or schedules.

Writing and running tests for individual units or components of the software.

Testing combined parts of the software to ensure they work together.

Quantitatively evaluating the software against benchmarks along some defined dimension.

Testing to ensure the software performs well under expected workloads.

Testing to ensure new changes do not adversely affect existing functionality.