The Developers is self-managed.

The Product Owner is accountable for effective Product Backlog management, which includes:

● Developing and explicitly communicating the Product Goal;

● Creating and clearly communicating Product Backlog items;

● Ordering Product Backlog items; and,

● Ensuring that the Product Backlog is transparent, visible and understood.

As the Developers work, it keeps the Sprint Goal in mind. In order to satisfy the Sprint Goal, it implements functionality and technology. If the work turns out to be different than the Developers expected, they collaborate with the Product Owner to negotiate the scope of Sprint Backlog within the Sprint.

Only the Product Owner can if needed.

Product Backlog items that can be Done by the Scrum Team within one Sprint are deemed ready for selection in a Sprint Planning event. They usually acquire this degree of transparency after refining activities. Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller more precise items. This is an ongoing activity to add details, such as a description, order, and size. Attributes often vary with the domain of work.

The Product Backlog is a living artifact which is continually kept up to date with the most recent insights.

The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

What is a Sprint Retrospective?

A Sprint Retrospective is a Scrum Event that occurs at the end of each Sprint. The purpose of the Sprint Retrospective is to reflect on the passed Sprint and identify areas for improvement in the next Sprint. The Developers, along with the Scrum Master and Product Owner, review their processes and identify ways to work more effectively together. This event provides an opportunity for the Scrum Team to continuously improve and evolve their way of working. The outcome of the Sprint Retrospective is a plan for the next Sprint that includes actions to address the identified improvements.

Scrum Artifacts:

● Product Backlog (Commitment = Product Goal).

● Sprint Backlog (Commitment = Sprint Goal).

● Increment (Commitment = Definition of Done).

As the individual responsible for maximizing the value of the product, the Product Owner should have a deep understanding of the marketplace in which the product will compete. This includes understanding the needs and preferences of potential customers or users, as well as the strengths and weaknesses of competing products and services.

By having a comprehensive understanding of the marketplace, the Product Owner can make informed decisions about which features and functionality to prioritize in order to deliver the most value to customers or users. They can also use this knowledge to identify potential opportunities or threats in the market, and adjust the product roadmap or release schedule accordingly.

Furthermore, the Product Owner's expertise in the marketplace can also be valuable in engaging with stakeholders, such as customers, users, and the development team. By being able to speak knowledgeably about the market and the needs of potential customers or users, the Product Owner can build credibility and trust, and ensure that everyone is aligned on the product vision and goals.

The result of the Sprint Review is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint. The Product Backlog may also be adjusted overall to meet new opportunities.

The Daily Scrum is a 15-minute time-boxed event for the Developers. Which means 15 mins is the maximum duration, not the minimum. A Daily Scrum can last less than 15 mins.

The Daily Scrum is held at the same time and place each day to reduce complexity.

Daily Scrums improve communications, eliminate other meetings, identify impediments to development for removal, highlight and promote quick decision-making, and improve the Developers' level of knowledge. This is a key inspect and adapt meeting.