Slide 1

Slide 1 text

Framework Compass Chart

Slide 2

Slide 2 text

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

Slide 3

Slide 3 text

WE DEVELOP DIGITAL PROJECT TOGETHER WITH YOU.

Slide 4

Slide 4 text

JavaScript Fatigue

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

“A pessimist sees the difficulty in every opportunity; an optimist sees the opportunity in every difficulty.” Winston Churchill

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

Choose the right framework

Slide 10

Slide 10 text

“Individuals and interactions over processes and tools” Agile Manifesto

Slide 11

Slide 11 text

Choose a “good enough” framework in a right way

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

Decision Making

Slide 18

Slide 18 text

What kind of problem is to choose a framework? https://www.amazon.com/Thinkers-Toolkit-Powerful-Techniques-Problem/dp/0812928083

Slide 19

Slide 19 text

Simplistic

Slide 20

Slide 20 text

There is only one answer

Slide 21

Slide 21 text

"Who is the president of the USA?"

Slide 22

Slide 22 text

Deterministic

Slide 23

Slide 23 text

There is only one answer but you need analysis or a formula to work it out

Slide 24

Slide 24 text

"What is the area of a circle with a radius of 5 cm?"

Slide 25

Slide 25 text

Random

Slide 26

Slide 26 text

Different answers are possible but the options can all be identified

Slide 27

Slide 27 text

"Which of the candidates will win the election?"

Slide 28

Slide 28 text

Indeterminate

Slide 29

Slide 29 text

Different answers are possible, but because of their range and complexity all of the options can’t be identified

Slide 30

Slide 30 text

"How will the Internet affect our retail sales over the next five years?"

Slide 31

Slide 31 text

No content

Slide 32

Slide 32 text

A mix of Data and Judgement

Slide 33

Slide 33 text

What Data do we need?

Slide 34

Slide 34 text

Functional Requirements

Slide 35

Slide 35 text

“As a user I want to login so that I can access the members section”

Slide 36

Slide 36 text

“As a user I want to login so that I can access the members section in less than two seconds”

Slide 37

Slide 37 text

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

Slide 38

Slide 38 text

Non-functional Requirements

Slide 39

Slide 39 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 40

Slide 40 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 precision predictability resilience transparency producibility safety recoverability relevance testability

Slide 41

Slide 41 text

Framework Compass Chart

Slide 42

Slide 42 text

A tool to help visualize the most important NFRs of your project

Slide 43

Slide 43 text

People involved: tech people and stakeholders

Slide 44

Slide 44 text

No content

Slide 45

Slide 45 text

Choose the 5 most important NFRs for your project

Slide 46

Slide 46 text

No content

Slide 47

Slide 47 text

Retrospective

Slide 48

Slide 48 text

SWOT analysis

Slide 49

Slide 49 text

Xhienne [CC BY-SA 2.5 (https://creativecommons.org/licenses/by-sa/2.5)]

Slide 50

Slide 50 text

Trade-offs slider

Slide 51

Slide 51 text

No content

Slide 52

Slide 52 text

When your team find the NFRs, put them on a radar chart

Slide 53

Slide 53 text

No content

Slide 54

Slide 54 text

Fill the chart

Slide 55

Slide 55 text

No content

Slide 56

Slide 56 text

Your tech team can now use this chart as a Compass while choosing a Framework

Slide 57

Slide 57 text

No content

Slide 58

Slide 58 text

Use it as a map of the Context where your software “lives”.

Slide 59

Slide 59 text

This tool will not give you the solution, but it will help you have a better discussion

Slide 60

Slide 60 text

Choose a “good enough” framework in a right way

Slide 61

Slide 61 text

No content

Slide 62

Slide 62 text

Rules

Slide 63

Slide 63 text

Don’t give the max to every NFR: the perfect solution does not exists

Slide 64

Slide 64 text

No content

Slide 65

Slide 65 text

Try to reach consensus (Planning Poker)

Slide 66

Slide 66 text

Use it as an information radiator

Slide 67

Slide 67 text

No content

Slide 68

Slide 68 text

Identity “Who are we?” Market “Who are the users?” Value “What the software should do?” Context “How the software should be?” Decisions

Slide 69

Slide 69 text

One more thing...

Slide 70

Slide 70 text

https://www.apress.com/it/book/9781484249666

Slide 71

Slide 71 text

http://frameworklessmovement.org/ Tweet At #Frameworkless

Slide 72

Slide 72 text

Thanks! Francesco Strazzullo strazz@flowing.it