Agile methodologies in teams with highly creative and autonomous members
The Agile manifesto encourages us to value individuals and interactions over processes and tools, while Scrum, the most adopted Agile development methodology, is essentially based on roles, events, artifacts, and the rules that bind them together (i.e., processes). Moreover, it is generally proclaim...
Gespeichert in:
Hauptverfasser: | , , , , , , , , , , , , |
---|---|
Format: | Artikel |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext bestellen |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
Zusammenfassung: | The Agile manifesto encourages us to value individuals and interactions over
processes and tools, while Scrum, the most adopted Agile development
methodology, is essentially based on roles, events, artifacts, and the rules
that bind them together (i.e., processes). Moreover, it is generally proclaimed
that whenever a Scrum project does not succeed, the reason is because Scrum was
not implemented correctly and not because Scrum may have its own flaws. This
grants irrefutability to the methodology, discouraging deviations to fit the
actual needs and peculiarities of the developers. In particular, the members of
the NASA ADS team are highly creative and autonomous whose motivation can be
affected if their freedom is too strongly constrained. We present our
experience following Agile principles, reusing certain Scrum elements and
seeking the satisfaction of the team members, while rapidly reacting/keeping
the project in line with our stakeholders expectations. |
---|---|
DOI: | 10.48550/arxiv.2009.05048 |