As a software architect, I've assisted in project management and filled the role of product owner. For all of these roles it is important to be familiar with the situations that most often cause software disasters. These are your most likely risks, but not all of them:
- Personnel shortfalls
- Unrealistic schedules
- Not understanding the requirements
- Building a poor user interface
- Trying to gold-plate when the customer doesn't want it
- Not controlling requirements changes
- Shortfalls of reusable, interfaced components, or microservices
- Shortfalls in externally performed tasks
- Poor response time
- Attempting to exceed the capability of current computer technology
If you don't already have one, this list is a good starting point for a project planning checklist. Additionally, you should add risks unique to your environment, industry, and project then develop plans on how to mitigate them.
Reference:
Boehm, B., "Software Risks Management: Principles and Practices," IEEE Software, January 1991.
