Title: Agile Product Management with Scrum: Creating Products that Customers Love

Q: Product Owner
A: The Product Owner is the one and only person responsible
for managing the Product Backlog and ensuring the value
of the work the team performs. This person maintains the
Product Backlog and ensures that it is visible to everyone.

Q: Characteristics of a Product Owner
A: Visionary and Doer
Leader and Team Player
Cummunicator and Negotiator
Empowered and Committed
Available and Qualified

Q: Collaborating with the ScrumMaster
A: The product owner is primarily responsible for the “what”—
creating the right product. The ScrumMaster is primarily responsible for the “how" --using Scrum the right way.

Product Owner Hierarchies

Q: Common Mistakes
A: - Entrusting insufficient authority in the product owner
- Product owner as a committee
- Splitting product owner role amongst multiple people
- Over-working the product owner
- Failing to relieve the product owner of (all) other responsibilities,
- Insufficient team support for the product owner,
- Distance
- Proxy product owner
- No vision
- Prophecy vision
- Analysis paralysis
- We know what is good for our customers
- Big is beautiful
- Requirements over-specification
- Wish list for Santa
- Requirements push
- Grooming neglect
- No release burndown or plan
- Product owner not driving the release plans
- Big-bang release
- Quality compromises
- Bungee product owner
- Passive product owner
- Unsustainable pace
- Smoke and mirrors
- Reporting up the sprint burndown

Q: A Vision
A: The vision describes why the project is being undertaken and what the desired end state is.

Q: Qualities of the Product Vision
A: Shared and Unifying
Broad and Engaging
Short and Sweet

Q: Creating Product Vision Methods
A: - Using Pet projects: “activity or goal pursued as a personal favorite, rather than because it is generally accepted as necessary or important.”
- Using Scrum: other than building software they can build any kind of artifacts as long as they are “working”.
- Making Pro Prototypes and mock-ups . They will help you with experimenting with your ideas and vision and see the cause and effect if you use prototypes rapidly.
- Personas and scenarios. Just like prototypes, the same works happen but with addressing the customers and different situations.
- Vision box and trade journal review. It’s like a branding campaign but to see what and much value the package of the product will add.
- Kano Model. A model to classify the customer’s requirements and satisfaction.

Q: Product Backlog
A: The product backlog is a prioritized list of user stories that might be needed in the product.

Q: The DEEP Qualities
A: Detailed appropriately: Higher-priority user stories will have more detail and are smaller but gradually they become larger with fewer details because the team cannot act on them.
Estimated: The efforts should be estimated with a standardized measure according to the team. Stories at the top have more precise estimations.
Emergent: the product backlog gets updated regularly and the details and priorities emerge from the processes and the feedback.
Prioritized: backlog should be ranked based on the value and strategic purpose of the items, which is top to bottom kind of place.

Q: Sprint Planning
A: Sprint planning is a timeboxed working session that lasts roughly 1 hour for every week of a sprint. In sprint planning, the entire team agrees to complete a set of product backlog items. This agreement defines the sprint backlog and is based on the team's velocity or capacity and the length of the sprint.

Q: Daily Scrum
A: The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. The Daily Scrum is held every day of the Sprint. At it, the Development Team plans work for the next 24 hours.

Q: Sprint Backlog
A: The sprint backlog is a list of tasks identified by the Scrum team to be completed during the Scrum sprint. During the sprint planning meeting, the team selects some number of product backlog items, usually in the form of user stories, and identifies the tasks necessary to complete each user story.

Q: Sprint Retrospective
A: Via the sprint retrospective process, the team examines how work is carried out and identifies ways to improve it.