$30 off During Our Annual Pro Sale. View Details »

Agile Fluency e che cosa significa per il business

Agile Fluency e che cosa significa per il business

My presentation (in Italian) at the Italian Agile Business Day 2016

Matteo Vaccari

September 19, 2016
Tweet

More Decks by Matteo Vaccari

Other Decks in Technology

Transcript

  1. Team agile fluency … e il business Matteo Vaccari

  2. AGILITÀ Che significa?

  3. Team Culture Shift Start: Building Code A Team’s Path Through

    Agile Fluency Focus on Value ˒ See progress from business perspective Redirect teams when needed Deliver Value ˒˒ Ship on market cadence Capture value frequently Reveal obstructions early Optimize Value ˒˒˒ Make excellent product decisions Eliminate handoffs Speed decision making Optimize for Systems ˒˒˒˒ Cross-pollinate perspectives Stimulate innovation Optimize value stream Team Skills Shift Organizational Structure Shift Organizational Culture Shift For more information, visit: agilefluency.com © 2012 James Shore and Diana Larsen. You may reproduce this diagram in any form so long as this copyright notice is preserved. James Shore Diana Larsen
  4. CHE SIGNIFICA “FLUENCY”? 4 fluent |ˈfluːənt| adjective 1 able to

    express oneself easily and articulately 2 smoothly graceful and effortless: his style of play was fast and fluent. 3 able to flow freely; fluid
  5. Non è una pagella…

  6. Team Culture Shift Start: Building Code A Team’s Path Through

    Agile Fluency Focus on Value ˒ See progress from business perspective Redirect teams when needed Deliver Value ˒˒ Ship on market cadence Capture value frequently Reveal obstructions early Optimize Value ˒˒˒ Make excellent product decisions Eliminate handoffs Speed decision making Optimize for Systems ˒˒˒˒ Cross-pollinate perspectives Stimulate innovation Optimize value stream Team Skills Shift Organizational Structure Shift Organizational Culture Shift For more information, visit: © 2012 James Shore and Diana Larsen. CREATE BUSINESS VALUE 6
  7. Team Culture Shift Start: Building Code A Team’s Path Through

    Agile Fluency Focus on Value ˒ See progress from business perspective Redirect teams when needed Deliver Value ˒˒ Ship on market cadence Capture value frequently Reveal obstructions early Optimize Value ˒˒˒ Make excellent product decisions Eliminate handoffs Speed decision making Team Skills Shift Organizational Structure Shift CREATE BUSINESS VALUE 7
  8. L’INIZIO DI UN PROGETTO… 8 T F

  9. LA CONCLUSIONE DESIDERATA 9 T F

  10. LA TRISTE REALTÀ 10 T F

  11. CONSEGNARE VALORE 11 T F

  12. TRASPARENZA 12 T F

  13. USER STORIES 13

  14. SCRUM 14

  15. ▫︎Investimento: sul team; ▫︎corsi ▫︎coaching ▫︎ScrumMaster ▫︎Metodi: Scrum, Kanban ▫︎Benefici:

    visibilità, riduzione del rischio ▫︎Come si vede: consegna di running, tested features ▫︎Tempi: 2-6 mesi Focus on Value ˒ See progress from business perspective Redirect teams when needed Deliver Value ˒˒ Ship on market cadenc Capture value frequent Reveal obstructions ear Optimize Value ˒˒˒ Make excellent product decisions Eliminate handoffs Speed decision making Optimize for Syste ˒˒˒˒ Cross-pollinate perspect Stimulate innovation Optimize value stream Team Skills Shift Organizational Culture Shift © 2012 James Shore and Diana Larsen. You may reproduce this diagram in any form so long as this copyright notice is preserved. CREATE BUSINESS VALUE 15
  16. Team Culture Shift Start: Building Code A Team’s Path Through

    Agile Fluency Focus on Value ˒ See progress from business perspective Redirect teams when needed Deliver Value ˒˒ Ship on market cadence Capture value frequently Reveal obstructions early Optimize Value ˒˒˒ Make excellent product decisions Eliminate handoffs Speed decision making Optimize for Systems ˒˒˒˒ Cross-pollinate perspectives Stimulate innovation Optimize value stream Team Skills Shift Organizational Structure Shift Organizational Culture Shift For more information, visit: © 2012 James Shore and Diana Larsen. CONSEGNARE AL RITMO DEL CLIENTE 16
  17. Team Culture Shift Start: Building Code A Team’s Path Through

    Agile Fluency Focus on Value ˒ See progress from business perspective Redirect teams when needed Deliver Value ˒˒ Ship on market cadence Capture value frequently Reveal obstructions early Optimize Value ˒˒˒ Make excellent product decisions Eliminate handoffs Speed decision making Optimize for Systems ˒˒˒˒ Cross-pollinate perspectives Stimulate innovation Optimize value stream Team Skills Shift Organizational Structure Shift Organizational Culture Shift For more information, visit: © 2012 James Shore and Diana Larsen. CONSEGNARE AL RITMO DEL CLIENTE 17
  18. F T 18 CONSEGNARE AL RITMO DEL CLIENTE

  19. None
  20. DOV’È L’INGHIPPO? 20 Produttività Tempo Il team inizia a fare

    TDD Il team fa TDD bene e ha ripagato il debito tecnico
  21. LE FORZE IN GIOCO 21 L’organizzazione Il team Il codice

  22. COME MITIGARE LA FOSSA? 22 Produttività Tempo Il team inizia

    a fare TDD Il team fa TDD bene e ha ripagato il debito tecnico
  23. METODO (A): UN COACH TECNICO 23

  24. METODO (B): CO-SOURCING 24 Il tuo team Un team esterno

    esperto in TDD Co-sourcing
  25. Deliver Value ˒˒ Ship on market cadence Capture value frequently

    Reveal obstructions early Optimize Value ˒˒˒ Make excellent product decisions Eliminate handoffs Speed decision making Optimize for Systems ˒˒˒˒ Cross-pollinate perspectives Stimulate innovation Optimize value stream Skills Shift Or Str Organizational Culture Shift For mor a © 2012 James Shore and Diana Larsen. You may reproduce this diagram in any form so long as this copyright notice is preserved. ▫︎Investimento: produttività ridotta mentre il team ▫︎impara ▫︎ripaga il debito tecnico ▫︎Metodi: Extreme Programming (XP) ▫︎Beneficio: consegne per tempo, con pochi difetti ▫︎Come si vede: si consegna quando vuole il cliente ▫︎Tempi: 3-24 mesi CONSEGNARE AL RITMO DEL CLIENTE 25
  26. Team Culture Shift Start: Building Code A Team’s Path Through

    Agile Fluency Focus on Value ˒ See progress from business perspective Redirect teams when needed Deliver Value ˒˒ Ship on market cadence Capture value frequently Reveal obstructions early Optimize Value ˒˒˒ Make excellent product decisions Eliminate handoffs Speed decision making Optimize for Systems ˒˒˒˒ Cross-pollinate perspectives Stimulate innovation Optimize value stream Team Skills Shift Organizational Structure Shift Organizational Culture Shift For more information, visit: © 2012 James Shore and Diana Larsen. OTTIMIZZARE IL VALORE 26
  27. Team Culture Shift Start: Building Code A Team’s Path Through

    Agile Fluency Focus on Value ˒ See progress from business perspective Redirect teams when needed Deliver Value ˒˒ Ship on market cadence Capture value frequently Reveal obstructions early Optimize Value ˒˒˒ Make excellent product decisions Eliminate handoffs Speed decision making Optimize for Systems ˒˒˒˒ Cross-pollinate perspectives Stimulate innovation Optimize value stream Team Skills Shift Organizational Structure Shift Organizational Culture Shift For more information, visit: © 2012 James Shore and Diana Larsen. OTTIMIZZARE IL VALORE 27
  28. T F Il momento di massima ignoranza

  29. QUAL’È LA “FUNZIONE”? 29

  30. LA COMPETIZIONE È SU “QUANTO BENE” ESEGUE LA SUA FUNZIONE

    30
  31. CAMBIAMO I TERMINI DEL PROBLEMA 31 Quanto ci mettete a

    finire questa pila di storie? Che cosa abbiamo imparato questa settimana? Qual è la cosa più importante per la settimana prossima? Plan Do Learn T F
  32. TOM GILB 32 www.gilb.com Some Literature

  33. IMPACT MAPPING 33 www.impactmapping.org

  34. None
  35. ▫︎Investimento: ▫︎Incorporare gli esperti di business nel team ▫︎Modiche all’organizzazione

    ▫︎Delegare le decisioni al team ▫︎Metodi: Tom Gilb’s Evo, Impact Mapping, Lean Startup ▫︎Beneficio: un prodotto realmente competitivo ▫︎Come si vede: decisioni basate su metriche di business ▫︎Tempi: 1-5 anni OTTIMIZZARE IL VALORE 35 Optimize Value ˒˒˒ Make excellent product decisions Eliminate handoffs Speed decision making Optimize for Sys ˒˒˒˒ Cross-pollinate perspec Stimulate innovatio Optimize value strea Organizational Culture Shift © 2012 James Shore and Diana Larsen. You may reproduce this diagram in any form so long as this copyright notice is preserved.
  36. Team Culture Shift Start: Building Code A Team’s Path Through

    Agile Fluency Focus on Value ˒ See progress from business perspective Redirect teams when needed Deliver Value ˒˒ Ship on market cadence Capture value frequently Reveal obstructions early Optimize Value ˒˒˒ Make excellent product decisions Eliminate handoffs Speed decision making Optimize for Systems ˒˒˒˒ Cross-pollinate perspectives Stimulate innovation Optimize value stream Team Skills Shift Organizational Structure Shift Organizational Culture Shift For more information, visit: © 2012 James Shore and Diana Larsen. CHOOSE YOUR REWARDS 36
  37. matteo.vaccari.name/blog twitter.com/xpmatteo thoughtworks.com GRAZIE