Great explanation. I think this is first time I see concise explanation in video, however one small but crucial detail is wrong. Product owner in scrum is not a role but accountability, it is on purpose to make it clear that product owner is not a role to replace or complete with the Product Manager, but accountability to be taken inside of the scrum process by product manager.
Thanks for your feedback. We both agree that product managers can act as product owners in Scrum, which is great. If "product owner" is just an accountability (as the 2020 Scrum Guide seems to suggest) or a role does not make a difference in practice in my experience.
I think you are right--it's a step in the right direction. As the product owner role/accountability--like the ScrumMaster and developer ones--have been, generally speaking, misunderstood and misapplied so badly, it would be best IMO to drop the product owner term altogether and describe Scrum as a collaborative development framework that requires a team member who manages the product, who is empowered to have the final say on product decisions if no agreement can be reached, and who is accountable for maximising the value the product creates. Thanks for bringing this up!
Clear, concise and so much more useful video than many hour-long videos on this. I loved the way you started from the genesis of the PO role and what it was actually meant to be and the changes over time. Great video, Roman.
Thank you for this video. I got this question in one of my interviews and I was stuck. From my perspective, the responsibility overlaps, or at least from the organizations I have been part of because we do not have both roles. Your closing statement at 05:40 is definitely a mic drop and will quote this in my next interview.
Thanks for the clear differences between these roles, Roman! I know it depends on the organisation but it sounds like pursuing the CSPO certification will cover a lot more ground compared to SAFe Product Owner/ Product Manager certification? I'm currently considering one of these options. Many thanks
You're welcome Dab. I am not the best person to advise on certification. But I recommend finding a course that offers the right content and is taught by someone you respect. Hope this helps!
Hi Roman i am very much with you adding never the less another perspective. 1. What if a product needs more then one Scrum Team to develop? A Product Owner is very helpful per Scrum Team, but he can not own the whole Product anymore independent from the scaling Framework. 2. I find it helpful that in this case a Product Owner is very much User focused (User Stories) on how to use eg. but not only (UX) (parts) of the Product and a Product Manager can focus more on the buyer of the product, what is very helpful in B2B may be not so much in B2C Products... Are this meaningful thought's?
Thanks for your comment Kurt. When a product is too big to be managed by a single individual, you have four choices: First, you empower end enable the development teams to take on some of the detailed, tactical product decisions. Second, you use a strategic product role (like the SAFe product manager) and a tactical one (like the SAFe product owner). Third, you employ roles that manage bigger product capabilities or features (like the Area Product Owner in LeSS). Fourth, you break up the product by unbundling one or more features or by creating product variants. None of these options is perfect; they all have benefits and drawbacks, as I explain in more detail in the following blog article: www.romanpichler.com/blog/scaling-the-product-owner/ Hope this helps.
Thanks for the feedback Chris. Glad you liked the video. I don't think it matters if you use Scrum or Kanban. In both cases, it is important to understand who you is responsible for product success and who has the final say in the key product decisions. Regarding Marty Cagan's views, I recommend reaching out to him directly. But make up your own mind and determine which product roles you should use at your company.
Thank you for simplifying the differences between two and explaining it . This is very valuable Roman!Can you please explain how a BA role would fit in the development team and is it advisable to have Product manager , product owner and BA roles in one Scrum team?if yes how would the responsibilities be segregated?
Thanks for sharing your feedback and question Minal. I write about the business analyst in an agile, Scrum-based context in the following article: www.romanpichler.com/blog/business-analysts-in-scrum/ Please leave a comment on the article if it doesn't answer your question, and I'll get bak to you :)
Great explanation. I think this is first time I see concise explanation in video, however one small but crucial detail is wrong.
Product owner in scrum is not a role but accountability, it is on purpose to make it clear that product owner is not a role to replace or complete with the Product Manager, but accountability to be taken inside of the scrum process by product manager.
Thanks for your feedback. We both agree that product managers can act as product owners in Scrum, which is great. If "product owner" is just an accountability (as the 2020 Scrum Guide seems to suggest) or a role does not make a difference in practice in my experience.
@@RomanPichler i agree, but it does make it clearer.
I think you are right--it's a step in the right direction. As the product owner role/accountability--like the ScrumMaster and developer ones--have been, generally speaking, misunderstood and misapplied so badly, it would be best IMO to drop the product owner term altogether and describe Scrum as a collaborative development framework that requires a team member who manages the product, who is empowered to have the final say on product decisions if no agreement can be reached, and who is accountable for maximising the value the product creates. Thanks for bringing this up!
Clear, concise and so much more useful video than many hour-long videos on this. I loved the way you started from the genesis of the PO role and what it was actually meant to be and the changes over time. Great video, Roman.
Thank you, Prasad. I am glad that you liked the video.
This cleared all my doubts, thank you, Roman. You are truly a Guru in Product Development.
You're welcome. I am glad that you found the video helpful.
Thank you for this video. I got this question in one of my interviews and I was stuck. From my perspective, the responsibility overlaps, or at least from the organizations I have been part of because we do not have both roles. Your closing statement at 05:40 is definitely a mic drop and will quote this in my next interview.
Thanks for the feedback Bernadette. Glad the video was helpful!
ROMAN, you are awesome. Good one again.
Thank you!
Thanks for the clear differences between these roles, Roman! I know it depends on the organisation but it sounds like pursuing the CSPO certification will cover a lot more ground compared to SAFe Product Owner/ Product Manager certification? I'm currently considering one of these options. Many thanks
You're welcome Dab. I am not the best person to advise on certification. But I recommend finding a course that offers the right content and is taught by someone you respect. Hope this helps!
Hi Roman i am very much with you adding never the less another perspective. 1. What if a product needs more then one Scrum Team to develop? A Product Owner is very helpful per Scrum Team, but he can not own the whole Product anymore independent from the scaling Framework. 2. I find it helpful that in this case a Product Owner is very much User focused (User Stories) on how to use eg. but not only (UX) (parts) of the Product and a Product Manager can focus more on the buyer of the product, what is very helpful in B2B may be not so much in B2C Products... Are this meaningful thought's?
Thanks for your comment Kurt. When a product is too big to be managed by a single individual, you have four choices: First, you empower end enable the development teams to take on some of the detailed, tactical product decisions. Second, you use a strategic product role (like the SAFe product manager) and a tactical one (like the SAFe product owner). Third, you employ roles that manage bigger product capabilities or features (like the Area Product Owner in LeSS). Fourth, you break up the product by unbundling one or more features or by creating product variants. None of these options is perfect; they all have benefits and drawbacks, as I explain in more detail in the following blog article:
www.romanpichler.com/blog/scaling-the-product-owner/
Hope this helps.
great video
- how do you see product roles working in a kanban context?
- how do you compare your views vs Marty Cagan's?
Thanks for the feedback Chris. Glad you liked the video. I don't think it matters if you use Scrum or Kanban. In both cases, it is important to understand who you is responsible for product success and who has the final say in the key product decisions. Regarding Marty Cagan's views, I recommend reaching out to him directly. But make up your own mind and determine which product roles you should use at your company.
Thank you for simplifying the differences between two and explaining it . This is very valuable Roman!Can you please explain how a BA role would fit in the development team and is it advisable to have Product manager , product owner and BA roles in one Scrum team?if yes how would the responsibilities be segregated?
Thanks for sharing your feedback and question Minal. I write about the business analyst in an agile, Scrum-based context in the following article:
www.romanpichler.com/blog/business-analysts-in-scrum/
Please leave a comment on the article if it doesn't answer your question, and I'll get bak to you :)