One doc tagged with "Operational Risk"

Providing guidance on how to use the software to users or developers.

Using machines to perform repetitive tasks.

Managing and maintaining configuration settings of the software.

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

Deploying the software to production.

Identifying and fixing defects in the software.

The practice of establishing and adhering to standards to ensure consistency, compatibility, and quality in software development.

Implementing and utilising specific tools in the development process.

Managing changes to systems and organisations in a systematic way.

Designing the high-level structure of the software.

Logging support issues and tracking their resolution.

The practice of exerting influence on team members to ensure tasks are completed on time and to a high standard.

Quantitatively evaluating the software against benchmarks along some defined dimension.

Ensuring the application is secure by identifying vulnerabilities.

Why is it so hard to be understood?

A lot of advice around constructing software comes back to simplicity. Why?

What prevents us working as a team? Why are distributed systems so hard?

Risk faced by depending on something else, e.g. an event, process, person, piece of software or an organisation.

Risk you face when providing features for your clients.

Risks due to the differences between reality and the internal model of reality, and the assumption that they are equivalent.