Product Owner - Your job Just Got Easier
Introduction
Thank you and congratulations on taking this class, “Agile Product Management:Product Manager vs Scrum Product Owner”.
When you have taken this class, you will understand the similarities and differences between traditional Product Management and Scrum Product Ownership. In order to develop a product from original concept to working model, many factors must be taken into consideration. Clients and stakeholders might have a clear idea of what they want and when they want it. In such cases, it is the product owner’s responsibility to clarify all of the details and enable the development team to generate the final product as quickly and inexpensively as possible. If the client and stakeholders are not as certain about what it is that they want, the product owner has the added responsibilities of helping them to figure out what they want and articulating this to the developers. In each segment of a development project the roles and responsibilities of product managers and product owners differ substantially. In each class, we will examine a component of product development and identify the different ways that these two roles approach them. In this class you will learn:
•An overview of the two product development methods
•How to manage requirements as a product owner as opposed to a traditional product manager
•How to plan a project as a product owner versus a traditional product manager
•How to schedule a project as a product owner as opposed to a traditional product manager
•Common methods for budgeting a project as a product owner versus that of a traditional product manager
•Tips for becoming a product owner in your team or business
Now, let us move forward and let me help you to learn the differences between a traditional product manager and a scrum product owner.
Introduction
Thank you and congratulations on taking this class, “User Stories: How to capture, and manage requirements for Agile Product Management and Business Analysis with Scrum”.
In this class, you will be given proven methods to create, maintain and manage your requirements using user stories as part of an agile scrum team.
I know you will get value from this class as it gives you a full introduction to the concept of agile user stories for managing product requirements. I then walk you step by step through everything involved in managing requirements using user stories including writing, combining and splitting complex user stories. Following this, I give you a complete overview of epics and themes and how they can be used to capture and group complex requirements in any team or business. Along the way, I give you plenty of examples and give you best practices for working with user stories within agile scrum. In this class, you will learn:
•What User Stories are and why they are so powerful for capturing requirements in complex projects
•Feel confident in writing user stories for any project
•Understand what a Requirements Spec is and Why they are less flexible than a Product Backlog built with Agile User Stories
•Explain what The Three Rs rule, Acceptance Criteria, the INVEST Principle, the Three Cs principle and Edge Cases are and how they will make you a better user story writer or agile practitioner
•Understand how and when to split and amalgamate stories
•Learn techniques to help you to split user stories when working in the real world
•Understand the difference between Epics and Themes and when each is used
Learn who is responsible for writing user stories in agile and scrum
So let’s get started and let me teach you how to improve product backlog management.
