Abstract
Managing the product’s backlog is a major task in agile projects. This case study reports on one organization’s experiences from the transition to a backlog management tool and its contribution to improving sprint planning.. Our key lessons learnt are that a tool is particularly appropriate to organize and specify backlog items in a transparent manner and to handle dependencies. However, we also observed an overhead in backlog management and in reporting during meetings. The concrete project settings play the paramount role in whether such a tool helps or harms the process.
Original language | English |
---|---|
Title of host publication | 35th EUROMICRO Conference on Software Engineering and Advanced Applications (SEAA) |
Place of Publication | Los Alamitos |
Publisher | IEEE |
Pages | 259-262 |
Number of pages | 4 |
ISBN (Print) | 978-0-7695-3784-9 |
DOIs | |
Publication status | Published - 27 Aug 2009 |
Event | 35th EUROMICRO Conference on Software Engineering and Advanced Applications, SEAA 2009 - Patras, Greece Duration: 27 Aug 2009 → 29 Aug 2009 Conference number: 35 |
Publication series
Name | Euromicro Conference on Software Engineering and Advanced Applications |
---|---|
Publisher | IEEE |
Volume | 2009 |
ISSN (Print) | 1089-6503 |
ISSN (Electronic) | 2376-9505 |
Conference
Conference | 35th EUROMICRO Conference on Software Engineering and Advanced Applications, SEAA 2009 |
---|---|
Abbreviated title | SEAA |
Country/Territory | Greece |
City | Patras |
Period | 27/08/09 → 29/08/09 |
Keywords
- SCS-Services
- Process improvement
- Sprint planning
- Agile development