Epics design ideation - 馃搫 Issue refactor
Purpose of this issue
This issue can house discussion or resources as we ideate on Epics within the Issue Refactoring project.
To keep in mind
Scope
What is the ideal Epic view?
- Overall deliverable: What is the general structure/IA of an Epic?
-
Plan: Document Epic feedback, use case, jobs -
Plan: Synthesize prior research and create actionable insights -
Plan: Evaluate and document usability insights -
Plan: Document Epic object job/use cases -
Plan: Prioritize Epic objects -
Plan: Validate structure
-
- Which objects need to be included to achieve consistency across issuables?
-
Plan: Evaluate inventory of objects across issue types and identify inconsistencies -
Plan: Document objects required to get job done in epics (stretch: across Requirements, Test Cases, Issues) -
Plan: Prioritize Epic objects -
Plan: Rank potentially configurable objects
-
- Deliverable: How do we optimize the user's general flow as they interact with the view from a usability perspective?
-
Plan: Evaluate and document usability insights and prioritize actionable insights -
Plan: Evaluate and document insights from competitive analysis -
Plan: Document potential solutions based on object priority for roadmapping future iterations
-
- Deliverable: How might we address impactful UX debt or user frustrations pertaining to the view?
-
Plan: Validate & document improved interactions of top prioritized objects
-
- Deliverable: What happens when the view is transformed? (Existing: Closed New: Moved, demoted, cloned/duplicated)
-
Plan: Document user flows -
Plan: Validate & document optimal experience
-
Objects included in each view
- Deliverable: 1. What are the highest priority objects? 2. What objects must be included by default? 3. What objects could be scoped out? Or potentially configurable?
-
Plan: Evaluate ranking exercises -
Plan: Validate improved structure and experience -
Plan: Document objects across views (stretch: Requirements, Test Cases, Issues)
-
Relationships of objects
- Deliverable: How might we ideally display the hierarchy or relationship of work items within a view (improving our current state)? 1. Epic <> Epic 2. Epic <> Issue 3. Issue <> Issue (we don't allow for great stack ranking here)
Edited by Alexis Ginsberg