Upgrade to Pro — share decks privately, control downloads, hide ads and more …

"How to structure your input so it becomes a manageable scope?" - workshop by Artur Hebda

Railsware
October 23, 2018

"How to structure your input so it becomes a manageable scope?" - workshop by Artur Hebda

Artur Hebda ran a workshop on managing inputs when creating products during the Product Development Days in Krakow, Poland.

Railsware

October 23, 2018
Tweet

More Decks by Railsware

Other Decks in Technology

Transcript

  1. How to structure your input so it becomes a manageable

    scope? Artur Hebda Railsware Labs
  2. Agenda - Product structure discovery - Intro + Group work

    + 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
  3. Contextual components - Map - Layers - Satellite - Terrain

    - 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 - ...
  4. Functional labels - Design - Engineering - Architecture - Maintenance

    - Performance - Tech Debt - Back-end - Front-end - Marketing - Sales - Support - ...
  5. Product is more... - Product Marketing - Market Research -

    Analytics - Customer Development - Experiments - ... - Product Development - Feature components... - Functional labels… - ...
  6. Company is more... - Google Maps - Product Marketing -

    Product Development - ... - Google Translate - ...
  7. Benefits of the structure - Improves communication - Common vocabulary

    - Reference points - Embraces deep focus & simplifies management - Context segregation - Responsibility split - Grows with us & supports step-by-step improvements - Restructuring is easy
  8. Ex#1 Product structure discovery Context : Uber rides Time :

    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
  9. Input types - Single context - Example : tech debt

    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
  10. Three steps of 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!
  11. Benefits of inputs - Single source of information - Simplifies

    prioritization - Streamlines content discovery
  12. Benefits of inputs - Single source of information - Simplifies

    prioritization - Streamlines content discovery - Everyone can contribute and be heard - People have great ideas - Feeling of ownership - Tech debt becomes transparent
  13. Benefits of inputs - Single source of information - Simplifies

    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
  14. Ex#2 Structure-based input grooming Context : Uber rides Time :

    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 :)
  15. Key takeaways - Structure - Improves communication - Embraces deep

    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
  16. BONUS : How to go from pen and paper into

    digital toolkit? Case study : JIRA
  17. Input Grooming GSheet App JIRA project OrgMap structure GSheet App

    Issues via Blockspring Tree of contexts via CSV Import Changed/new issues via CSV File Import