Decision Making for software development

Transcript

2. Francesco Strazzullo (AKA Strazz) @TheStrazz86 (Follow me on Twitter!)
4. ♥ London, Madrid, Las Palmas, Berlin, Milan, Rome, Turin, Genoa, Bologna, Ancona and wherever you want! We are hiring →
5. https://www.stackoverflowbusiness.com/blog/what-defines-a-senior-developer
10. Jeremykemp at English Wikipedia [CC BY-SA]
23. Identity Who are we? Market Who are the users? Value How does the software impact the market? Context Where my software “lives”? Decisions
26. Conway’s Law
29. For [TARGET CUSTOMER TYPE] who want to [NEED / DESIRE], [PRODUCT / FEATURE] is a [MARKET CATEGORY] that [KEY BENEFIT].
35. 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.
40. Graphic by Adobe
50. “As Max, I want to invite my friends, so that we can enjoy this service together”
53. 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 effect? 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.
54. “We believe that [impact] by doing [deliverable] will lead to [goal]”
55. “We believe that showing the platform by letting Max invite his friends will lead to have more paying users”
57. https://www.facebook.com/notes/kent-beck/the-product-development-triathlon/1215075478525314/
59. “We believe that showing the platform by letting Max invite his friends in less than two seconds will lead to have more paying users”
60. “What a software should do?” VS “How a software should be?”
61. “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
62. 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
78. Depth People Pro/Cons Dot Voting QuEST Hearings
79. Depth Guess Speed Learning
80. Impact Speed Practice Guess Guts Depth
82. Thanks! Francesco Strazzullo strazz@flowing.it
83. https://forms.gle/q55usWAWDDuRRnkh9
84. 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