Data Analysis in Sprints
Hello everyone
I wanted to guage your views on data analysis during a 3 week sprint, should this be a sprint activity or pre-sprint?
Just trying to weigh up as not really adding business value end of the 3 weeks, its more of a data discovery.....
Many Thanks.
Without knowing other info, it's safe to say a spike sounds like a good idea to perform the analysis. It's best to keep the spike timeboxed (say, 20 hours).
Is/will this "data discovery" be linked to backlog work?
I wanted to guage your views on data analysis during a 3 week sprint, should this be a sprint activity or pre-sprint?
Just trying to weigh up as not really adding business value end of the 3 weeks, its more of a data discovery.....
Presumably - if the results of the data analysis are put in delay - the usefulness of it will degrade. The short answer is, therefore, that data analysis ought to occur as a Sprint activity.
In agile practice, information should be obtained in a timely manner, so as to support inspection and adaptation.
in addition to Ian, I would state that it depends on the purpose the data analysis is ment to serve for?
If it is necessary to produce a done increment of your product, well then it is obvisiouly a task to be considered and estimated within the sprint backlog.
If the data analysis is needed to decide on the value of product backlog items or to specify user storys more precisely. Then it is not part of the sprint, as it does no value add to the product, nor influences architecture. This would be something to be handeled by the product owner beforehand (maybe within the refinement meetings if support of the development team is needed.
Best regards,
Marc