Skip to main content

How to decide on timeline where validation happens in separate sprint

Last post 08:46 am April 17, 2018 by Ian Mitchell
2 replies
01:19 pm April 16, 2018

How shall we structure our timeline where the development happens for 1 month and validation takes another 1 week.

PI 1

Sprint 1.1 (1 month)

      VS 1.1.1 (1 week)

Or is there a better approach to it?


06:18 am April 17, 2018

If validation happens in another sprint, are you actually spinting?

A sprint is a fixed timebox wherein a part of the Product Backlog is developed into a potentially shippable product increment. Would you really ship an increment if it hasn't been validated?


08:46 am April 17, 2018

In Scrum work must be planned and delivered to release quality in Sprints of one month or less. That’s the timeline.

It’s more likely to be the way your teams are organized which needs restructuring, if they are to apply Scrum and deliver better value.


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.