Risk

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

Risk is the possibility that uncertainty will adversely affect an objective, investment, or change initiative.

Risk is evaluated as a delivery concern when choosing where to begin modernization: identify what could prevent timely delivery and what consequences would follow. section 16.2.2

Assess delivery risk alongside related decision factors:

• Business value: determine what new value the opportunity creates and how it supports important outcomes. section 16.2.2
• Delivery risks: consider potential causes and consequences of missing required delivery timeframes. section 16.2.2
• Discovery and learning value versus complexity: weigh future insight against the difficulty of achieving it. section 16.2.2

Workflow automation as a first slice

A workflow automation subdomain has promised product features for high-profile customers. A scorecard compares the risk of missing delivery timeframes with the value of building those features in a modernized system rather than the legacy monolith. section 16.2.2

Figure 16.10 An example delivery risks scorecard section

Use the delivery risks scorecard to make potential causes, consequences, and timing concerns visible during modernization prioritization. section 16.2.2

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes

Frames risk through causes and consequences in a context-specific scorecard rather than prescribing a universal scoring model.

Examples

Uses a workflow automation subdomain, promised customer features, a modernization initiative, and a legacy monolith.

What you can do after

Evaluate modernization candidates by comparing delivery threats with business value and learning value.

How it connects

Connects delivery risk with business value, modernization, legacy systems, discovery value, complexity, and scorecards.

liveBookmanning.com

Read Architecture Modernization: Socio-technical alignment of software, strategy, and structure on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Investing for ProgrammersInvestment risk is the possibility that an investment will produce an unfavorable outcome, including loss or lower-than-expected returns.
• 

  liveBookmanning.com
  Software Testing with Generative AIThe possibility that an action, system, or technology will cause harm, loss, failure, or another undesirable outcome.
• 

  liveBookmanning.com
  Delivering Machine Learning Projects: From design to deploymentProject risk is the possibility that uncertainty in a project will cause adverse effects such as cost escalation, unmet targets, or failure to deliver.
• 

  liveBookmanning.com
  Functional Design and Architecture: Examples in HaskellA risk is a potential problem whose occurrence can increase the cost, delay, or failure likelihood of a software project.
• 

  liveBookmanning.com
  Data-Driven CybersecurityThe potential for loss, harm, or adverse impact arising from a threat exploiting a vulnerability or hazardous condition.
• 

  liveBookmanning.com
  Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and TerraformDeployment risk is the possibility that releasing a software change will cause failures or disruption in an application.
• 

  liveBookmanning.com
  Authorization in ActionRisk is the possibility of an unfavorable outcome or failure arising from dependence on uncertain actions or conditions.

Compare how 8 books explain risk →

Related concepts

• risk matrixmeasured by · A risk matrix is a tabular or graphical tool that classifies risk levels by combining estimated likelihood and potential impact.
• security controladdressed by · A security control is a safeguard, policy, procedure, or mechanism intended to prevent, detect, limit, or respond to security risks.
• batch sizeproduced by · Batch size is the number of items grouped together for processing or computation as a single batch.
• market riskincludes · Market risk is the risk that movements in the overall market will reduce an investment’s value.
• code coveragecontrasts with · Code coverage measures the extent to which a test suite exercises a program’s code elements, execution paths, or behaviors.

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.