Guardrails
A framework that sets clear expectations and keeps business analysis work on track to deliver outcomes in line with standards and best practice.
Definition of guardrails
Guardrails are a framework that:
- set clear expectations
- guide delivery and decision making
- keep work on track to deliver outcomes in line with standards and best practice
Quality assurance criteria
Use the following ratings to assess guardrail compliance:
Compliant
The guardrail is fully in place, with no breaches or deviations. There is low or no risk, and expectations are met.
Partially compliant
The guardrail is partly in place, but there are gaps or inconsistencies. This creates a moderate risk and requires follow-up action.
Non-compliant
The guardrail has been breached or standards are not being met. This creates a high risk and requires immediate action.
Problem and opportunity statements
A problem or opportunity statement clearly describes an issue to resolve or an opportunity to realise. It should be:
- concise and easy to understand
- based on evidence and facts
- suitable for DDTS to develop solutions
Use this structure:
- The problem or opportunity is: [describe it]
- It affects: [users and stakeholders]
- The impact is: [describe the consequences]
Benefits and measures of success:
- Benefits: [describe the desired outcomes]
- Measures of success: [how you will measure success]
For more information, see Business Analysis Guardrails: problem and opportunity statements.
Process maps
Business analysts use BPMN (Business Process Model and Notation) to create process maps. This ensures consistency and makes processes easier to understand without relying on long descriptions.
You can discover processes using collaborative techniques and tools, such as Mural.
You must produce final process maps in Microsoft Visio, which is Defra's preferred tool for documentation and future reference.
For more information, see Business Analysis Guardrails: process mapping.
User stories
Business analysts must write user stories in a consistent format:
As a [user], I want to [action], so that I can [benefit].
User stories must also follow the INVEST principles.
For more information, see Business Analysis Guardrails: user stories.
Backlog
Business analysts define backlog items, such as user stories, ahead of each iteration. This ensures work is ready for delivery.
For more information, see Business Analysis Guardrails: product backlog.
Get support
The Business Analysis Community can help you understand and apply these guardrails.