File-by-file merge request diff navigation Product Discovery Sprint
The Product Discovery Sprint
The Product Sprint will last 5 days (12-14, 19-20 August 2019). Through each day of the sprint, we will progressively get closer to an actionable design solution. This sprint will include 1 PM, 1 Designer, 1 BE engineer, and 1 FE engineer.
The Problem
Improve the performance and usability of merge request diff navigation by implementing a file-by-file diff navigation mode.
| Mockup |
|---|
 |
Tools
TBD
The Plan
Participants in the discovery sprint will have at least 4 hours overlap each day, so that there can be multiple meetings per day.
Planning/Kickoff
- 1 hour: Day 1 will begin with a planning call to discuss problem (diff navigation performance and usability for large merge requests), and logistics of thee week.
- What is each person's work style? How can we make it work together?
- 1 hour: Think Big/Think Small exercise
- Think Big: what's the dream solution if we had three months to solve the problem with enough UX, frontend and backend to make anything possible?
- Think Small: focusing back on the present, what is that absolute minimum needed to address the state problem? Which parts of the problem to we solve first? In the second and third iterations, what are the most impactful changes? How can we measure success?
Iteration 1 (Core): TBD
Goal: TBD during kick off
Validation plan: TBD
Iteration 2 (Core+)
Goal: TBD during kick off
Validation plan: TBD
Iteration 3 (Core++)
Goal: TBD during kick off
Validation plan: TBD
Iteration 4 (Metrics/Polish)
Goal: TBD during kick off
Validation plan: TBD
Iteration 5 (Polish)
Goal: TBD during kick off
Validation plan: TBD
Post-delivery testing
After the conclusion of the discovery sprint, we should get feedback from 5 external customers:
- TBD
- TBD
- TBD
- TBD
- TBD
Desired Outcomes
A beta quality MVC, that can be shipped in 12.3, subject to code review and testing.