Back to Forum

Sprint Goal and MVP

Last post 05:02 pm September 10, 2020 by Ian Mitchell
1 reply
Karina Alfaro Cordoba
01:14 pm September 10, 2020

I've been struggling with the sprint goal of creating "a potentially shippable product increment". There are instances where that is just not possible as most of the sprint may require doing design work before committing to code. How do you wrestle with this fact and avoid falling in the trap of doing multi-sprint design, then develop that could send you back to waterfall-land?

Ian Mitchell
05:02 pm September 10, 2020

Every Sprint ought to yield a potentially shippable product increment, no matter how small it may be. Whether most of the work undertaken in a Sprint is design -- or perhaps the setup of infrastructure or architecture or the remediation of technical debt -- is not necessarily a great concern.

In your situation, is a complex product being worked on, for which empirical process control would be important? Are there significant unknowns or risks to be reduced? If so, then Sprint Goals ought to be of better service. What is there to be learned or validated each new Sprint, in the timeliest way, and by the smallest piece of feature functionality?

 

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.