Decision Making for software development

Slide 1

Slide 1 text

No content

Slide 2

Slide 2 text

Francesco Strazzullo (AKA Strazz) @TheStrazz86 (Follow me on Twitter!)

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

♥ London, Madrid, Las Palmas, Berlin, Milan, Rome, Turin, Genoa, Bologna, Ancona and wherever you want! We are hiring →

Slide 5

Slide 5 text

https://www.stackoverflowbusiness.com/blog/what-defines-a-senior-developer

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

Jeremykemp at English Wikipedia [CC BY-SA]

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

No content

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

No content

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

Identity Who are we? Market Who are the users? Value How does the software impact the market? Context Where my software “lives”? Decisions

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

No content

Slide 26

Slide 26 text

Conway’s Law

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

No content

Slide 29

Slide 29 text

For [TARGET CUSTOMER TYPE] who want to [NEED / DESIRE], [PRODUCT / FEATURE] is a [MARKET CATEGORY] that [KEY BENEFIT].

Slide 30

Slide 30 text

No content

Slide 31

Slide 31 text

No content

Slide 32

Slide 32 text

No content

Slide 33

Slide 33 text

No content

Slide 34

Slide 34 text

No content

Slide 35

Slide 35 text

1. Tell, the manager decides. 2. Sell, the manager decides and tries to sell their decision to the team. 3. Consult, the manager asks input from the team before the manager makes the decision. 4. Agree, the manager and team agree together on the decision. 5. Advice, the team asks input from the manager before they make the decision. 6. Inquire, the team makes the decision, and try to sell this decision to the manager. 7. Delegate, the team makes the decision. If necessary they will inform the manager.

Slide 36

Slide 36 text

No content

Slide 37

Slide 37 text

No content

Slide 38

Slide 38 text

No content

Slide 39

Slide 39 text

No content

Slide 40

Slide 40 text

Graphic by Adobe

Slide 41

Slide 41 text

No content

Slide 42

Slide 42 text

No content

Slide 43

Slide 43 text

No content

Slide 44

Slide 44 text

No content

Slide 45

Slide 45 text

No content

Slide 46

Slide 46 text

No content

Slide 47

Slide 47 text

No content

Slide 48

Slide 48 text

No content

Slide 49

Slide 49 text

No content

Slide 50

Slide 50 text

“As Max, I want to invite my friends, so that we can enjoy this service together”

Slide 51

Slide 51 text

No content

Slide 52

Slide 52 text

No content

Slide 53

Slide 53 text

Goal The centre of an impact map answers the most important question: Why are we doing this? This is the goal we are trying to achieve. Actors The first branch of an impact map provides answers to the following questions: Who can produce the desired eﬀect? Who can obstruct it? Who are the consumers or users of our product? Who will be impacted by it? These are the actors who can influence the outcome. Impacts The second branch level of an impact map sets the actors in the perspective of our business goal. It answers the following questions: How should our actors’ behaviour change? How can they help us to achieve the goal? How can they obstruct or prevent us from succeeding? These are the impacts that we’re trying to create. Deliverables Once we have the first three questions answered, we can talk about scope. The third branch level of an impact map answers the following question: What can we do, as an organisation or a delivery team, to support the required impacts?These are the deliverables, software features and organisational activities.

Slide 54

Slide 54 text

“We believe that [impact] by doing [deliverable] will lead to [goal]”

Slide 55

Slide 55 text

“We believe that showing the platform by letting Max invite his friends will lead to have more paying users”

Slide 56

Slide 56 text

No content

Slide 57

Slide 57 text

https://www.facebook.com/notes/kent-beck/the-product-development-triathlon/1215075478525314/

Slide 58

Slide 58 text

No content

Slide 59

Slide 59 text

“We believe that showing the platform by letting Max invite his friends in less than two seconds will lead to have more paying users”

Slide 60

Slide 60 text

“What a software should do?” VS “How a software should be?”

Slide 61

Slide 61 text

“A non-functional requirement (NFR) is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors.” Wikipedia

Slide 62

Slide 62 text

accessibility accountability accuracy adaptability reliability administrability affordability agility auditability responsiveness autonomy availability compatibility composability seamlessness configurability correctness credibility customizability simplicity debugability self-sustainability robustness dependability sustainability deployability determinability discoverability distributability usability durability effectiveness efficiency extensibility repeatability fault tolerance fidelity flexibility inspectability reusability reproducibility integrity interoperability learnability securability maintainability manageability mobility modifiability stability modularity operability evolvability performances tailorability portability wow-effect predictability resilience transparency producibility safety recoverability relevance testability

Slide 63

Slide 63 text

No content

Slide 64

Slide 64 text

No content

Slide 65

Slide 65 text

No content

Slide 66

Slide 66 text

No content

Slide 67

Slide 67 text

No content

Slide 68

Slide 68 text

No content

Slide 69

Slide 69 text

No content

Slide 70

Slide 70 text

No content

Slide 71

Slide 71 text

No content

Slide 72

Slide 72 text

No content

Slide 73

Slide 73 text

No content

Slide 74

Slide 74 text

No content

Slide 75

Slide 75 text

No content

Slide 76

Slide 76 text

No content

Slide 77

Slide 77 text

No content

Slide 78

Slide 78 text

Depth People Pro/Cons Dot Voting QuEST Hearings

Slide 79

Slide 79 text

Depth Guess Speed Learning

Slide 80

Slide 80 text

Impact Speed Practice Guess Guts Depth

Slide 81

Slide 81 text

No content

Slide 82

Slide 82 text

Thanks! Francesco Strazzullo strazz@flowing.it

Slide 83

Slide 83 text

https://forms.gle/q55usWAWDDuRRnkh9

Slide 84

Slide 84 text

https://www.amazon.it/Decision-Making-Dummies-Dawna-Jones/dp/111883366X https://www.amazon.it/Business-Model-Generation-Visionaries-Challengers/dp/0470876417 https://www.amazon.it/New-How-Creating-Solutions-Collaborative/dp/0596156251 https://www.amazon.it/Thinkers-Toolkit-Fourteen-Powerful-Techniques/dp/0812928083 https://www.amazon.it/Building-Evolutionary-Architectures-Support-Constant/dp/1491986360 https://www.amazon.it/Impact-Mapping-Software-Products-Projects/dp/0955683645