Welcome back to a new week and new cartoon at www.implementingscrum.com.
For new subscriber via email, facebook, and twitter — Welcome and thanks for the interest in the site.
Please feel free to pass this site on to your friends and talk about it on twitter and other social networking sites.
The problem depicted in this cartoon is something I see a LOT when working with teams around the world.
Even when Scrum is being implemented on teams within an organization.
So what do we do about this situation?
When asked for a status from a Chicken within a Sprint, Scrum talks about the team members not saying, “No” and punting it to the Product Owner.
The same goes for a new feature request.
In the past… before Scrum… this type of request was a major cause of never getting to “Done.”
This is the main reason to have a strong demarcation point between the Product Backlog and the Sprint Backlog. The main reason is to help shield the team from the outside “Noise”.
Care to share some real life stories about this via comments below?
How do you do this without committing career suicide?
Who really is responsible for telling outside Chickens to speak with the Product Owner?
What does the Product Owner need to do with this next?
Is this really an important concept or what do you think about it?
Please share with us…
- mike vizdos