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

by Railsware

Slide 1

Slide 1 text

How to structure your input so it becomes a manageable scope? Artur Hebda Railsware Labs

Slide 2

Slide 2 text

We build client and own products.

Slide 3

Slide 3 text

We build client and own products. Consultancy

Slide 4

Slide 4 text

We build client and own products. Consultancy Labs

Slide 5

Slide 5 text

We build client and own products. Consultancy Labs

Slide 6

Slide 6 text

We don’t do what client wants. We do what client needs.

Slide 7

Slide 7 text

Lead Engineer => Product Manager

Slide 8

Slide 8 text

Source: YouTube

Slide 9

Slide 9 text

Let’s get to know each other. Name? Role? Hope?

Slide 10

Slide 10 text

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

Slide 11

Slide 11 text

Where do you keep ideas/suggestions?

Slide 12

Slide 12 text

How many open tickets do you have in backlog?

Slide 13

Slide 13 text

Source: Ashim D’Silva Unsplash

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

Product structure discovery

Slide 16

Slide 16 text

Image: http://www.orlandospencer.com Product is a never consistent set of features

Slide 17

Slide 17 text

Split product into feature components Contextual, not functional Tree-like structure - divide & conquer

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

Source: Google Maps in Google Play

Slide 20

Slide 20 text

Source: Google Maps in Google Play

Slide 21

Slide 21 text

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 - ...

Slide 22

Slide 22 text

Functional labels - Design - Engineering - Architecture - Maintenance - Performance - Tech Debt - Back-end - Front-end - Marketing - Sales - Support - ...

Slide 23

Slide 23 text

Product is more... - Product Marketing - Market Research - Analytics - Customer Development - Experiments - ... - Product Development - Feature components... - Functional labels… - ...

Slide 24

Slide 24 text

Company is more... - Google Maps - Product Marketing - Product Development - ... - Google Translate - ...

Slide 25

Slide 25 text

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

Slide 26

Slide 26 text

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

Slide 27

Slide 27 text

Source: Uber in Google Play

Slide 28

Slide 28 text

Discussion of results

Slide 29

Slide 29 text

Structure-based input grooming

Slide 30

Slide 30 text

Working with inputs is hard...

Slide 31

Slide 31 text

https://goo.gl/Agc71c

Slide 32

Slide 32 text

Customer Feedback Public Private INPUT as a single source of truth

Slide 33

Slide 33 text

Customer Feedback Product Team Stakeholders INPUT as a single source of truth

Slide 34

Slide 34 text

The only effective solution we have found is to gather them in one place.

Slide 35

Slide 35 text

https://goo.gl/uKiGaV

Slide 36

Slide 36 text

That’s why you need structure.

Slide 37

Slide 37 text

No content

Slide 38

Slide 38 text

Customer Feedback Product Team Stakeholders INPUT as a single source of truth

Slide 39

Slide 39 text

Customer Feedback Product Team Stakeholders INPUT as a single source of truth Context #1 Context #2 Context #3

Slide 40

Slide 40 text

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

Slide 41

Slide 41 text

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!

Slide 42

Slide 42 text

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

Slide 43

Slide 43 text

Slide 44

Slide 44 text

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

Slide 45

Slide 45 text

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 :)

Slide 46

Slide 46 text

Discussion of results

Slide 47

Slide 47 text

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

Slide 48

Slide 48 text

BONUS : How to go from pen and paper into digital toolkit? Case study : JIRA

Slide 49

Slide 49 text

2 projects JIRA projects across entire Railsware : Input and Roadmap

Slide 50

Slide 50 text

3 years Time we spent using and improving Input as an approach

Slide 51

Slide 51 text

4500+ Created inputs

Slide 52

Slide 52 text

825 Contexts

Slide 53

Slide 53 text

Input flow

Slide 54

Slide 54 text

No content

Slide 55

Slide 55 text

No content

Slide 56

Slide 56 text

No content

Slide 57

Slide 57 text

No content

Slide 58

Slide 58 text

No content

Slide 59

Slide 59 text

No content

Slide 60

Slide 60 text

Organisation Map

Slide 61

Slide 61 text

Context from OrgMap => component and quick filter in JIRA

Slide 62

Slide 62 text

No content

Slide 63

Slide 63 text

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