Nowadays, Scrum, born in 1993, is by far the dominant methodology in software development. It progressed by a series of stages. In the first stage, Scrum became more and more popular for the development team. In a second stage, approximately between 2006 and 2016, Scrum and Agile Methodologies were extended to manage large projects, giving rise to the “Scaled Agile”. In the third stage, Scrum and allied Agile Methodologies had to deal with the Covid Pandemics, which impeded almost all the face-to-face Scrum ceremonies and interactions, and developed equivalent software surrogates. In short, Agile methodologies may be classified in three layers, which are partially self contained. The outer layer includes Project Management approaches and techniques, like LeSS and alike. In turn, the middle layer includes the core Scrum ceremonies and artifacts. Finally, the inner layer includes Software Engineering techniques, whose most important methodologies are inherent to Extreme Programming. This three-layer model allows a hybrid approach to the software Project Development. Specifically, a very large and very complex project may rely on an outer layer partially or totally built on a traditional Project Management, like PMBOK, while the work of a Development Team can rely on a typical Scrum approach. In turn, the Scrum’s “User Stories” may be replaced by modeling languages like BPMN or UML. Our thesis provides an extensive list of techniques and methodologies that apply to this three-level on a set of case studies. This can enable Project management to define a case-by-case Project Management approach based on the specific characteristics of each individual project.
Oggi Scrum, nato nel 1993, è di gran lunga la metodologia dominante nello sviluppo del software. Si è evoluto in una serie di fasi. Nella prima fase, Scrum è diventato sempre più popolare per il team di sviluppo. In una seconda fase, approssimativamente tra il 2006 e il 2016, le Metodologie Scrum e Agile sono state estese alla gestione di grandi progetti, dando vita allo “Scaled Agile”. Nella terza fase, Scrum e le Metodologie Agile si sono adattate per le Pandemie Covid, che hanno impedito quasi tutte le cerimonie e le interazioni face-to-face di Scrum, e si sono sviluppati "surrogati" grazie all'utilizzo di software equivalenti. In breve, le metodologie Agili possono essere classificate in tre livelli, che sono parzialmente autonomi. Lo strato esterno include approcci e tecniche di Project Management, come LeSS e simili. A sua volta, lo strato intermedio include le cerimonie Scrum fondamentali, come le cerimonie nello Sprint. Infine, lo strato interno comprende le tecniche di Ingegneria del Software, le cui metodologie più importanti sono inerenti all' Extreme Programming. Questo modello a tre livelli consente un approccio ibrido allo sviluppo del progetto software. Nello specifico, un progetto molto grande e molto complesso può fare affidamento su uno strato esterno costruito parzialmente o totalmente su un Project Management tradizionale, come PMBOK, mentre il lavoro di un Team di Sviluppo può contare su un tipico approccio Scrum. A loro volta, le User Story di Scrum possono essere sostituite da linguaggi di modellazione come BPMN o UML. La nostra tesi fornisce un ampio elenco di tecniche e metodologie che si applicano a questi tre livelli su una serie di casi di studio. Ciò può consentire al Project Management di definire un approccio di Project Management caso per caso basato sulle caratteristiche specifiche di ogni singolo progetto.
The Evolution of Agile Projects: a reference framework
CESENO, ALESSANDRO
2021/2022
Abstract
Nowadays, Scrum, born in 1993, is by far the dominant methodology in software development. It progressed by a series of stages. In the first stage, Scrum became more and more popular for the development team. In a second stage, approximately between 2006 and 2016, Scrum and Agile Methodologies were extended to manage large projects, giving rise to the “Scaled Agile”. In the third stage, Scrum and allied Agile Methodologies had to deal with the Covid Pandemics, which impeded almost all the face-to-face Scrum ceremonies and interactions, and developed equivalent software surrogates. In short, Agile methodologies may be classified in three layers, which are partially self contained. The outer layer includes Project Management approaches and techniques, like LeSS and alike. In turn, the middle layer includes the core Scrum ceremonies and artifacts. Finally, the inner layer includes Software Engineering techniques, whose most important methodologies are inherent to Extreme Programming. This three-layer model allows a hybrid approach to the software Project Development. Specifically, a very large and very complex project may rely on an outer layer partially or totally built on a traditional Project Management, like PMBOK, while the work of a Development Team can rely on a typical Scrum approach. In turn, the Scrum’s “User Stories” may be replaced by modeling languages like BPMN or UML. Our thesis provides an extensive list of techniques and methodologies that apply to this three-level on a set of case studies. This can enable Project management to define a case-by-case Project Management approach based on the specific characteristics of each individual project.È consentito all'utente scaricare e condividere i documenti disponibili a testo pieno in UNITESI UNIPV nel rispetto della licenza Creative Commons del tipo CC BY NC ND.
Per maggiori informazioni e per verifiche sull'eventuale disponibilità del file scrivere a: unitesi@unipv.it.
https://hdl.handle.net/20.500.14239/15097