A risk-driven method for eXtreme programming release planning

Abstract

XP (eXtreme Programming) has become popular for IID (Iteration and Increment Development). It is suitable for small teams, lightweight projects and vague/volatile requirements. However, some challenges are left to developers when they desire to practise XP. A critical one of them is constructing the release plan and negotiating it with customers. In this paper, we propose a risk-driven method for XP release planning. It has been applied in a case study and the results show the method is feasible and effective. XP practicers can follow it to decide a suitable release plan and control the development process.

PorchLight: A tag-based approach to bug triaging

“…In some organizations, bug triaging occurs during meetings regularly scheduled to prepare for the next phases of development-whether these phases are a coarse-grained series of major releases (release planning [45,38,41]) or a fine-grained set of sprints in an Agile project [30]. Triagers working in a distributed setting can also participate in the process, either by sharing a screen during a triaging session or by asynchronously annotating bug reports for others to follow-up with.…”

User Story Software Estimation:a Simplification of Software Estimation Model With Distributed Extreme Programming Estimation Technique

“…In software development both of those challenge also called as risks. Li et al [12] proposed a risk driven XP development, and the interesting point in their research is a fact that risks in XP is categorized into four main risks which are requirements risks, estimation risk, technology risk, and personnel risk. In their research, those risks are described qualitatively in a range low, medium, and high.…”

“…Therefore, when calculating man days we calculate using this formula. (12) Effort rate (ER) in user story is following the Carroll effort rate. The man-days value then converted using a standard rate that agreed both client and the team.…”

Basic research in computer science and software engineering at SKLCS

“…A risk-driven release planning method for extreme programming has also been proposed. The method uses risks analysis to expose the strengths and the weaknesses of a release plan and to improve developers' understanding of system goals and awareness of their abilities [78].…”