On the sprint length estimation technique in agile software development using planning poker
International Journal of Agile Systems and Management, ISSN: 1741-9182, Vol: 16, Issue: 2, Page: 205-225
2023
- 5Usage
- 13Captures
Metric Options: Counts1 Year3 YearSelecting the 1-year or 3-year option will change the metrics count to percentiles, illustrating how an article or review compares to other articles or reviews within the selected time period in the same journal. Selecting the 1-year option compares the metrics against other articles/reviews that were also published in the same calendar year. Selecting the 3-year option compares the metrics against other articles/reviews that were also published in the same calendar year plus the two years prior.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Metrics Details
- Usage5
- Abstract Views5
- Captures13
- Readers13
- 13
Article Description
The recent literature trend has highlighted the existing method for deciding the length of sprint in agile software development acts as a limitation for agile practitioners and researchers. It prevents them from driving benefit from existing theme and semantic release planning methods. Therefore, this research paper suggests planning poker for estimating the length of sprint for delivering a release scope derived using theme or semantic based release planning method. To perform the research study, a theme based release is taken into consideration and an agile team is set-up to deliver half of the sprint using traditional approach and another half using proposed approach. The planning poker estimates for proposed (median BREbias = –0.1154, BRE = 0.2154) and traditional approach (median BREbias = –0.1169, median BRE = 0.2267) were found almost consistent with an overall saving of approximately 30% saving in sprint planning time, improved stakeholder satisfaction and agile team experience.
Bibliographic Details
http://www.scopus.com/inward/record.url?partnerID=HzOxMe3b&scp=85161943351&origin=inward; http://dx.doi.org/10.1504/ijasm.2023.130837; http://www.inderscience.com/link.php?id=130837; https://scholarworks.sjsu.edu/faculty_rsca/3927; https://scholarworks.sjsu.edu/cgi/viewcontent.cgi?article=4926&context=faculty_rsca
Inderscience Publishers
Provide Feedback
Have ideas for a new metric? Would you like to see something else here?Let us know