Service acceptance SEAC
Managing the process to obtain formal confirmation that service acceptance criteria have been met.
Updates for SFIA 9
- There is an updated version of this skill for SFIA 9.
- Theme(s) influencing the updates for this skill: Making SFIA easier to consume (enhance readability/guidance/descriptions), Making SFIA easier to consume (new levels).
- New levels have been added at level 3.
- Content changes have been made to levels 4, 5, and 6.
- You can move to SFIA 9 when you are ready - SFIA 8 skill descriptions will still be available to use.
- Previous SFIA assessments or skills mapping may be impacted by this change.
Guidance notes
Service acceptance criteria are used to ensure that a service meets the defined service requirements, including functionality, operational support, performance, safety, security and quality requirements. Acceptance criteria include both utility/functional and warranty/non-functional tests.
Activities may include — but are not limited to:
- engaging with a variety of stakeholders and delivery life-cycle activities such as — but not limited to — external service providers, technical design, software development and project management
- implementing service acceptance practices to support iterative/agile working
- ensuring the service provider is ready to operate the new service when it has been deployed.
Levels of responsibility for this skill
| 4 | 5 | 6 |
Service acceptance: Levels 1-3
This skill is not typically observed or practiced at these levels of responsibility and accountability.
Service acceptance: Level 4
Engages with delivery teams to confirm that products developed meet the service acceptance criteria and are to the required standard.
Provides input into change control processes.
Service acceptance: Level 5
Engages with delivery teams to ensure correct products are produced in a timely fashion.
Evaluates the quality of project outputs against agreed service acceptance criteria.
Service acceptance: Level 6
Develops the organisation's approach for service acceptance, owns the transition process and defines the acceptance criteria for service transitions.
Promotes and monitors project quality outputs to ensure they are fit for purpose and fit for use within operational services.
Actively engages with stakeholders to promote awareness and compliance with service transition quality plans and processes.
Agrees the service acceptance criteria with delivery teams.
Service acceptance: Level 7
This skill is not typically observed or practiced at this level of responsibility and accountability.