Skip to main content

Is it OK to have tasks that are no associated with a user story in your sprint backlog?

Last post 11:46 pm March 15, 2018 by Ian Mitchell
2 replies
08:47 pm March 15, 2018

Hello,

Is it OK to have tasks that are no associated with a user story in your sprint backlog?  Should my team not be allowed to do this sort of thing?  What are other scum teams do with these tasks?  

Thanks,

Paul


11:01 pm March 15, 2018

If the Development team feels that the task is needed to accomplish the Sprint Goal, then why would it not be part of the Sprint Backlog?  The Sprint Backlog should make all work visible, and there are no rules as to whether or not the work has to be expressed as a story or a task.

Scrum makes no mention of a user story (that comes from XP), although they are a find way to describe a Product Backlog item.

Does your team have a Sprint Goal?

All the best


11:46 pm March 15, 2018

What are other scum teams do with these tasks?  

They should implement at least one priority item from the last Sprint Retrospective, and planning tasks for that might possibly be useful.


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.