1:20 Product owner should be from the business side to close the gap between business and IT 2:10 A good product owner needs to know the business world - the customers, products, markets; the full context of the product 2:50 The person has mandate to make decision as in what is good/bad, to be/not to build 3:55 Product owner doesn't have to do everything himself. Most importantly, finding values and putting the right orders in the product backlog. The details could be done from the stakeholders, analysts, etc. Product owner can get help from these roles.

Hi Krystian, This is shankar and just sarted understanding the Scrum framework. Is it mandatory to have Scrum Master from IT / Tech team? Can a BA become Scrum master

@ScrumOrg

6 жыл бұрын

Shankar, it doesn't matter where in the organization the Scrum Master comes from, what matters is that they have the right capabilities and understanding of Scrum. Check out this blog that addresses this topic specifically: www.scrum.org/resources/blog/should-scrum-master-be-technical

Hi Krystian, How do we incorporate lean agile methods as a Product owner?

@KrystianKaczor

5 жыл бұрын

Hi Saravanan, What do you mean as "lean agile methods"? In what sense?

Thank you for your opinion. Can you explain in other video what is the typical day of product owner?

@ramjam6712

2 жыл бұрын

The main job of a product owner is to be a proxy product manager. 1. So a typical day would be to have a meeting with the stakeholder understanding the context of the product. 2. Create and Refine the product backlog by adding user stories and prioritizing the backlog after understanding the value the story adds to the product. This is for the upcoming sprint. 3. Clarifying the questions that the team may be with the current sprint. 4. Attend the standup meeting to know the progress of the sprint and to mitigate and issues 5. Have a meeting with partners regarding mitigation challenges. 6. analysis of requirements possible usecases and how the product should perform under those scenarios and add it to the user story. 7. Facilitate sprint planning sessions at the start of a sprint clarifying the team with the requirements and help them get to the sprint backlog. 8. Provide analytical insights about customer trends to help with marketing

@diegofernandez597

2 жыл бұрын

@@ramjam6712 thank you so much for your answer.

Hello! I have a question. I am currently a 6+ years of experience in test engineer(manual) having an hands-on experience on scrum methodology. And would like to change my stream and planning to become a product owner. Just curious if I can/am eligible to enter the product owner job?

@KaziShahinWebdevelopment

3 жыл бұрын

Would be a good choice

@jiml3881

3 жыл бұрын

@@KaziShahinWebdevelopment thank you !

How to priortise product backlog?

@KrystianKaczor

4 жыл бұрын

We prefer to use order instead of priority. Priority is one of the factors to decide on the order and there are couple of issues with priority. Priority can be subjective, multiple PBIs can have high priority, it might be not possible to build the product looking at priority only, priority doesn't always mean value. To decide on the order you need to take under consideration at least priority, value, risk, dependencies: business process, technical, external. You can use some techniques or tools to decide on value and priority like 500 points, theme scoring, OKRs, etc. The criteria and tools are context-specific. You need to decide what fits best your context.

Hi, I would like to know 2 things: 1. Can we have several Product Owners (for example: one for sales, one for finance and one for marketing) 2. Is it allowed to have a Business PO (from business) and an IT PO(from development team) Thanks.

@ScrumOrg

4 жыл бұрын

Parvez Soobhany you have one Product Owner per product. Many people can give input to the PO as stakeholders but only one is responsible.

@welcometosundriesjoinusons9793

Ай бұрын

hi soobhany, the Business PO aka PO with a Scrum Master and Dev Team that strive to be self-managing are your "IT PO," they are baked into the cake of the Scrum Team, Scrum on!

Starts at 1:17