Slide 1

Slide 1 text

How to break down Lightning Talk ⚡ Niklas

Slide 2

Slide 2 text

2 This session What it means to me (mental model) What is important to me Not defining a general process Making recommendations that worked well for me in the past Doing it via example

Slide 3

Slide 3 text

3 “Breakdown” - what it means to me Given a complex requirement or goal, a breakdown is the initial step to split it into smaller manageable chunks. Each chunk should be then shaped to something to easily work on, one step at a time. Break a chunk as small as possible so that me or another person can work with each chunk and develop a working product. 1 2 3

Slide 4

Slide 4 text

4 “Breakdown” - what it means to me Given a complex requirement or goal, a breakdown is the initial step to split it into smaller manageable chunks. 1

Slide 5

Slide 5 text

5 “Breakdown” - what it means to me Given a complex requirement or goal, a breakdown is the initial step to split it into smaller manageable chunks. 1 Task A Task B Task C Task Z ...

Slide 6

Slide 6 text

6 “Breakdown” - what it means to me Each chunk should be then shaped to something to easily work on, one step at a time. 2 What How why WHY UX Thinking

Slide 7

Slide 7 text

7 “Breakdown” - what it means to me Each chunk should be then shaped to something to easily work on, one step at a time. 2 What How why WHY UX Thinking basic human needs

Slide 8

Slide 8 text

8 “Breakdown” - what it means to me Each chunk should be then shaped to something to easily work on, one step at a time. 2 What How why WHY UX Thinking basic human needs autonomy bonding competence physicality significance stimulation security popularity Sarah Diefenbach and Marc Hassenzahl

Slide 9

Slide 9 text

9 “Breakdown” - what it means to me Each chunk should be then shaped to something to easily work on, one step at a time. 2 Shape up

Slide 10

Slide 10 text

10 “Breakdown” - what it means to me Each chunk should be then shaped to something to easily work on, one step at a time. 2 double (triple) Diamond

Slide 11

Slide 11 text

11 “Breakdown” - what it means to me Each chunk should be then shaped to something to easily work on, one step at a time. 2 really understand the goal and the why

Slide 12

Slide 12 text

12 “Breakdown” - what it means to me Each chunk should be then shaped to something to easily work on, one step at a time. 2

Slide 13

Slide 13 text

13 “Breakdown” - what it means to me Break a chunk as small as possible so that me or another person can work with each chunk and develop a working product. 3 Kickoff Epic issues

Slide 14

Slide 14 text

Example

Slide 15

Slide 15 text

15 Q1/2021 KR: Camunda Modeler has Zeebe Modeler capabilities integrated and is ready to be released

Slide 16

Slide 16 text

16 1 Create an empty Epic Issue

Slide 17

Slide 17 text

17 1 Create an empty Epic Issue mark as epic issue

Slide 18

Slide 18 text

18 1 Create an empty Epic Issue mark as epic issue give few first words about the what

Slide 19

Slide 19 text

19 1 Create an empty Epic Issue mark as epic issue give few first words about the what give few first words about the why

Slide 20

Slide 20 text

20 1 Create an empty Epic Issue mark as epic issue give few first words about the what collect tasks (actual break down) give few first words about the why

Slide 21

Slide 21 text

21 1 Create an empty Epic Issue mark as epic issue give few first words about the what collect tasks (actual break down) give few first words about the why provide additional important resources

Slide 22

Slide 22 text

22 2 Start chatting OKR presentation

Slide 23

Slide 23 text

23 2 Start chatting OKR presentation Initial clarification

Slide 24

Slide 24 text

24 2 Start chatting OKR presentation Initial clarification “Internal Kickoff”

Slide 25

Slide 25 text

25 2 Start chatting OKR presentation Initial clarification “Internal Kickoff” Technical brainstorming

Slide 26

Slide 26 text

26 2 Start chatting OKR presentation Initial clarification “Internal Kickoff” Technical brainstorming Product brainstorming

Slide 27

Slide 27 text

27 2 Start chatting OKR presentation Initial clarification “Internal Kickoff” Technical brainstorming Product brainstorming There is even more (consultants, customers, community)

Slide 28

Slide 28 text

28 3 Really understand it

Slide 29

Slide 29 text

29 “Breakdown” - what it means to me Each chunk should be then shaped to something to easily work on, one step at a time. 2 What How why WHY UX Thinking basic human needs autonomy bonding competence physicality significance stimulation sicherheit security popularity Sarah Diefenbach and Marc Hassenzahl Reminder

Slide 30

Slide 30 text

30 4 Collect, collect, collect ...

Slide 31

Slide 31 text

31 5 Scope, shape and (maybe) hack ● take individual post its that are unclear or have a bigger uncertainty ● consult others ● create sketches ● do research ● hack and try something out ● ...

Slide 32

Slide 32 text

32 5 Scope, shape and (maybe) hack

Slide 33

Slide 33 text

33 5 Scope, shape and (maybe) hack

Slide 34

Slide 34 text

34 5 Scope, shape and (maybe) hack

Slide 35

Slide 35 text

35 5 Scope, shape and (maybe) hack

Slide 36

Slide 36 text

36 6 Iterate, come to an end Important: Time Boxing

Slide 37

Slide 37 text

37 7 Summarize and kick it off

Slide 38

Slide 38 text

38 7 Summarize and kick it off Provide enough context, invite anyone optionally Have a look at our docs

Slide 39

Slide 39 text

39 7 Summarize and kick it off Important: after the Kickoff and Scope Clarifications ● Write and send a summary (e.g. via Mail, inside the Epic issue) ● Keep the Epic Issue on track ● Create sub issues if needed ● Start the work

Slide 40

Slide 40 text

40 7 Summarize and kick it off

Slide 41

Slide 41 text

41 Summary and possible action needs ● Create Epic Issue Template ● Create Miro Template for Kickoffs ● Share your thoughts

Slide 42

Slide 42 text

Thank you!

Slide 43

Slide 43 text

43

Slide 44

Slide 44 text

44 Notes ● What it means to me ○ OKR as a starting point ○ Double diamond & shape up & the big why ○ How does the Kickoff fit into this ● Learning by example ○ KR: Camunda Modeler has Zeebe Modeler capabilities integrated and is ready to be released ○ Get input first from all stakeholders! ○ What does it mean? What is the minimal thing we want to achieve? First step: clarify OKR ○ Create an empty epic issue ○ Collecting, collecting, collecting ○ Try to scope and descope, already try out stuff (hacking) ○ Once I as a DRI think it is sophisticated shaped, initiate the Kickoff, create Miro ● Potential action items for us as a team