Closed ghost closed 4 years ago
After re-reading Gen's comments for the blueprint, changed the ticket to include both front & back stage, as she wanted the "front end section of the service" documented in the blueprint so we can onboard early adopters.
Andy prepared, first draft. Reviewed with Paul (July 20) and incorporated his input. Have booked another review with Paul and Gen (July 22).
Updating blueprint with feedback from first draft review with Gen & Paul.
main feedback - highlight the items that are mandatory for the EA journey. Other tools/processes that are nice to have from a user testing point of view will only be used if they are in place in time.
Updates sent to Paul, Stu & Gen
Having incorporated input from review with Gen and Paul, have booked two further reviews for this week (July27-31) - will incorporate input and declare first iteration of Service Blueprint to be done.
Describe the issue Cloud Pathfinder, OCIO and Ministries need to understand, and be able to address user expectations and requirements for managed cloud services. Ministries need to understand their share of responsibilities for compliant use of cloud services. Our stakeholders will benefit from knowing what to ask from us.
We will start with creating the front end activities, up to the point of handing access keys to ministry teams
Which Sprint Priority is this issue related to? The 'Milestone' should clearly list Sprint Priorities - which one is this issue related to?
Additional Context
Definition of done