How to break down

Lightning Talk

Transcript

1. How to break down Lightning Talk ⚡ Niklas
2. 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
3. 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
4. 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
5. 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 ...
6. 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
7. 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
8. 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
9. 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
10. 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
11. 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
12. 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
13. 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
14. Example
15. 15 Q1/2021 KR: Camunda Modeler has Zeebe Modeler capabilities integrated and is ready to be released
16. 16 1 Create an empty Epic Issue
17. 17 1 Create an empty Epic Issue mark as epic issue
18. 18 1 Create an empty Epic Issue mark as epic issue give few first words about the what
19. 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
20. 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
21. 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
22. 22 2 Start chatting OKR presentation
23. 23 2 Start chatting OKR presentation Initial clarification
24. 24 2 Start chatting OKR presentation Initial clarification “Internal Kickoff”
25. 25 2 Start chatting OKR presentation Initial clarification “Internal Kickoff” Technical brainstorming
26. 26 2 Start chatting OKR presentation Initial clarification “Internal Kickoff” Technical brainstorming Product brainstorming
27. 27 2 Start chatting OKR presentation Initial clarification “Internal Kickoff” Technical brainstorming Product brainstorming There is even more (consultants, customers, community)
28. 28 3 Really understand it
29. 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
30. 30 4 Collect, collect, collect ...
31. 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 • ...
32. 32 5 Scope, shape and (maybe) hack
33. 33 5 Scope, shape and (maybe) hack
34. 34 5 Scope, shape and (maybe) hack
35. 35 5 Scope, shape and (maybe) hack
36. 36 6 Iterate, come to an end Important: Time Boxing
37. 37 7 Summarize and kick it off
38. 38 7 Summarize and kick it off Provide enough context, invite anyone optionally Have a look at our docs
39. 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
40. 40 7 Summarize and kick it off
41. 41 Summary and possible action needs • Create Epic Issue Template • Create Miro Template for Kickoffs • Share your thoughts
42. Thank you!
44. 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