In Scrum, the Product Owner, one side of the triangle that makes the Scrum Team, is the single point of contact for the Team – the cross functional group of people that are producing the work. The Product Owner has a chance to alter the direction of development at the end of each Sprint, through the prioritization of the Product Backlog. If you want your feature to be added next, if you need something changed, or if you have a bug that you’ve found, you tell it to the Product Owner. There’s a reason for this.
Talk with a developer in an organization of any size and I bet that you will hear stories of the best laid plans derailed by someone coming to him or her and saying something like, “I need you to add feature x. It’s more important than what you’re doing now, and I need it done asap. It should be pretty easy.” This is a sad fact for many developers out there. That simple feature usually turns out to be non-trivial, and takes days to add. The release is missed, and everyone wonders why. The developer gets blamed, the developer blames the requester, and everyone is unhappy.
This should not, and does not, need to happen. Let the Product Owner do his or her job, and ScrumMaster and Team, help them do it. Don’t mess with the Team,
Other Posts That Might Interest You
