Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Framework Compass Chart - Agile Venture Day Bol...

Framework Compass Chart - Agile Venture Day Bolzano 2019

Francesco Strazzullo

May 10, 2019
Tweet

More Decks by Francesco Strazzullo

Other Decks in Programming

Transcript

  1. “A pessimist sees the difficulty in every opportunity; an optimist

    sees the opportunity in every difficulty.” Winston Churchill
  2. Different answers are possible, but because of their range and

    complexity all of the options can’t be identified
  3. “As a user I want to login so that I

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

    can access the members section in less than two seconds”
  5. “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
  6. 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
  7. Your tech team can now use this chart as a

    Compass while choosing a Framework
  8. This tool will not give you the solution, but it

    will help you have a better discussion
  9. Identity “Who are we?” Market “Who are the users?” Value

    “What the software should do?” Context “How the software should be?” Decisions