See also Strategies for attacking product risk.

‣: order risk reduction activities from cheapest (or rather, highest marginal economic value due to risk reduction) to more expensive.

Technical feasibility:

• Prototype to buy information
• Limit the number of new technologies, processes, people on the project.
• Scaffold project early
• Identify and Do the riskiest parts first

Schedule risk:

• Iterative development:
  • Use agile practices in a complex space
  • Make shorter iterations in an unknown space
• Flex scope
• Force priorities: cf. Implement only top 20% features
• Set and track milestones (see ‣)

Functionality not coming together:

• Scaffold project early
• Integrate and test often: CI/CD

Platform risks:

• Use only stable & simple features of the platform
• Attract experts

Alignment:

• Set clear direction