Scrum artifacts for the basic series of scrum entry

Scrum entry for the basic series scrum artifacts 3 replies

The scrum artifacts consist of 3 main types:

1. Product Backlog
2. Sprint Backlog
3. Product Increment

Product Backlog

In scrum, the product backlog is organized and maintained primarily by the product owner [see the scrum role of the Scrum Starter Foundation series]. The product backlog is the primary component in scrum to maintain requirements and is the first step in scrum. A good product backlog is to conform to the deep principle that the product backlog is detailed slightly appropriate (detailed appropriate), emerging (emergent), estimated (estimated), and sequenced (prioritised). For more information, refer to the "Principles of product backlog and user stories" that I sent before.

In general, what can be included in the product backlog? New features, improvements, bug fixes, documentation requirements, and more.

Sprint Backlog

The sprint backlog consists mainly of the product backlog items that are selected for the current sprint, and the tasks that are based on those items, and one important thing in the sprint backlog is the current sprint target. The team picks it up based on this goal and the sort of product backlog. The content of the Sprint backlog is determined by the team, and the specific methods of work and implementation are determined by the team itself. At this point, fully embodies the team's self-organizing ability.

Product Increment

Product increment is a very important artifact in scrum because the product increment is the content that is ultimately delivered to the customer. Therefore, each sprint team must deliver product increments to comply with the following guidelines:

• The product increment to be delivered must be of high quality. This means that each product increment is potentially available for release.
• The delivered product increment conforms to the team's completion definition (definition of done)
• Product owner (or customer) can accept product increment

In addition, product increments are an indicator of team progress. By continuously delivering product increments, the development team gives confidence to the team itself and its stakeholders, prompting the final release of the product. Team Progress There are other common identifiers that are Burndown charts and task boards. Burndown charts and task boards are generally used to make current progress public to more other teams or stakeholders.

The completion definition means that when the product is incrementally completed, it must be done by the team members in a common understanding, without ambiguity. and the product increment needs to be high-quality, potentially can be released. In other words, when the product owner wants to publish the current product increment, it can be released immediately. The completion of the definition of the team according to the current situation of the team, jointly negotiated, agreed and understood. Also, the definition of completion is not immutable, and over time, the team tends to be more restrictive, such as adding more content to the completion definition.

Basic Scrum Basics Series:

• Scrum origins in the basic series of scrum entry
• Scrum framework for the basic series of scrum entry
• Scrum roles for the basic series of scrum entry
• Scrum Conference for the basic series of scrum entry
• Scrum artifacts for the basic series of scrum entry
• Scrum requirements grooming for the basic series of scrum entry
• Scrum estimates for the basic series of Scrum basics (please expect)

Scrum artifacts for the basic series of scrum entry