|
Have you fully explored what the problem-behind-the-problem is
| Ensure that you have found the "root cause" of the stakeholder pain. Often stakeholders will define solutions rather
than stating the problem they are experiencing. |
Is the problem statement correctly formulated
| Ensure you have agreement on the problem to be solved. |
Is the list of stakeholders complete and correct
| Make sure you didn't miss any stakeholders. If you did, chances are you have not heard all perspectives. |
Does everyone agree on the definition of the system boundaries
| Defining the system boundaries, what's in and what's out, is a critical step for defining the scope of work. |
Have you sufficiently explored constraints to be put on the system
| Don't forget about the non-functional requirements and constraints. These are often the largest cost driver in
development. |
Have you covered all kinds of constraints - for example political, economic, and environmental
These non-technical constraints often lead to challenges.
|
Have all key features of the system been identified and defined
| Do a completeness check, comparing the features with the problem statement, to make sure you didn't miss a critical
feature. |
Will the features solve the problems that are identified
| Are all the features really needed? Perhaps there is some room to down-scope. |
Are the features consistent with constraints that are identified
Check that conflicting requirements do not exist. If you identify conflicts, resolve them now.
|
Can a person who is not familiar with the project understand what the project hopes to achieve by reading the Vision
| The intent of the Vision is to describe the objectives of the project in terms that non-technical people, who are not
intimately involved with the project, can understand. |
|
