ALM Day 2014, Napoli: agile@scale - be safe!

355 views

Published on

Agile a livello Enterprise

1 Comment
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total views
355
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
2
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

ALM Day 2014, Napoli: agile@scale - be safe!

  1. 1. getlatestversion.it
  2. 2. @felicepescatore Disciplined Agile Delivery Italy Group www.felicepescatore.it Agile Software Architect & Metodology Head Ancitel Spa
  3. 3. COMPLEX Emergent Practices COMPLICATED Good Practices CHAOTIC Novel Practices SIMPLE Best Practices Cynefin Model
  4. 4. If a process is too unpredictable or too complicated for the planned, (predictive) approach, then the empirical approach (measure and adapt) is the method of choice. - Ken Schwaber
  5. 5. Con il cappello “Agile” non si intende un insieme di processi e tool. Agile è un set di Valori e Pratiche su cui basare le proprie attività, e, perché no, I processi e i tool utilizzati.
  6. 6. SCRUM eXtreme Programming Kanban RUP / OpenUP DSDMEvo CrystalFDD
  7. 7. DSDM Atern RUP / Open UP FDD Fuller Approaches (still agile) SCRUM Crystal eXtreme Programming Lightweight Approaches Disciplined Agile Delivery, DAD Scaled Agile Framework@Scale Scaled Agile Framework, SAFe Agile
  8. 8. Domain Complexity Straight -forward Intricate, emerging Compliance requirement Low risk Critical, audited Team size Under 10 developers 1000’s of developers Co-located Geographical distribution Global Enterprise discipline Project focus Enterprise focus Technical complexity Homogenous Heterogeneous, legacy Organization distribution (outsourcing, partnerships) Collaborative Contractual Disciplined Agile Delivery Flexible Rigid Organizational complexity
  9. 9. A project is more than only development…
  10. 10. Aggredire il mercato con una nuova idea • Generata dall’esigenza • Pensata per creare un’esigenza • Chi finanzia il progetto? • Quali sono i rischi? • Di quante persone ho bisogno? Quanti Team? • Dove avvengono le attività? • Quali sono le tecnologie di supporto? • … Program Level & Inception
  11. 11. Program Level & Inception • Creare il Program Backlog (Feature) • Creare i Team Backlog (User Story) • Identificare i PSI (Potential Shippable Increment) • …. Team Level & Construction • Prendere in carico il Team Backlog • Definire le iterazioni in relazione ai PSI • Definire i Task • Scegliere le pratiche da utilizzare • …
  12. 12. Program Level & Transition • Completato lo sviluppo, il sistema deve essere manutenuto in erogazione e fruibile correttamente da client di tipologia diversa (anche molto!)
  13. 13. • Leaders (in ALM) have strong capabilities in agile practices, including driving portfolio management support and support for enterprise agile capabilities, such as SAFe and Disciplined Agile Delivery (DAD)* * Tratto da: Magic Quadrant for Application Development Life Cycle Management (19 November 2013)
  14. 14. Lean Based

×