- List the requirements of the system
- Create an actor diagram
- List the happy path
- List the alternate paths
- Sort the requirements in p0, p1 & p2
- Further sort the requirements in essence, risk, & complexity
- Create a sequence/flow diagram for happy path
- Create sequence/flow diagram for alternate path
- Focus on the feature that is most risky and that is not blocked on something first.
- Once risk is reduced by some means (may be class diagram / flow diagram) move on to the other areas
- Try to find commonality b/w the entities of the system
- Reduce complexity of the system and features
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (1)
And don't forget to include operational reports, KPI metrics and performance analysis as first class citizens in the scope. Too often stakeholders concentrate on what they need to put in and forget about what they need to get out.