Agile Metrics: Progress Monitoring of Agile Contractors

Hayes, William; Miller, Stephanie; Lapham, Mary Ann; Wrubel, Eileen; Chick, Timothy A.

doi:10.21236/ada609876

Cited by 9 publications

(3 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Also, the teamwork uses the Fibonacci series method to scale the complexity. Velocity is the volume of work accomplished in a specified period of time, by a given team [17]. The velocity in agile refers to amount of stories that can be handled in single iteration.…”

Section: Story Point's Methodsmentioning

confidence: 99%

An Enhanced Framework for Effort Estimation of Agile Projects

Raslan¹,

Darwish²

2018

IJIES

View full text Add to dashboard Cite

Software effort estimation methods are used to measure the total time and forecast the amount of required effort to develop the software. In addition, agile software projects, the requirements are characterized by changeability during the software projects. Therefore using the traditional estimation models in agile software projects may cause inaccurate effort estimation. This paper proposes a framework which utilizes The Constructive Cost Model (COCOMO II), story points, and fuzzy logic models without affecting the sacredness of agile principles. Furthermore, the results show the proposed framework increasing the value of Prediction Level (Pred) to 80%.

show abstract

Section: Story Point's Methodsmentioning

confidence: 99%

An Enhanced Framework for Effort Estimation of Agile Projects

Raslan¹,

Darwish²

2018

IJIES

View full text Add to dashboard Cite

show abstract

“…Three most popular Agile metrics are velocity, sprint burndown chart and release burndown chart [10]. Velocity Information Technology and Management Science _______________________________________________________________________________________________ 2018/21 55 represents volume of work accomplished in a specified time; a sprint burndown chart shows progress of development during a sprint and a release burndown chart shows progress of development during the whole release [10].…”

Section: B Metricsmentioning

confidence: 99%

Quality metrics in Agile Software Development Projects

Kārkliņa

Pirta

2018

ITMS

View full text Add to dashboard Cite

Nowadays, IT projects are becoming more complex and larger in scale. Stakeholders often experience difficulties assessing project quality attributes, such as progress, budget. Specifically adapted project metrics based on their descriptive features are beneficial tools for acquiring important information. The paper discusses metrics as an important project quality assessment method. It proposes using GQM method for selecting the most appropriate Agile project quality metrics. For metrics monitoring it explores popular cloud-based project management systems. An illustration of the approach is provided by two case studies with Agile projects in the public sector.

show abstract

“…Evolving development approaches also introduce new measurement concepts altogether. For instance, notions such as velocity (amount of working software delivered in a given development period), sprint burndown (daily progress toward completing a fixed workload), and release burnup (accumulation of completed work) augment traditional counts of software size, number of requirements satisfied, count of defects detected, and so on [30].…”

Section: Failing To Recognize the Challengesmentioning

confidence: 99%

Giant Slayer: Will You Let Software be David to Your Goliath System?

Blanchette

2016

Journal of Aerospace Information Systems

View full text Add to dashboard Cite

Modern aerospace systems are marvels of engineering. Their amazing achievements are due in large part to software, yet relatively few project personnel, especially project management staff, understand or appreciate the significance of it. The lack of understanding and attention to software often dooms large aerospace projects to significant delay if not outright failure. As a motivation, several software-related aerospace incidents, from benign to calamitous, are recounted here to demonstrate the extent of the problem. Frequently repeated oversights witnessed on many large aerospace projects are then reviewed, with an eye toward what can (and should) be done to avoid the pitfalls. The intent is to empower the reader with information and ideas to prevent software from slaying the giant systems that it is built to support. Nomenclature t = time

show abstract

Agile Metrics: Progress Monitoring of Agile Contractors

Abstract: xiv

Cited by 9 publications

References 5 publications

An Enhanced Framework for Effort Estimation of Agile Projects

An Enhanced Framework for Effort Estimation of Agile Projects

Quality metrics in Agile Software Development Projects

Giant Slayer: Will You Let Software be David to Your Goliath System?

Contact Info

Product

Resources

About