Empowering Release Product Manager and Designer to estimate the UX effort of issues
Purpose
Let's discuss how we can apply a definition of done for UX. Below you can find the Criteria for Moving Issues with UX & Engineering we identified in the current UX flow for Release Management. This is for feature proposals with UI deliverables.
Success metrics
-
KR1: Provide a documented UX DoD for Release Management by February 30, 2020 => 100% -
KR2: Apply DoD to all UX issues scheduled for 13.0 planning => 0% -
KR2: Delivery of 50% of UX issues prior to engineering planning for 13.0 => 0%
Pilot
-
Define DoD for our UX process. -
Experiment with an issue template for Release management that includes the UX DoD. @rayana to put MR together. -
Apply process during 2 milestones - @rayana & @jmeshell -
Consider UX estimation during 2 milestones -
Document lessons learned. -
Revisit process (retrospective) and iterate.
Proposed UX DoD
<details>
<summary>Click this to collapse/fold the UX DoD 🔽</summary>
#### Entry Criteria for Design
- [ ] Problem has been validated
- [ ] Has UX effort accounted for in long term cycle, _we know unknowns_
#### Criteria for UX DoD
- [ ] ~UX label is added to the issue
- [ ] User stories and acceptance criteria have been created
- [ ] Edge cases were considered
- [ ] Cross-team dependencies have been identified, if applicable
- [ ] Prototype or mock for each user story have been created
- [ ] Empty states
- [ ] Responsiveness
- [ ] If changes involve copy, ~"UI text" label has been added
- [ ] Pajamas: UI Component design have been identified
- [ ] Pajamas issue is created (new workflow)
- [ ] Marked as Ready for engineering evaluation per user story moved into ~"workflow::planning breakdown" & ~"needs weight"
#### Entry Criteria for Ready for Development
- [ ] Scope has been defined and reviewed with engineering
- [ ] User stories have been weighed and are less than **5 MRs**
- [ ] Create new issues for follow up user stories
#### Criteria for Engineering DOD ([in addition to defined process](https://docs.gitlab.com/ee/development/contributing/merge_request_workflow.html#definition-of-done))
- [ ] UX review for MRs that include user experience changes - mandatory for ~frontend that has impact to UI/UX
- [ ] Update SSOT in issues:
- [ ] Update prototypes of deliverables
- [ ] Add link to documentation
- [ ] Create new issues for follow up and open scope
</details>
Edited by Jackie Porter