+ Discussion of results - Structure-based input grooming - Intro + Group work + Discussion of results - Key takeaways - BONUS : How to go from pen and paper into digital toolkit? - Case study : JIRA
- 3D - Zoom - Road state - Area classification - Street View - Places - Points of Interest - Practical Information - Reviews - Areas of Interest - Your Places - Lists - Home - Work - Search - Directions - Traffic - Transit - Flights - Arrive on time - Navigation - ...
10 minutes Google Maps example ->> - Map - Layers - Zoom - Road state - Area classification - Street View - Places - Points of Interest - Areas of Interest - Your Places - Search - Directions - Traffic - Transit - Flights - Arrive on time - Navigation
ticket - Example : bug report from user - => can be groomed right away - Multiple contexts - Example : bulk feedback - => has to be split first - Format and scope of information - #issue - #issue + #idea(s) - #dk (domain knowledge) - plain text
single most specific context - Split multi-context inputs into many single-context inputs - Optionally add functional label - Go through contexts to deduplicate inputs - Go through contexts to merge inputs into epics - NOTE: epics might span across contexts, but it’s not advised - Epics describe problem space and potential ideas - NOTE: structure might have to be changed, that’s OK!
prioritization - Streamlines content discovery - Everyone can contribute and be heard - People have great ideas - Feeling of ownership - Tech debt becomes transparent
prioritization - Streamlines content discovery - Everyone can contribute and be heard - People have great ideas - Feeling of ownership - Tech debt becomes transparent - External memory for your brain - Capture thought, write it down as input, done - Get back to it when the right time comes
30 minutes Three steps to grooming ->> - Assign all inputs to a single most specific context - Split multi-context inputs into many single-context inputs - Optionally add functional label - Go through contexts to deduplicate inputs - Go through contexts to merge inputs into epics - NOTE: epics might span across contexts, but it’s not advised - Epics describe problem space and potential ideas - NOTE: structure might have to be changed, that’s OK! - - P.S. If something bothers you about Uber, you can write and groom your own inputs :)
focus & simplifies management - Grows with us & supports step-by-step improvements - Input - Single source of information - Everyone can contribute and be heard - External memory for your brain - Grooming inputs - Assign input to the most specific context - Deduplicate inputs - Merge inputs into epics on per context basis