Like many in this forum, I am working in an enterprise organisation that subscribes largely to the ITIL model of service management.
A discrete team that provide guidance and sign-off for service acceptance.
A set of criteria used for service acceptance testing to ensure that an IT service meets its functionality and quality requirements and that the service provider is ready to operate the new service when it has been deployed
This is a wrapper that envelopes the entirety of the product (normally near the end of the delivery) that dictates such things as
- Documented processes (who is getting called out on a Sunday if it goes down etc)
- BAU team
This is a common constraint when attempting to deliver a Product within the Scrum Framework using the User Story pattern. It is closely linked to the idea that, in a user story, it is often hard to articulate NFR's.
Most Service Acceptance Checklist's can run to 100-150 line items. Is there a best practice for how to incorporate this list into the backlog of a Scrum Team?
Any answer that involves disbanding the ITIL Service Team is considered off topic for this question since Organisational Change is not possible at this time.