-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
all guidance interated to remove reference to alpha and beta peer rev…
…iews
- Loading branch information
1 parent
f95dcc5
commit 9783596
Showing
9 changed files
with
170 additions
and
168 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
33 changes: 12 additions & 21 deletions
33
app/views/service-assessments/complete-peer-review-report.html
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,50 +13,34 @@ | |
|
||
A discovery peer review is a 2-hour informal review of a team's work in the [discovery phase](https://www.gov.uk/service-manual/agile-delivery/how-the-discovery-phase-works). | ||
|
||
|
||
|
||
It's a way to get feedback and recommendations at the end of this phase. All discoveries in DfE are required to have one. | ||
|
||
|
||
|
||
It's not an assessment. There are no assessments at discovery. | ||
|
||
|
||
|
||
[Book a discovery peer review.](/book) | ||
|
||
|
||
|
||
## Why have one | ||
|
||
|
||
|
||
A discovery peer review will give reassurance to confirm whether you: | ||
|
||
- have understood what the problem is and priorities for the team | ||
- should move into the alpha phase | ||
|
||
|
||
|
||
After the review, the team will get a report with practical recommendations, and advice. It will not result in a pass or fail. It will not stop a team from progressing. | ||
|
||
But remember, if research shows that it's better to stop at the end of discovery, this is not a failure. The team will be saving time and money that could be better spent elsewhere. | ||
|
||
|
||
|
||
### What a team gets out of having a review | ||
|
||
If the assessors have recommendations for the team, these will be detailed in the report. The team can then decide on how they want to act on the recommendations. This could mean having a follow-up call or a workshop. | ||
|
||
Use the report to the team's advantage. Communicate recommendations with stakeholders or use it to prepare for the next phase of delivery. | ||
|
||
|
||
|
||
## When to book | ||
|
||
When you start your discovery, you should plan to [book your peer review](/book) so that it happens near the end of discovery. | ||
|
||
However, you should request this at least 5 weeks in advance so the service assessment plus team has time to arrange a panel. | ||
You should request this at least 5 weeks in advance so the service assessment plus team has time to arrange a panel. | ||
|
||
## What to prepare for a discovery peer review | ||
|
||
|
@@ -79,7 +63,9 @@ | |
|
||
### After you request the peer review | ||
|
||
You'll receive an email with next steps. This includes how to share links to artefacts for the panel to read. For example, Lucid boards, docs, or slide decks. You can add links to work in progress; it doesn't need to be finished, it just gives the panel an idea of the discovery. | ||
You'll receive an email with next steps. | ||
|
||
This includes how to share links to artefacts for the panel to read. For example, Lucid boards, docs, or slide decks. You can add links to work in progress, it doesn't need to be finished, it just gives the panel an idea of the discovery. | ||
|
||
### One to 2 days before | ||
|
||
|
@@ -93,21 +79,47 @@ | |
|
||
See an [example agenda](/service-assessments/run-peer-review#example-discovery-peer-review-agenda). | ||
|
||
|
||
|
||
### After the discovery peer review | ||
|
||
The panel will meet after the peer review to discuss observations. | ||
The panel will meet to discuss observations. | ||
|
||
They'll complete the report and share it with the team approximately 3 working days after the review takes place. | ||
|
||
The report will include what the team has done well and recommendations that consider the first 7 points of the [Service Standard](https://apply-the-service-standard.education.gov.uk/service-standard). | ||
## Your discovery peer review report | ||
You'll receive an email with a link to the report up to 7 days after the discovery peer review. | ||
|
||
The report will include what team has done well, plus recommendations that consider the first 7 points of the [Service Standard](https://apply-the-service-standard.education.gov.uk/service-standard). | ||
|
||
The panel will support the team with any recommendations made. | ||
|
||
### Review recommendations as a team | ||
|
||
If your report has recommendations, you could: | ||
|
||
- consider stopping work or revisiting the problem space | ||
- escalate issues or problems to the senior responsible officer or senior leadership team | ||
- contact the lead assessor or relevant head of profession for support to plan next steps | ||
- plan how to demonstrate actioning recommendations at an alpha or beta assessment. [Apply the Service Standard in DfE](/) can help with this | ||
|
||
### Accept or challenge the report | ||
|
||
Once you've read the report, the product or delivery manager has 10 working days to accept or challenge it. | ||
|
||
### To accept the report | ||
|
||
If the team agree with what's written, you can accept the report on [your dashboard](/book) in the Service assessment service. | ||
|
||
### To challenge the report | ||
|
||
Arrange next steps and email the service assessment plus team at [[email protected]](mailto:[email protected]). | ||
|
||
The assessor panel will support the team with any recommendations made. | ||
They'll set up a meeting for the team with the panel. You'll agree any changes to the report with the panel before you accept it. | ||
|
||
Go to [your peer review report](/service-assessments/peer-review-report) for details about receiving a report and acting on recommendations. | ||
## What happens next | ||
|
||
Once the report has been accepted, it will automatically be published in the [reports section](/reports/) of the service. The team can then follow any recommendations and next steps. | ||
|
||
Depending on the outcome, the team may be asked to provide evidence of any actions they've taken to implement recommendations. | ||
|
||
|
||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -12,13 +12,13 @@ | |
|
||
{% markdown %} | ||
|
||
All services need to have a service assessment. Getting assessed is a condition of your Cabinet Office | ||
In DfE, all services need to have a service assessment. Getting assessed is a condition of your Cabinet Office | ||
spend approval. | ||
|
||
This includes: | ||
|
||
- non-transactional | ||
- transactional, and | ||
- transactional | ||
- non-transactional, and | ||
- information services | ||
|
||
Service assessments happen at the end of alpha, private beta and public beta phases. If you are in the discovery phase, | ||
|
@@ -44,24 +44,27 @@ | |
|
||
## DfE panel service assessment | ||
|
||
You need a DfE panel assessment if your service or product is transactional and will have less than 100,000 transactions per year. | ||
You need a DfE panel assessment if your service or product is: | ||
|
||
- transactional and will have less than 100,000 transactions per year | ||
- non-transactional | ||
- an information service | ||
|
||
The panel will be made up of people from across professions in DfE. | ||
|
||
Book a DfE panel service assessment by emailing the <a href="mailto:[email protected]">service assessment plus team</a>. | ||
|
||
## Peer reviews | ||
|
||
You need a peer review if your service or product is: | ||
You need an end-of-phase peer review if your service or product is in the discovery phase | ||
|
||
- in the discovery phase | ||
- a non-transactional service, for example a guidance or information service | ||
|
||
The outcome of a peer review will be a report sharing what the team has done well and what they need to improve. | ||
The outcome of a discovery peer review will be a report sharing what the team has done well and what they need to improve. | ||
|
||
However, you can choose to have a DfE panel service assessment if you think your service will benefit from being assessed more formally against the [Service Standard](/service-standard). | ||
Book a discovery peer review by emailing the <a href="mailto:[email protected]">service assessment plus team</a>. | ||
|
||
If you would like a mid-phase peer review at the alpha or beta phase, you can arrange one as a team with DDaT colleagues. | ||
|
||
Book a peer review by emailing the <a href="mailto:[email protected]">service assessment plus team</a>. | ||
They can be a useful way to get feedback and recommendations as you prepare for a service assessment. | ||
|
||
{% endmarkdown %} | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.