Agile Development (Scrum Guide)

The key stages in the process must be evident to those responsible for the output. To achieve transparency, uniform standards must be established for these key stages, so that everyone paying attention to these stages will have a consistent understanding of what they observe.

Scrum users must frequently inspect Scrum artifacts and progress towards completing Sprint goals to identify unnecessary differences. Inspections should not be too frequent to impede the work itself. When inspections are conducted diligently by skilled inspectors during work, they yield the best results.

If the inspector finds that one or more aspects of the process have deviated beyond an acceptable range and will result in an unacceptable product, adjustments to the process or its content must be made. These adjustments must be executed as soon as possible to minimize further deviations.

Maximize the product value developed by the development team

Clearly articulate the product backlog items;

Sort the product backlog items to best achieve the goals and mission;

Optimize the value of the work executed by the development team;

Ensure that the product backlog is visible, transparent, and clear to everyone, while also displaying the next work the Scrum team will undertake;

Ensure that the development team has a thorough understanding of the product backlog items.

The development team includes professionals from various fields, responsible for delivering potentially releasable and "done" product increments at the end of each Sprint. A "done" increment is required at the Sprint Review meeting. Only members of the development team can create increments.

is self-organized

It is a cross-functional team.

Do not recognize any titles of the development team members.

Do not recognize the so-called "sub-teams" within the development team.

Each member of the development team may have their own expertise and focus areas, but the responsibility belongs to the entire development team.

(3, 9]

Ensure that everyone in the Scrum team understands the goals, scope, and product domain as much as possible.

Find tips for effectively managing your product backlog.

Help the Scrum team understand why clear and concise product backlog items are necessary.

Understanding product planning within an empiricist context

Ensure that the product owner knows how to arrange the product backlog to maximize value.

Understand and practice agility.

Guide Scrum events when requested or needed.

As a coach, provide guidance to the development team in self-organization and cross-functional aspects.

Help the development team create high-value products

Remove obstacles in the development team's work progress.

Guide Scrum events as requested or needed.

In an organizational environment where Scrum has not been fully adopted and understood, guiding the development team as a coach.

Lead and coach the organization in adopting Scrum

Planning the Implementation of Scrum within the Organization

Help employees and stakeholders understand and implement Scrum and experience-oriented product development.

Initiate changes that can enhance the productivity of a Scrum team

Collaborate with other Scrum Masters to enhance the effectiveness of Scrum applications within the organization.

Sprint Planning Meeting

Daily Scrum Stand-up

Development work

Sprint Review Meeting

Sprint Review Meeting

Changes that are detrimental to the Sprint goal cannot be made.

a goal that cannot be compromised on quality

As the understanding of information increases, the product owner can clarify and renegotiate with the development team on what needs to be done within the scope.

Cancel before the Sprint time box ends

Only the product owner has the authority to cancel a Sprint.

If a Sprint loses its value and significance to its environment, then it should be canceled.

Because Sprint timeframes are usually short, it is generally not reasonable to cancel Sprint.

Re-evaluation of the review

Cause a severe blow

What should be included in the upcoming Sprint delivery increment?

How can the work required to deliver the increment be completed?

To achieve the goals set out in the product backlog within the current Sprint.

The attendees include the Scrum team and the key stakeholders invited by the product owner.

The Product Owner explains which items on the product backlog are "done" and which are not "done".

The development team discusses what work was done well during the Sprint, what problems were encountered, and how these problems were resolved.

The development team demonstrates the "completed" work and answers questions about the delivered increments.

The product owner discusses the current state of the product backlog.

All attendees discussed the next steps of the work.

The most valuable change to be made next, brought about by reviewing the market or potential product usage methods.

Review the schedule, budget, potential, and market for the next anticipated product feature or capability version release.

Revised Product To-Do List

Inspect how the previous Sprint fared in terms of people, relationships, processes, and tools.

Identify and prioritize the key aspects that are performing well and those that potentially need improvement.

Develop a plan to improve the Scrum team's working methods