One doc tagged with "Implementation Risk"

Demonstrating the software to stakeholders.

Conducting systematic reviews of work done.

Managing and maintaining configuration settings of the software.

Writing software to meet a required feature.

Identifying and fixing defects in the software.

Making use of software libraries or services as a dependency.

Making use of software libraries or services as a dependency.

Two developers working together on the same code.

Creating early models of the software to test concepts and ideas.

Revising code to improve its structure without changing its behavior.

Revising code to improve its structure without changing its behavior.

Using version control systems to manage changes to the codebase.

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

Getting formal approval for various project stages.

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.

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 new changes do not adversely affect existing functionality.

Having a customer representative available onsite for feedback.