Back to Forum

Business Implementation AFTER delivering the Increment

Last post 11:21 am March 7, 2019 by Jörg Häcker
2 replies
Joost van Poppel
08:51 am March 7, 2019

Hi,

Our scrum-teams deliver Done Increments each sprint.

But after deploying there also is a "business implementation"; 

- Business inscructions on how to use the new features to users

- Classes on how to use new features to users

- New/Changed "Standard Operating Procedures" within business.

- Setting up / configuring of Change Management modules.

These tasks can not always be done by the development team or during the sprint.

How would you handle these "business implementation" tasks? Should they be in the Definition of Done? Which role is responsible for the Business Implementation?

Should the Product Owner add  "Support"-userstories for the Dev-Team?

 

Would love to see some insights from you guys.

Thanks,

Joost

Ian Mitchell
10:15 am March 7, 2019

Given that the work you describe is necessary to effect a release, why wouldn’t it be in the Definition of Done? If the Development Team don’t have the associated skills and authorizations, how can they commit to delivering a working increment that meets a Sprint Goal?

Releasing work is necessary to establish empirical process control, and for that to happen, work must be completed every Sprint to release quality.

Jörg Häcker
11:21 am March 7, 2019

These tasks can not always be done by the development team or during the sprint.

Why can these tasks not be done during sprint? From my own experience tasks for this type of work can be quite "heavyweighted".  Maybe there is room for improvement.

I think it is up to the team to find out which approach("Support" User-Stories, DoD, finding responsibilty ...) fits best.  The base is that the team is willing to deliver an increment of release quality every Sprint.

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.