Services
Business Analysis
A requirement is useful when the delivery team and the business understand it in the same way.
Business Analysis
Make the next decision easier to assess
We clarify workflows, rules and exceptions with the people involved, then write requirements that can be reviewed and tested. This reduces the gap between a request made in a meeting and the feature eventually delivered.
Put these on the agenda
- Stakeholder requirement gathering
- Process mapping & gap analysis
- Functional & non-functional specifications
- User stories & acceptance criteria
- Requirements traceability documentation
In practice
Business Analysis: a practical example
Observe a request from the person who submits it to the person who approves it. Write down the information each needs, the exceptions and the current workaround. Review that description with both roles before turning it into requirements, so the specification reflects the whole process.
An illustrative scenario to discuss when planning your project.