This piece of work has arisen to address efficiencies around the creation, drafting, testing and releasing of new exercises on the platform. Programme Office create a basic draft of future exercises in order to allocate them a reference number. Admins set up draft exercises on Staging to test them before copying across the content to the draft exercises on Production. The proposition here is to, on Production, a single lifecycle, in which the exercise is drafted, tested, approved, released, completed and archived.
User Story
As an Admin, I would like to be able to draft and test an exercise on Production, so that I have confidence everything is working correctly before final release.
Benefit(s) to users (if not already clear from User story)
As well as assurance that an exercise is working as intended, Admins will gain time efficiencies from not having to copy and paste data from Staging to Production
Ultimately, the Digital team will be able to decommission the Staging environment on Admin and Apply; one less environment to maintain/support.
Background
This piece of work has arisen to address efficiencies around the creation, drafting, testing and releasing of new exercises on the platform. Programme Office create a basic draft of future exercises in order to allocate them a reference number. Admins set up draft exercises on Staging to test them before copying across the content to the draft exercises on Production. The proposition here is to, on Production, a single lifecycle, in which the exercise is drafted, tested, approved, released, completed and archived.
User Story
As an Admin, I would like to be able to draft and test an exercise on Production, so that I have confidence everything is working correctly before final release.
Benefit(s) to users (if not already clear from User story)
Feature(s) Description
Miro Board
Acceptance Criteria
It's done when:
Definition of Done
User Testing Steps
Specify for users what is being tested (but not how to test it.)
Feature Champion
Nick