Closed kevwalsh closed 3 years ago
As a CMS help desk, i have an establish set of fulfillment request process
A hypothesis may depend on a spike ticket to be completed.
We believe that _thissolution will achieve _thisoutcome. We'll know that to be true when this measurable outcome occurs.
Which CMS design principle is at play?
(How will these assumptions be validated?)
This is particularly relevant for feature launches, or for making changes to the content model that require front end changes as well.
[ ] Spike task, with some of the following attributes:
Identify the baseline against which we will measure improvements
Ideation (sketching, cross-displinary meeting of minds around how the problem may be solved)
Analysis of the drupal landscape
Possible implementation(s)
Proof of concept or prototype
UX writing discovery
[ ] User research
[ ] Design
[ ] UX writing
[ ] Usability testing (eg with a prototype or other design stimula)
[ ] Implementation
[ ] Documentation (What needs changing or adding to the documentation?
[ ] Product release notes (How will we describe this feature to CMS users?)
[ ] Training (Will any users require additional training?)
[ ] Metrics (How will we measure any improvements)
Please leave only the team that will do this work selected. If you're not sure, it's fine to leave both selected.
Platform Team
Sitewide CMS Team
is this a duplicate of #3543
Background
User Story or Problem Statement
As a CMS help desk, i have an establish set of fulfillment request process
Affected users and stakeholders
Hypothesis
A hypothesis may depend on a spike ticket to be completed.
We believe that _thissolution will achieve _thisoutcome. We'll know that to be true when this measurable outcome occurs.
Design principles
Which CMS design principle is at play?
Assumptions
(How will these assumptions be validated?)
Acceptance Criteria
Runbook
This is particularly relevant for feature launches, or for making changes to the content model that require front end changes as well.
Possible tickets to create for this epic
[ ] Spike task, with some of the following attributes:
Identify the baseline against which we will measure improvements
Ideation (sketching, cross-displinary meeting of minds around how the problem may be solved)
Analysis of the drupal landscape
Possible implementation(s)
Proof of concept or prototype
UX writing discovery
[ ] User research
[ ] Design
[ ] UX writing
[ ] Usability testing (eg with a prototype or other design stimula)
[ ] Implementation
[ ] Documentation (What needs changing or adding to the documentation?
[ ] Product release notes (How will we describe this feature to CMS users?)
[ ] Training (Will any users require additional training?)
[ ] Metrics (How will we measure any improvements)
CMS Team
Please leave only the team that will do this work selected. If you're not sure, it's fine to leave both selected.
Platform Team
Sitewide CMS Team