Related Posts
This is the crux

Additional Posts in Product Management
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
This is the crux

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Download the Fishbowl app to unlock all discussions on Fishbowl.
Copy and paste embed code on your site

Scan your QR code to download
Fishbowl app on your mobile

Mentor
For me, pretty hands on. I think this depends on the team structure and asks of the PM, so context is important. My team doesn’t have a scrum master, so I largely end up facilitating the key ceremonies, including the daily scrum call (not that it requires all that much facilitating).
I also do end up using my scrum in practice as a discussion forum for the team to actually discuss more detail than I think traditional scrum would suggest you should, so that may play into it 🤷🏼♂️
Mentor
I think that is pretty normal. The scrum master should run the meeting, it’s their job.
My experience—when that structure is in place, I’d be very attentive so that I was always aware of what was going on, so listening pretty intently to understand the work that’s happening and any challenges. That helped facilitate conversations with my developers so they didn’t need to catch me up.
Bowl Leader
I’ve been on both ends of the spectrum. In my last company, the culture was such that the PM essentially defined all the stories and drove those meetings, including facilitating the conversation around technical sub-tasks and explorations.
In my current company, PMs are out of the backlog and are asked to keep focus higher level. I participate in our scrum meetings and give input when I think things are going the wrong direction or if there’s a user need being misunderstood, but don’t drive them anymore.
I liked both ends
The correct answer is you shouldn’t be at all unless your team is very green.
Scrums are meant to be at most 15 minutes to give an update on what you worked on yesterday, what you’re working on today, and are you facing any impediments. Any elaboration should happen outside the scrum. If you’re hands on in the scrum then it’s not a scrum anymore and indicative of a lack of agility. If I was an agile lead it would make me look into your team and watch for anti-patterns.
This applies to all meetings as well except backlog refinement where was a PO/PM you need to be hands on since that’s where your vision comes to life or where corrections need to happen.
Following above. I use to be involved with all
Tickets and scrum activities “ceremonies” measuring and tracking all work. Now my role is shifting on the commercial side which is somewhat unique but our company splits the product development work from the commercial line of business / GTM.