4 docs tagged with "Internal Model Risk"

Demonstrating the software to stakeholders.

Creating documentation to describe the software and its use.

Conducting regular reviews to discuss what went well, what didn't, and how to improve.

Conducting systematic reviews of work done.

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

Using machines to perform repetitive tasks.

Two developers working together on the same code.

Examining systems to understand how they work and how they should change.

Managing relationships and communications with stakeholders.

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

Quantitatively evaluating the software against benchmarks along some defined dimension.

Testing to ensure the software performs well under expected workloads.

Having a customer representative available onsite for feedback.

Risk associated with getting messages heard and understood and the transfer of information.

The use of metrics as a cause of Internal Model Risk

Internal Model Risk threats caused by broken systems.