Very helpful video as always! Just what I was looking for! Thanks a lot! I am trying to better understand the concept of 'Whole Product Focus' . In a company where there isn't a physical product how do we classify what a product means? My understanding is anything that is used by the end customer internal or external falls under one product category. That includes any projects teams are working on, BAU work, technical upgrade. So the PO should have authority to prioritise all this work based on the risk involved, ROI etc. Is that correct?
In the context of Scrum ... projects, BAU work, technical upgrade, request from CEO ... are considered as Product Backlog item (PBI) ... So you can say that a project is a huge PBI or a PBI that has not been broken down to at least 1 Sprint length. Here's a video that elaborates Product Backlog ua-cam.com/video/pBYSgnXvVOI/v-deo.html.
Yes the Product Owner should have authority to order all the PB based on the risk involved, ROI etc. That's why IMO this is a position that should report directly to senior mgmt and experienced in the domain.
@@scrummasterinblack Thanks Josh for a prompt reply. This indeed is a very important position and needs to have that kind of authority to be able to make the priority decision. The Product ownership needs to be understood and agreed upon on the organisational level
You liken a Scrum Product Owner to a Store Owner, but a Store Owner truly owns all aspects of the Store, not just design and setup. A Scrum Product Owner does not typically own ongoing operations, do they?
Lead Product Owner is an oxymoron. An owner is an owner. A manager who has more ownership than an owner is more confusing. The Product Owner in a scaled environment owns end-to-end. Check out my video on scaling Scrum to see the position of product manager in scaled Scrum ua-cam.com/video/hqKP9eQrUgw/v-deo.html
@@scrummasterinblack VERY helpful! This only further supports my feeling that we are approaching our Learning Path in the wrong way in my company. DevOps and SAFe are adding a lot of confusion to the mix before we even master Scrum and Nexus.
As always awesome 👌
Thanks heaps saishekar 🙏 Much appreciated.
Very helpful video as always! Just what I was looking for! Thanks a lot!
I am trying to better understand the concept of 'Whole Product Focus' . In a company where there isn't a physical product how do we classify what a product means?
My understanding is anything that is used by the end customer internal or external falls under one product category. That includes any projects teams are working on, BAU work, technical upgrade. So the PO should have authority to prioritise all this work based on the risk involved, ROI etc.
Is that correct?
In the context of Scrum ... projects, BAU work, technical upgrade, request from CEO ... are considered as Product Backlog item (PBI) ... So you can say that a project is a huge PBI or a PBI that has not been broken down to at least 1 Sprint length. Here's a video that elaborates Product Backlog ua-cam.com/video/pBYSgnXvVOI/v-deo.html.
Yes the Product Owner should have authority to order all the PB based on the risk involved, ROI etc. That's why IMO this is a position that should report directly to senior mgmt and experienced in the domain.
In a whole product perspective, software is just a component that adds value to the producf.
@@scrummasterinblack Thanks Josh for a prompt reply. This indeed is a very important position and needs to have that kind of authority to be able to make the priority decision. The Product ownership needs to be understood and agreed upon on the organisational level
You liken a Scrum Product Owner to a Store Owner, but a Store Owner truly owns all aspects of the Store, not just design and setup. A Scrum Product Owner does not typically own ongoing operations, do they?
They better own it. If they don’t, the Scrum Master can help the company to have better understanding of PO.
@@scrummasterinblack Or perhaps in the scaled environment, the Product Manager or lead Product Owner would own it?
Lead Product Owner is an oxymoron. An owner is an owner. A manager who has more ownership than an owner is more confusing. The Product Owner in a scaled environment owns end-to-end. Check out my video on scaling Scrum to see the position of product manager in scaled Scrum ua-cam.com/video/hqKP9eQrUgw/v-deo.html
@@scrummasterinblack VERY helpful! This only further supports my feeling that we are approaching our Learning Path in the wrong way in my company. DevOps and SAFe are adding a lot of confusion to the mix before we even master Scrum and Nexus.