You need to sign in or sign up before continuing.
UX Goals: Define objectives and requirements for the first iteration of this project - 馃搫 Issue refactor
Objectives
- What do you believe is the main goal of this project?
-
@cdybenko:
- align on an issue type view that brings our design and codebase together for issue types
- align on an issue type view that brings our design and codebase together for issue types
-
@cdybenko:
- What are we trying to accomplish with this project from a Product Planning perspective?
-
@cdybenko:
- enable epics to use issue types
- figure out parent/child for issue types
-
@cdybenko:
- What are we trying to accomplish with this project from a Project Management perspective (if different)?
- What are the main benefits of having both groupproject management and groupproduct planning involved? What goals should we make sure to strive for here?
-
@cdybenko:
- we need both @uhlexsis and @hollyreynolds to:
- determine which fields or widgets are necessary in the spreadsheet as this will inform product and engineering
- figure out how parenting works for issue types other than epics
- we need both @uhlexsis and @hollyreynolds to:
-
@cdybenko:
- What UX output are we hoping for at the end of this project? What is the definition of done?
- What is the "handoff" to Product Management? How might UX enable us to build a better roadmap?
- What is the "handoff" to Engineering? How might UX provide a better starting point/SSOT for refactoring?
- What output from UX will enable us to better refactor into a single vue app?
- What is the ideal end goal for the first iteration of the first iteration of this project as a whole?
- What is success and how will we define it?
- What might enable us to move into the second iteration?
Assumptions and discussion
- What does "starting from scratch and rebuilding the issue view" mean to you?
- What do you think is the main problem that all objects being a type of issue will solve?
- What are you hoping for from this project vs ideating as normal through our workflow?
- Is there anything we should absolutely not do?
Scope
馃幀 What is in scope?
- Create a list What can we reasonably complete well? What do we need to set a good foundation for future iteration?
馃洃 What is out of scope?
- Create a list What is important but might we complete in future iterations?
Considerations
- What objects are in scope? Issues, Epics- what about Requirements, test cases? What about Incidents? Feature Flags? Any item we would forsee being a issue type?
- Are we scoping this to redesigning the "view" of an object (for example, the structure of the epic page)? If it is more than this- what is expected?
Edited by Alexis Ginsberg