Skip to main content

Simple Task

Last post 03:34 pm September 15, 2021 by Daniel Wilhite
3 replies
09:49 pm September 14, 2021

if the PO asks for a small and not very important modification that won't even take one minute we can do it without putting it in the PB and it can be realized at any sprint!!


02:26 pm September 15, 2021

If it's not very important, why would it not go on the Product Backlog? Context switching is very expensive. Only a Developer would be able to confirm that it is indeed a small modification, so you'd be asking a Developer to context switch away from important and valuable work to look at and understand the modification, confirm that it's small, and then do that unimportant thing.

Considering that a Product Owner's responsibility is to maximize the value of the work done by the Scrum Team, I can't see how asking for the modification would be consistent with that responsibility.


03:17 pm September 15, 2021

if the PO asks for a small and not very important modification that won't even take one minute we can do it without putting it in the PB and it can be realized at any sprint!!

What is the effect of this practice on transparency?


03:34 pm September 15, 2021

One minute of coding is only part of the time it takes to do anything. That developer has to switch stash the work that they are doing now, create a new branch, make a code change, test the code change, submit the code change to the source code repository, wait for the build process to complete, deploy the change to production, etc.  Then the developer will have to context switch back to the original work that they were doing. 

This can be disruptive and should be VERY CAREFULLY weighed against the work that is already in progress.  Something simple usually isn't something that is critical to have done so it can usually wait until at least the next 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.