Quality metrics in Agile Software Development Projects

Kārkliņa, Kristīne; Pirta, Ruta

doi:10.7250/itms-2018-0008

Cited by 6 publications

(2 citation statements)

References 10 publications

(16 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The measurement practices in ASD [79], [81] Work capacity, percentage of adopted work, sprint-level effort burndown, percentage of found work, focus factor, the accuracy of estimation, accuracy of the forecast, targeted value increase [79] Delivery on time, unit test coverage for the developed code, bug correction time from "new" to "closed" state, open defect severity index ASD process [81] Lack of cohesion of methods, work capacity, sprint goal success rated, total project duration, time to market, total product cost, return on investment, new requests within ROI budgets, success at scale, win/loss record, velocity, standard violation, business value delivered, defects per iteration, number of stories, number of tests Measuring and predicting the developed quantitative planning software in Scrum [90] Functional size method, function points, lead time, queue size in the requirements process, work in progress, requirements ambiguity, requirements completeness, aspectual density per sprint for requirements, requirements maturity index, problem per user month, user stories carried on to the next iteration, size of work items in story point, the complexity level of PB items, the total number of story points, end-user satisfaction, respect of requirements Requirements-associated metrics [93] Passed/failed TCs, failed TC priorities, task breakdown within sprints, release burndown chart, created/executed tasks, task status breakdown, task priority breakdown, average task life span…”

Section: Sourcesmentioning

confidence: 99%

Verifying Agile Black-Box Test Case Quality Measurements: Expert Review

Barraood,

Mohd,

Baharom

et al. 2023

IEEE Access

View full text Add to dashboard Cite

Tests on software are performed to ensure it has no defects. Software testing companies and organizations claimed that the testing problem increased their time and budget for testing by over 50%. As a result, the product's release is delayed, which attracts customer complaints. Testing involves test cases, which are a vital part of the process. Therefore, quality test cases likely to identify defects and meet users' requirements must be chosen. This paper aims to identify and verify the characteristics, sub-characteristics, and metrics that construct the proposed model for producing high-quality black-box test cases in an Agile Software Development environment. An expert review approach was used to verify the proposed model. Ten academic and six industry experts contributed to this verification. The results showed that six characteristics, 22 sub-characteristics, and 56 metrics are accepted to be included in the proposed model. Furthermore, findings revealed that the proposed model is comprehensive, consistent, relevant, and well-organized for Agile projects.INDEX TERMS Expert review, quality characteristics, software test metrics, test case quality, test case quality assessment.

show abstract

Section: Sourcesmentioning

confidence: 99%

Verifying Agile Black-Box Test Case Quality Measurements: Expert Review

Barraood,

Mohd,

Baharom

et al. 2023

IEEE Access

View full text Add to dashboard Cite

show abstract

“…It is simply a ratio of return on investment in terms to cost spent but the challenge here lies in defining an output parameter that is qualitative and quantitative both. According to the previous research, the productivity of Agile software development can be measured with help of metrics like-Done Index, Velocity, and Quality of the Software deliverables (Ramírez-Mora and Oktaba, 2017; Kārkliņa and Pirta, 2018).…”

Section: Theoretical Backgroundmentioning

confidence: 99%

Analyzing the impact of agile mindset adoption on software development teams productivity during COVID-19

Sathe

Panse²

2022

JAMR

View full text Add to dashboard Cite

PurposeThe objective of the study is to analyze the impact of the adoption of the Agile Mindset on the productivity of Agile software development teams in IT enterprises during COVID-19.Design/methodology/approachA web-based survey is performed with voluntary participants working with the Agile software development professionals with a specific focus on IT enterprises around Pune, India. For this the initial exploratory literature review was performed, to explore the team's behaviors and their response to the crises like the Covid-19 pandemic. Data is collected from the targeted population using the random sampling method. A questionnaire is designed with the help of a five-point Likert scale. All the respondents were analyzed based on their behaviors shown and how adopting to Agile mindset has impacted their productivity during the pandemic. Collected data would be then analyzed using the Smart PLS-SEM methodology.FindingsFindings of the study show that Agile software development teams adopting to Agile mindset are better at responding to crisis and quick to adapt to change as teams adopting the Agile mindset is likely to sustain or even improve their productivity during the crises like Covid-19 pandemic. Adapting to an Agile mindset is important for Agile software development teams during a crisis as a response to changes in the working as well as environmental conditions. This study also shows that by adopting an Agile mindset, development teams are better at responding to the crisis eventually improving productivity.Research limitations/implicationsResearch limitations for this study-scope of the study could be extended to the larger population across geographies to have improved insights Productivity Factors like- Efforts Efficiency, Backlog-management Index (BMI), and Weighted Average Productivity (VWP) for team members can be included. More behavioral factors for Agile Mindset can be considered.Practical implicationsAgile software development teams are characterized by collaboration and responsibility. Recent enforcement of pandemic precautionary measures has enforced Agile software development teams to work remotely and maintain social distancing while in the office. It was challenging for most of the working people to adjust to the new working conditions (Yang et al., 2021) However, in IT organizations, adopting the Agile mindset has ensured continuous software deliveries, took ownership, and quickly adapted to the volatile situations, ultimately resulting into the growth in the productivity unlike to that of other sectors of the economy.Social implicationsIn this study, we have analyzed the hypotheses with statistical significance in association with constructs that are in sync with the available literature. Adopting the Agile mindset values has positively impacted the team's behavior resulting in productivity improvement even in the distributed working locations in pandemic situations.Originality/valueThe study highlights that adopting to Agile mindset has positively impacted an Agile software development team's productivity during the Covid-19 pandemic. As environmental conditions during Covid-19 were uncertain and ambiguous and teams were working in distributed and disconnected ways, many researchers have believed that it would have affected the overall productivity. This was turned true for most of the sectors of the economy, however, Agile software development teams have shown positive trends in their productivity, as they have adopted the Agile mindset values and principles, during crises.

show abstract