PO Roles and Responsibilities
- Accountable for Product success
- Defines all Product Features
- Active Participation with Business Stakeholders to have constant updates on business priorities for features
- Responsible for prioritizing the product features/user stories
- Owns and Maintains the Product Backlog and make sure that the backlog is healthy and consistent in nature
- Ensures team is working on highest valued features/user stories
- Accepts/Rejects Development Work Results
- Responsible for Product Backlog Refinement (Backlog Grooming) Meeting
- Responsible for maximizing ROI and increasing value of the product for the customer
- Decides Release Dates and to release working product into production when there is a value to customer
And?
Dear friends
I have a question, would it be nice to form a scrum team with only 2 people? a product owner and a one developer? Or is it that Scrum is in disuse for only a developer? or is the scrum methodology being misused?
What does the Scrum Guide say about team composition and appropriate team size?
Dear friends
I have a question, would it be nice to form a scrum team with only 2 people? a product owner and a one developer? Or is it that Scrum is in disuse for only a developer? or is the scrum methodology being misused?
One of the main points of scrum is team work; hard to have teamwork with only 1 developer. Is Scrum really the best framework to be employed in this scenario or is there a better option out there?
"Dear friends
I have a question, would it be nice to form a scrum team with only 2 people? a product owner and a one developer? Or is it that Scrum is in disuse for only a developer? or is the scrum methodology being misused?"
Highly probable that cross functionality would be non-existent. If you have such a small 'garage team' it might be better to consider another framework e.g. (but not only) KANBAN. Accountability remains as does transparency and the ability to track WiP