Planning Poker in cost estimation in Agile methods: Averaging Vs. Consensus

Gandomani, Taghi Javdani; Faraji, Hamidreza; Radnejad, Mahsa

doi:10.1109/kbei.2019.8734960

Cited by 20 publications

(17 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To investigate the hypotheses and research question, regression analysis and correlation were used to estimate the unique relationship between each of the questionnaire and outcome variables in this study. Furthermore, to assess where there were significant differences amongst the thorough ttest [76][77][78].…”

Section: • Data Analysismentioning

confidence: 99%

A software-based cost estimation technique in scrum using a developer's expertise

Butt

Khalid²,

Ercan³

et al. 2022

Advances in Engineering Software

View full text Add to dashboard Cite

Section: • Data Analysismentioning

confidence: 99%

A software-based cost estimation technique in scrum using a developer's expertise

Butt

Khalid²,

Ercan³

et al. 2022

Advances in Engineering Software

View full text Add to dashboard Cite

“…All these literature studies on user stories (i.e., [50]- [52], [228]) were systematic literature reviews that reviewed a limited set of papers (24 to 38) for answering specific review research questions. Given that the user story is the most popular RE artifact in ASD [15], [16], [24] and interaction with users during ASD remains challenging [2], [14], [53], a systematic mapping of all published research on user stories will contribute to an overview and better understanding of our knowledge regarding this technique. As a systematic literature mapping of 186 unique peer-reviewed studies on user stories, this paper distinguishes itself from the systematic literature reviews with specific user story research foci that were discussed in this section.…”

Section: B Previous Literature Studiesmentioning

confidence: 99%

Systematic Literature Mapping of User Story Research

Amna

Poels

2022

IEEE Access

View full text Add to dashboard Cite

User stories are a widely used artifact in Agile software development. Currently, only a limited number of secondary studies have reviewed the research on the user story technique. These research reviews focused on specific research topics related to ambiguity of requirements, effort estimation, and the application of Natural Language Processing. To our knowledge, a systematic mapping of all user story research has not been performed. To this end, we study the academic literature to investigate what user stories research has been performed, what types of problems have been identified, what sort of solutions or other types of research outcomes have been achieved, how mature the research is, and what research gaps exist. We followed Systematic Mapping Study guidelines to synthesize the currently available academic research on user stories. In total, we found 186 unique peer-reviewed studies, published in the period 2001-2021. We observed that research on the user story technique and its use had grown exponentially over the last seven years. Further, using a five-dimensional classification framework -requirements engineering activity, problem class, outcome class, type of research, type of publication -we observed several patterns in the classification of these studies across the different framework dimensions, which provided insights into the state-of-the-art and maturity of the research. We also identified four research gaps: the paucity of focused literature reviews; a lack of research on the role that user stories play in human cognition and interaction; a lack of comprehensive and mature solutions for resolving ambiguity issues with user stories early in the project; and a lack of validation and evaluation of proposed solutions. Several research opportunities are suggested, making our paper a useful reference for future research on user stories allowing researchers to clearly position their contributions.INDEX TERMS Requirements engineering, agile software development, user stories, systematic literature mapping.

show abstract

“…All these make agile less productive for efficient soft-ware development. Therefore, the agile methodology needs some improvements in its methods to become suitable for all types of projects and needs to introduce a cost estimation process with some new team-based estimation procedure to make accurate estimation [9,10,11].…”

Section: Problem Statementmentioning

confidence: 99%

“…Agile also facilitates the client to prioritize the user stories and can give change requests at any level of the project [3]. Agile methods are productive for small-scale projects, small-size teams, requirements welcomed, and group effort estimation for example a planning poker technique [9]. In the agile methodology, the project manager leads estimates the project effort with teamwork [40].…”

Section: Introductionmentioning

confidence: 99%

Project Management Issues While Using Agile Methodology

Butt

Piñeres-Espitia

Ariza-Colpas

et al. 2022

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Software engineering has many software development life cycle (SDLC) models to develop a software application and the latest SDLC models have been provided by agile methods. The agile methodology has been introduced due to some existing lacks in software development. Now agile methodology is used to overcome these deficiencies and improve software development. The use of the agile methodology is increased within software industries due to its distinctive features such as enabling change requests from the client at any stage of a project, client satisfaction, iterative development, and clientdeveloper interaction. Another reason for agile adoption is the methods that are being used for agile software development. These methods include Scrum, Feature drive development, Extreme programming, and Dynamic system development methods. However, the agile methodology has some issues for project development and management. In this study, we discuss all these issues which are related to agile methods and individuals (i.e. team and developer). Further, we suggest the possible improvements that need to be introduced in the agile methodology. We believe such improvements is to make the agile methodology more productive for development environments.

show abstract

Planning Poker in cost estimation in Agile methods: Averaging Vs. Consensus

Cited by 20 publications

References 22 publications

A software-based cost estimation technique in scrum using a developer's expertise

A software-based cost estimation technique in scrum using a developer's expertise

Systematic Literature Mapping of User Story Research

Project Management Issues While Using Agile Methodology

Contact Info

Product

Resources

About