How do you handle "partial" releases?

Last post 02:26 pm April 10, 2015 by Ian Mitchell

1 reply

10:15 am April 10, 2015

Hi,

Hope someone can help. Not so much a Scrum question as a SDLC question.

How do you go about doing a partial release.

This is the scenario.

Client gives us 5 items to work on. We complete all 5 but 1 gets rejected. The client now wants us to release the 4 items that have passed QA but not the 1 that failed.

Is there a best practice or best procedure to follow here? Doing a branch per issue is going to become a mission to manage.

Any thoughts and advice please.

Thanks,
Justin

Ian Mitchell

02:26 pm April 10, 2015

Assuming the 4 items are genuinely complete, what is stopping the client from releasing an increment of the value that has accumulated? If the client is looking to you to "do" something, it suggests that at least some work remains undone.

In Scrum a Product Owner should be in a position to release an increment of work that meets the Definition of Done where there is value in doing so.

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.