Framework Compass Chart - Agile Venture Day Bolzano 2019

Transcript

1. Framework Compass Chart
2. Francesco Strazzullo (AKA Strazz) @TheStrazz86 (Follow me on Twitter!) Ego Slide
3. WE DEVELOP DIGITAL PROJECT TOGETHER WITH YOU.
4. JavaScript Fatigue
7. “A pessimist sees the difficulty in every opportunity; an optimist sees the opportunity in every difficulty.” Winston Churchill
9. Choose the right framework
10. “Individuals and interactions over processes and tools” Agile Manifesto
11. Choose a “good enough” framework in a right way
17. Decision Making
18. What kind of problem is to choose a framework? https://www.amazon.com/Thinkers-Toolkit-Powerful-Techniques-Problem/dp/0812928083
19. Simplistic
20. There is only one answer
21. "Who is the president of the USA?"
22. Deterministic
23. There is only one answer but you need analysis or a formula to work it out
24. "What is the area of a circle with a radius of 5 cm?"
25. Random
26. Different answers are possible but the options can all be identified
27. "Which of the candidates will win the election?"
28. Indeterminate
29. Different answers are possible, but because of their range and complexity all of the options can’t be identified
30. "How will the Internet affect our retail sales over the next five years?"
32. A mix of Data and Judgement
33. What Data do we need?
34. Functional Requirements
35. “As a user I want to login so that I can access the members section”
36. “As a user I want to login so that I can access the members section in less than two seconds”
37. “What a software should do?” VS “How a software should be?”
38. Non-functional Requirements
39. “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
40. 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 precision predictability resilience transparency producibility safety recoverability relevance testability
41. Framework Compass Chart
42. A tool to help visualize the most important NFRs of your project
43. People involved: tech people and stakeholders
45. Choose the 5 most important NFRs for your project
47. Retrospective
48. SWOT analysis
49. Xhienne [CC BY-SA 2.5 (https://creativecommons.org/licenses/by-sa/2.5)]
50. Trade-offs slider
52. When your team find the NFRs, put them on a radar chart
54. Fill the chart
56. Your tech team can now use this chart as a Compass while choosing a Framework
58. Use it as a map of the Context where your software “lives”.
59. This tool will not give you the solution, but it will help you have a better discussion
60. Choose a “good enough” framework in a right way
62. Rules
63. Don’t give the max to every NFR: the perfect solution does not exists
65. Try to reach consensus (Planning Poker)
66. Use it as an information radiator
68. Identity “Who are we?” Market “Who are the users?” Value “What the software should do?” Context “How the software should be?” Decisions
69. One more thing...
70. https://www.apress.com/it/book/9781484249666
71. http://frameworklessmovement.org/ Tweet At #Frameworkless
72. Thanks! Francesco Strazzullo strazz@flowing.it