Scrum artifacts or process documents provide guidance or links in the process framework.

4.1 Product Backlog

The Product Backlog is the core artifact of Scrum. In larger organizations management of the Product Backlog is unnecessarily complicated. What are the key messages, what are the rules for a Product Backlog, which also apply in scaled environments?

First of all, there is only one product backlog. For this there is a very clear statement in the Scrum Guide:  

The Product Backlog lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases. […,] Multiple Scrum Teams often work together on the same product. One Product Backlog is used to describe the upcoming work on the product. A Product Backlog attribute that groups items may then be employed.

Scrum events include the Sprint and the Scrum meetings. If we consider the definitions in the Scrum Guide as rules for the scaled implementation, all Scrum events apply both for the individual Scrum teams and for the whole product organization.

Prescribed events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum. All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process.

One of the most difficult decisions in the formation of an agile product organization is the team composition. Many elements of Scrum affect largely the process organization. The set-up and the constant increase in performance of Scrum Teams joggle the existing organizational structure.

The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master. Scrum Teams are self-organizing and cross-functional.

Let's look at this quotation in reverse order in detail.

This is the first blog post in a series of articles, where we interpret the Scrum Guide and try our best to create the Guidelines for the "rule-abiding" Scaling of Scrum.

The Scrum Guide defines Scrum as follows:

Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.