" Topic Three: How will the chosen work get done?

For each selected Product Backlog item, the Developers plan the work necessary to create an Increment that meets the Definition of Done. This is often done by decomposing Product Backlog items into smaller work items of one day or less. How this is done is at the sole discretion of the Developers. No one else tells them how to turn Product Backlog items into Increments of value. "

- The Scrum Guide (TM) of 2020.

Defined measures of value will vary by organization. For example, the EBM looks at 4 Key Value Areas where all 4 areas contribute to an organization’s ability to deliver business value. Revenue is only a single measure of many that the Product Owner must take into consideration.

As a collaborator, the Product Owner, is responsible for engaging with and closely working together with the Developers. He/she supports them in optimizing the work it performs in order to accomplish the Sprint Goal and create the anticipated Increment.

Technical debt is any shortcomings in the code. It is a natural by-product of software development (unavoidable) and can at best be managed. If neglected, it will compound and have a negative effect on the team's ability to the deliver value. A team can have an artificially high velocity by taking shortcuts or introducing technical debt into the system. This can give a false assumption about the current state of the product. It can look good on the surface but underneath can be a mess.

The Product Owner ensures that attendees are prepared to discuss the most important Product Backlog items and how they map to the Product Goal. The Scrum Team may also invite other people to attend Sprint Planning to provide advice.

Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.

In Scrum, the length of the Sprint Planning meeting can vary depending on the length of the Sprint and the complexity of the work that needs to be planned.

Note: There is no need to decompose all the Items in the Sprint Backlog. It can be done only for the first days of the Sprint.

People personally commit to achieving the goals of the Scrum Team by doing their best and helping others.

Successful use of Scrum depends on people becoming more proficient in living five values: Commitment, Focus, Openness, Respect, and Courage

Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint. They are also self-managing, meaning they internally decide who does what, when, and how.

Self-managed teams allow teams to creatively solve difficult problems, be accountable for the work they do, and commit to each other and the goals of the team.

Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.

The Product Owner manages Product Backlog against the assumption that value will be generated. Indications of value on Product Backlog are useful but are only a prediction until validated against users and market.