Importance of stable velocity in agile maintenance

Omanović, Samir; Buza, Emir

doi:10.1109/icat.2013.6684044

Cited by 5 publications

(7 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This research continues to develop the concept that velocity is an important parameter for stability [16]. This research uses data from a software agile development project to investigate whether a metric(s) for scope change provides an accurate indication for schedule risk.…”

Section: Discussionmentioning

confidence: 98%

See 1 more Smart Citation

Using Velocity, Acceleration, and Jerk to Manage Agile Schedule Risk

Bumbary

2016

2016 International Conference on Information Systems Engineering (ICISE)

View full text Add to dashboard Cite

Stable velocity is paramount for agile planning and builds trust with stakeholders. What metric represents agile stability? Agile processes establish the principle the schedule is fixed and scope changes. Agile velocity is well defined. Velocity is how much technical scope a team of people can produce over a period of time. It ties the technical scope to the schedule. This research continues to develop the concept that a stable velocity is an important factor in the change management process and risk management process. Specifically, stable velocity can help prevent a chaotic relationship with the customer. If the velocity is stable from sprint to sprint, it means planning and the execution is well aligned. This research uses past data from software agile development projects to investigate whether a metric for change in technical scope provides a leading indicator for schedule risk. Specifically, this paper studies agile velocity and proposes two physics concepts derived from velocity, as new agile metrics: agile acceleration and agile jerk. This paper identifies agile acceleration as a trigger for change and agile jerk as an indicator for stability of a release. The process to incorporate the metrics into agile risk management is provided. This research is relevant to persons who participate and manage Agile development projects. This research can be used to understand potential schedule risk/opportunity associated with unfinished work returning to the product backlog for later planning. (Abstract)

show abstract

Section: Discussionmentioning

confidence: 98%

“…With this goal, we can better plan the release which may lead to reduced schedule risk of unfinished work [16].…”

Section: )mentioning

confidence: 96%

Using Velocity, Acceleration, and Jerk to Manage Agile Schedule Risk

Bumbary

2016

2016 International Conference on Information Systems Engineering (ICISE)

View full text Add to dashboard Cite

show abstract

“…Agile maintenance is the most excellent option to stay pace for customer requirements Omanovic and Buza [2]. This is answer to customer requests for a change.…”

Section: Agile Maintenancementioning

confidence: 99%

Scrum-Based Methodology for Product Maintenance and Support

Naz¹,

Khan²,

Aamir³

2016

IJEM

View full text Add to dashboard Cite

Product maintenance techniques have significant importance because they are much cost effective and less time consuming to maintain a product or software rather to change it. There are different product maintenance and support techniques. These previous techniques do not solve user/clients bugs, issues and enhancements effectively and efficiently. Scrum is being used now a day as a quick, flexible and holistic methodology to develop software. In Scrum projects there is the much customer involvement is included which help to develop a user oriented product. Users can change their requirements in Scrum. Many techniques have been proposed for product maintenance and support. However, in this paper, there have been a detailed literature review of existing product maintenance techniques and also presented a new proposed model and technique for the product maintenance by using Scrum methodology. This Scrum based model for maintenance is designed and based on the analysis of client request types and severity (priority). In our approach, The Session attendees (Scrum Master, Product Owner and Team) choose that bug, issue or enhancement first which has an urgent type or higher priority request and resolves it then select low priority request or non urgent requests and facilitates the clients in timely manner. In this way this proposed model works effectively and defiantly to meet the customer"s demand. A comprehensive study on product maintenance and support has been carried out which adds to the current practices in the scrum. We found that maintenance phase of the scrum has been given less attention in the existing literature. In view of this, we have made an attempt to propose a novel model that focuses on the maintenance phase of scrum.

show abstract

“…Moreover, both adaptive (e.g., due to changed qualitative requirements) and perfective (new user requirement from PB) forms of maintenance are incremental in nature. Actually [6] provide a pertinent characterization of the interplay between agile project and maintenance activities: "Maintenance can be seen as an endless agile project whose product backlog is changing constantly". The same authors, importantly, also point out the existence of Change request -change management type of activity resulting from a customer as PO mastering the Product Backlog.…”

Section: Introductionmentioning

confidence: 99%

“…The same authors, importantly, also point out the existence of Change request -change management type of activity resulting from a customer as PO mastering the Product Backlog. In [6] the overall analysis along the change management direction, provided recommendations on balancing the customer disturbance and agility, and being more involved in the customer's planning process on aligning business and software changes.…”

Section: Introductionmentioning

confidence: 99%

Distributed Scrum when Turning into Maintenance : A Single Case Study

Kilpala¹,

Kärkkäinen

Oy³

2015

Computer Science &Amp; Information Technology ( CS &Amp; IT )

View full text Add to dashboard Cite

Global software development using agile methods is commonplace in software industry nowadays. Scrum, as the agile development management framework, can be distributed in many ways, especially concerning how the key roles are presented in different sites. We describe here a single case study of a distributed Scrum, mainly for maintenance of the already constructed web portal. Using a qualitative method, both working well and challenging parts of the software work, as experienced by the project stakeholders, are revealed and discussed.

show abstract

Importance of stable velocity in agile maintenance

Cited by 5 publications

References 2 publications

Using Velocity, Acceleration, and Jerk to Manage Agile Schedule Risk

Using Velocity, Acceleration, and Jerk to Manage Agile Schedule Risk

Scrum-Based Methodology for Product Maintenance and Support

Distributed Scrum when Turning into Maintenance : A Single Case Study

Contact Info

Product

Resources

About