Which type of story would be used when an estimate is not available due to lack of knowledge of the technology required to implement the story?
A. Defect
B. Slack
C. Spike
D. Nonfunctional
One Comment on “Which type of story would be used when an estimate is not available due to lack of knowledge of the technology”
mohsinalish5@gmail.comsays:
In agile software development, a spike is a story that cannot be estimated until a development team runs a time-boxed investigation. The output of a spike is an estimate for the original story.
spike stories are reasonable, as long as they are kept off the Product Backlog. The team would have to introduce them directly into their own Sprint Backlog since they are part of their own plan for delivery, and do not (in themselves) represent product value. However, this is a controversial practice and some authorities do not recognize this type of story as a valid construct at all.
In agile software development, a spike is a story that cannot be estimated until a development team runs a time-boxed investigation. The output of a spike is an estimate for the original story.
spike stories are reasonable, as long as they are kept off the Product Backlog. The team would have to introduce them directly into their own Sprint Backlog since they are part of their own plan for delivery, and do not (in themselves) represent product value. However, this is a controversial practice and some authorities do not recognize this type of story as a valid construct at all.
1
0