Skip to main content

Product Owner Exerting Leadership At Standup

Last post 07:10 pm July 1, 2016 by Alan Larimer
8 replies
05:41 am June 17, 2016

I read an interesting passage from this book (no need to buy, I've copied & pasted the text below)
https://www.amazon.com/Agile-Data-Warehousing-Project-Management/dp/012…

"Fully engaged product owners sometime exert project leadership on a daily basis to the point where they can stand before the task board each morning, driving the team with tough questions that used to come from a project manager:

- Why aren't more task getting completed?
- Why are the remaining labor estimates ballooning?
- What are you folks planning to show during next week's demo?"


Thoughts / opinions?


10:22 pm June 17, 2016

Perhaps this sort of thing illustrates why Ken Schwaber felt it necessary to create scrum.org.


01:35 pm June 20, 2016

I would not classify this behavior as "exerting leadership". It smells more like exerting micromanagement and mistrust.

Any belief where one feels the need to "drive" the team and question their progress on a daily basis is quite simply the opposite of Agile/Scrum.


08:15 pm June 21, 2016

Just keep in mind that one of the main characteristics of a Development Team is that it's self-organizable and no one but the Development Team itself tells it how to perform its work.


08:03 pm June 23, 2016

What happens if the scrum master is failing to exert leadership and the team is not self-organizing around this deficit? I work on a very small team as the PO, and am currently struggling with the Scrum Master's failure to lead AND failure to deliver as a developer. Honestly looking for pointers on how to handle this.


02:07 pm June 24, 2016

Meghan,

What leads you to believe that the Scrum Master for your team is not doing an effective job?

Regarding the development issue, the team has ownership of all sprint backlog items and the sprint goal. If the team is not delivering, that must be treated as a team issue, and not a deficiency with any single team member.


01:33 am July 1, 2016

One of the biggest problems I've seen with organizations and implementing Scrum is with the Daily Scrum. I believe that it is because of articles such as the one in the opening post or the Scrum For Dummies book. People not in the Development Team want to oversee or participate in that event. It becomes a status report. Although there can be value in a quality Scrum Master occasionally observing and providing feedback OUTSIDE OF THE EVENT, it is made very clear in The Scrum Guide that this is for Development Team members only and NOT a status report. Trust the senior members to foster the conversation and build a safe environment for holding each other accountable to commitments. Despite the source literature, quotes, and videos from Ken and Jeff . . . this is a problem that is almost always present highlighting the true lack of Agile mindset in people and organizations.

U agree, Ian, this is why Scrum.org exists,


02:40 pm July 1, 2016

Hi Andrew,

On a general note, the PO is not a mandatory participant in dailys. He may participate with the main purpose of feeling the team's spirit/motivation and only if he does not speak. The daily is for the team and the SM only in order to sync and to raise impediments.

Michael


07:10 pm July 1, 2016

"The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum."

It is that simple. If the Product Owner, a manager, a maintenance person, the CEO, or anyone else is there then the Scrum Master is not fulfilling the duties of the role: "The Scrum Master is responsible for ensuring Scrum is understood and enacted."

--------------------------

@Meghan Turjanica: Mixing responsibilities (DT member as SM, DT member as PO, SM as PO) leads to issues. I understand that this happens in smaller organizations and those just learning Scrum, but it is highly beneficial to segregate the responsibilities as soon as possible. During the Sprint Retrospective is that place to bring your concerns to the entire Scrum Team and work together to find a solution to implement.


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.