This process is meant to help you determine what their requirements are and what should be prioritised, and to design a solution. This is a bit different to the consulting engagement phases and is more customer and solution-focused.
The stages are:
- Requirement elicitation
- Gap analysis
- Prioritisation, categorisation and scope
- Solution design
- Design considerations
Requirement elicitation. This occurs after the project plan has been finalised and should involve plenty of communication. Hold requirements workshops to identify pain points and requirements.
Gap analysis. This is about identifying:
- ‘As is’ business processes
- ‘To be’ business processes
When you have these you have identified the gap, which is useful for getting them to where they want to be.
Requirement prioritization. Requirements, once gathered, are prioritised according to urgency and importance. Generally high, medium and low are the grades.
- High priority requirements are ‘must have’ and included in the contractual part of the statement of work
- Medium priority requirements may be pushed to the next phase of the project depending on time
- Low priority requirements are ‘nice to have’ and usually pushed to next phase
Requirement categorisation. Useful to categorise requirements to make the project more comprehensible.
Requirement scope. Basically, you want to determine if the requirements are within or beyond the scope of the project. Or in other words is it related to the objective of the project and within the expectations of work required to fulfill.
Solution design. This is about creating a solution design document. This document should outline the system specifications which would fulfill customer requirements. Can have different sections.
Design considerations. This is about identifying whether the solutions will be created:
- Programmatically, or
- With a third party app