Requirements engineering
01Elicit, structure and trace business requirements through to acceptance criteria
The problem
Why programmes build the wrong solution
- 01Requirements lack traceable business needs
- 02Process decisions made in workshops are not reflected in the solution
- 03Testing confirms function but not business benefit
Scope
Scope of work
Business process analysis
02Map the current process, define the target process and agree operational changes
Data and integration
03Specify the data, interfaces, business rules and controls the solution requires
UAT and benefits
04Plan user acceptance testing, support implementation and confirm benefits after release
Ways to engage
Engagement models
Questions
Frequently asked questions
Review the business requirement
Share the programme, unresolved decision and expected benefit
Book a call