Skip to main content

Data Analysis in Sprints

Last post 02:35 pm October 19, 2018 by Marc Betz
3 replies
04:25 am October 17, 2018

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.


07:49 am October 18, 2018

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?


02:58 pm October 18, 2018

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.


05:35 am October 19, 2018

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


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.