Agile (opens in new tab) is a way of working that encourages teams to build quickly, test what they've built and iterate their work based on regular feedback and other useful data.
Use agile principles (opens in new tab) and tools (for example, Trello, Lucid and Jira) and have processes in place that follow the governance principles for service delivery (opens in new tab).
Why it's important
By getting your service in front of real users as soon as possible you can get insights on how they use it and iterate based on what you learn.
Working this way means you're not specifying everything up front before you've developed an understanding of what users need, you will reduce the risk of delivering the wrong thing.
How to meet this standard in every phase
You'll be assessed on what you've done to meet this standard at service assessments. However, even if the service you're working on is not being assessed, it's good practice to consider how you'll meet this standard point.
Things to consider:
- how the team use agile ways of working (opens in new tab), tools and techniques
- changes to the service are based on user research feedback and testing. The children and families design history documents how they've done this
- how the team will prioritise riskiest assumptions
- evidence of decision making with senior stakeholders that allow the team to adapt and change
- evidence that governance is being managed with measurable goals
- the team has all the skills it needs at each phase of the agile lifecycle
Profession specific guidance
Each DDaT profession in DfE has their own community and guidance.
User Research Manual