Proceedings of the 2020 European Symposium on Software Engineering 2020
DOI: 10.1145/3393822.3432342
|View full text |Cite
|
Sign up to set email alerts
|

An Empirical Investigation of Spikes in Agile Software Development

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2021
2021
2022
2022

Publication Types

Select...
2
1
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(3 citation statements)
references
References 6 publications
0
3
0
Order By: Relevance
“…Working on this user story will gradually fulfill the needs of Epic that have been previously defined. Spike was originally applied to Extreme Programming, where its use was to create prototypes, conduct exploration, investigation and experiment (Al Hashimi and Gravell, 2019). It needs to be done to find out how complex is the program/application that will be developed using the part that is being explored.…”
Section: Software Developmentmentioning
confidence: 99%
“…Working on this user story will gradually fulfill the needs of Epic that have been previously defined. Spike was originally applied to Extreme Programming, where its use was to create prototypes, conduct exploration, investigation and experiment (Al Hashimi and Gravell, 2019). It needs to be done to find out how complex is the program/application that will be developed using the part that is being explored.…”
Section: Software Developmentmentioning
confidence: 99%
“…In Agile terminology, Kent Beck coined the name "spike"a simple task aimed at answering a question or gathering information. Spikes are also described in Leffingwell [15]: "Spikes, another invention of XP, are a special type of story used to drive out risk and uncertainty in a user story or other project facet," and in Al Hashimi [23].…”
Section: Substitutionmentioning
confidence: 99%
“…The task-based assessment of exposure during schedule estimation, described here, makes it feasible to flag tasks with exposures for priority treatment. When a high risk task cannot be done early, the risk part should be addressed as a separate spike [23] [14].…”
Section: Agilementioning
confidence: 99%