Agile business analysis
Gathering, analysing and presenting information and user needs to enable effective product or service design decisions.
Agile Business Analysis involves:
- understanding user needs
- breaking those needs out into constituent parts
- analysing multiple solutions
- supporting the communication and delivery of a solution to meet the user needs.
Some relevant roles: business analyst, user researcher, performance analyst, designer, developer
Deconstructing user needs
- deconstructing user needs and problem statements into constituent parts for analysis and reconstruction
- separating out what is critical
- analysing component parts from all sides
- ‘reassembling’ in order to lead to viable solutions
Root cause analysis
- listening to user needs
- asking probing questions until the real need is drawn out and understood through root cause analysis
- evaluating multiple options before helping the team to settle on one solution
- communicating effectively in working meetings, using techniques such as active listening and negotiation
- tailoring communication style to suit both face-to-face and virtual settings, including web meetings and conference calls
Sharing information between workstreams
Ensuring that the wider impact of changes is understood by parallel workstreams.
Promoting stakeholder engagement during development
Articulating business and user needs to the team
- working with the development team to ensure they have a complete understanding of the business and user needs
- making sure end user perspectives are fully considered by the content and technical design team
Continuously review user needs
Helping make sure development work is continuously reviewed and iterated so that the business and user needs continue to be met by the proposed solution.
Alignment with business strategy
- understanding organisational and wider government strategic objectives
- ensuring that solutions are aligned with important priorities
- being alert to changes in strategic direction and assessing the impact of change
Designing and planning (with stakeholders) the process used to gather user needs and relevant data.
- performing analysis of user stories and making amends where necessary
- helping ensure user stories are prioritised and contributing to that process
- interpreting data from a range of sources (eg user research and performance metrics)
- working with designers and developers to ensure solutions are based on data
Mapping business processes
- creating user flows and wireframes
- mapping business processes that represent the current structure and future design of a product or service
Innovating and improving
- analysing the existing landscape with an innovative mindset
- identifying opportunities and generating ideas for continuous improvement or new solutions to meet user needs
The Service Design Manual gives a comprehensive overview of the discovery phase of projects, when you need to find out what your users need, what to measure and what your constraints are. It also includes a considerable amount of information on agile, including what is is, why it works and how to do it.