2017
DOI: 10.29015/cerem.359
|View full text |Cite
|
Sign up to set email alerts
|

Zwinne szacowanie pracochłonności w projektach programistycznych – studium przypadków

Abstract: Aim:Aim: The purpose of this paper is to identify common mistakes and pitfalls as well as best practices in estimating labor intensity in software projects. The quality of estimations in less experienced teams is often unsatisfactory, as a result of which estimation as part of the software development process is abandoned. The decision is usually justified by misunderstanding "agility". This article is part of the discussion on current trends in estimation, especially in the context of the new "no estimates" a… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
3
0
1

Year Published

2020
2020
2023
2023

Publication Types

Select...
4

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(4 citation statements)
references
References 13 publications
0
3
0
1
Order By: Relevance
“…Even though Labedzki et al [40], when examining the performance of Planning Poker in multiple projects with diverse characteristics, found that "Planning Poker is a technique which yields good results in any undertaking, increasing the estimation precision and raising the level of understanding user stories which await their realization", as far as generalization is concerned, our results are limited to projects with a relatively small number of user stories and smaller development teams. The question is whether these three methods would yield similar results with larger development teams with significantly larger set of user stories in the project.…”
Section: Limitationsmentioning
confidence: 78%
See 2 more Smart Citations
“…Even though Labedzki et al [40], when examining the performance of Planning Poker in multiple projects with diverse characteristics, found that "Planning Poker is a technique which yields good results in any undertaking, increasing the estimation precision and raising the level of understanding user stories which await their realization", as far as generalization is concerned, our results are limited to projects with a relatively small number of user stories and smaller development teams. The question is whether these three methods would yield similar results with larger development teams with significantly larger set of user stories in the project.…”
Section: Limitationsmentioning
confidence: 78%
“…However, the most used are those that use expert-based subjective assessment [87]. Planning Poker has been used in the software industry and teaching environment [40,31,19,44]. It can provide reliable estimates compared to single expert estimation [5].…”
Section: Project Settingmentioning
confidence: 99%
See 1 more Smart Citation
“…En las últimas dos décadas, varias encuestas de investigación se han centrado en el esfuerzo del proyecto de software y la estimación del cronograma. Esto es importante, ya que una visión imparcial es esencial para ayudar a la industria a hacer estimaciones más precisas [30].…”
Section: Estado Del Arteunclassified