Agile Framework & the Product
The Role of the Product Owner
The Product Backlog & Scrum Routines
Product Backlog Management
Potpourri
100

This long-term description of what the product should turn out to be helps Product Owners design the future-looking backlog items.

What is the Product Vision? 

100

The person responsible for managing the product backlog and accountable for keeping it "healthy" at least 2 PIs out into the future.

Who is the Product Owner?

100

This work item represents a piece of work to be done.

What is a Product Backlog item?

100

It is the software solution where the ULA Product Backlogs are created.

What is Jira?

100

The work items that make up the "Team Backlog"

What are user-stories/tasks?

200

This is a high-level plan that outlines the product’s direction, focused on describing the program's timeline including milestones, releases, and increments.

What is a Product Roadmap?

200

This is the Product Owner's primary responsibility.

What is creating work plans (to maximize product value)?

200

It is the process of adding (or removing), detailing, estimating, and ordering to product backlog items.

What is the Product Backlog Refinement session?

200

It is how a Product Owner prioritizes items in the Product Backlog Management process.

What is a pre-established prioritization method (focused on business value)?

200

One describes a larger piece of functionality (intent) at the product level, while the other describes a specific activity that needs to be executed in order to create a part of the functionality.

What is the difference between an epic and a task?

300

This ordered list of everything that might be needed to build a product is the Product Owner's responsibility and they are the ones accountable for maintaining it "healthy".

What is a Product Backlog?

300

It is deciding what will be included in the product's intent (functionality) and ranking the product backlog items by using inputs from all stakeholders and methodically assessing the work items' priority.

What prioritizing the product backlog?

300

It is an ambitious yet attainable output that is planned to be accomplished within a Sprint.

What is a Sprint Goal?

300

Weighted-shortest job first (WSJF), Kano Model, Stacked Ranking, RICE (Reach, Impact, Confidence, Effort), and Value vs. Effort

What are examples of prioritization methods?

300

It is the Scrum Team's facilitator of flow and Servant-Leader.

Who is the Scrum Master?

400

These are independent, negotiable, valuable, estimable, small, testable, and actionable pieces of work that are created and completed by the Development Teams.

What is a Task/User-story?

400

Representing the customer and the stakeholders by linking the product strategy to the execution of the work.

What is been a "Linking Strategist"?

400

It is routinely scheduled event that focuses on inspecting (show & tell) the completed work done by the development team in a Sprint (and presented by them) with the stakeholders.

What is the Sprint Demo or Sprint Review?

400

Clear product vision, better transparency, effective inspection, faster adaptation, increased team alignment, and faster product delivery (time-to-market).

What are benefits of the Product Backlog Management process?

400

This is the queueing theory principle (or law) which states that the higher number of items "in progress" in a system, the longer it is going to take for that system to process the items in queue.

What is Little's Law?

500

This timeboxed activity represents the sum of all the product backlog items that are planned to be completed in a series of sprints.

What is a Program Increment (or PI)?

500

Going to the future of the program and back to the present to translate the product's strategy into features/epics that the Dev Teams can use to plan their tasks.

What is been a "Time-Traveler"?

500

It is an inspection of the sprint itself to identify improvements that development teams can do at the process level or at the ways of working level. Product Owner Teams can focus on their routines to find areas of improvement.

What is a team's Sprint Retrospective?

500

Scope creep (emergent work), changing priorities, dark work, incomplete work descriptions, absent definition of done or acceptance criteria, and inaccurate estimates.

What are obstacles to adequate prioritization?

500

It describes the minimum characteristics of a product with just enough working functionality to satisfy early needs and can be iteratively improved.

What is "Minimum Viable Product" (MVP) a.k.a. First/Next Viable Product (F/NVP)?

M
e
n
u