Skip to main content

In Scrum with Kanban guide, What's meant by the "Scope of definition of work flow" ?

Last post 05:23 pm May 15, 2023 by Ian Mitchell
2 replies
11:43 am May 15, 2023

Hello Folks, Myself (Emka) Emmanuel Katto From Uganda, Can someone please help me understand what is meant by "Scope of definition of work flow"?

The other thing that I cannot understand from the "Scrum with Kanban guide" is the following paragraph:

"Note that the scope of the Definition of Workflow may span beyond the Sprint and the Sprint Backlog. For instance, a Scrum Team's Definition of Workflow may encompass flow inside and/or outside of the Sprint."

What is meant by "may span beyond sprint and the sprint backlog"? What activities are being mentioned here?. Can someone please explain with an example.

 

Thank You!


04:56 pm May 15, 2023

A workflow may include activities done prior to a Product Backlog Item being selected for a Sprint. An example of this would include things that happen as part of refinement. A workflow may also include activities done outside of a Sprint. In software development, examples of this could be deploying a new version of the software or toggling a feature flag to make changes available to end users. This quote from the Scrum Guide says that the team's workflow may begin before work is selected for Sprint Planning and go beyond when work is considered "Done" against the Definition of Done if there are activities. The specific activities will vary by organization, team, and domain.


05:23 pm May 15, 2023

The guide says that the visualization of workflow should include defined points at which the Scrum Team considers work to have started and to have finished.

Those defined points (such as a Sprint Backlog) can articulate to the framing of certain commitments. Transparency may be enhanced when they are contextualized within the wider workflow.


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.