Willkommen zum 8. Artikel der „Scrum im Selbststudium“-Artikelreihe. Solltest du den letzten Artikel verpasst haben, findest du ihn hier. 

Why do you need to have a Sprint Retrospective? Who should attend? What's the point of it?

Anyone can act as a teacher, helping your colleagues obtain new knowledge or learn new skills. However, if you want to become a very effective teacher, it’s best if you learn a few of the principles of the teaching profession, the skills and traits of a teacher and when teaching can be helpful for a Scrum Team.

Successful Scrum Masters continuously find ways to improve their practice to have greater influence and impact on their teams and organizations. Scrum’s foundational concept, empiricism, which advances learning through experience and observation, can support this kind of growth. In this blog post, w...

Analyzing the Agile fluency model from the perspective of Org Topologies.

In this article, we will analyze the famous “Tribes and Squads” model (also known as a “Spotify model”) in terms of where it fits on the archetype map.

"At regular intervals, the team reflects on how to become more effective, then tunes and adjust its behavior accordingly." What does this mean and why is it important?

Willkommen zum 7. Artikel der „Scrum im Selbststudium“-Artikelreihe. Solltest du den letzten Artikel verpasst haben, findest du ihn hier. 

Scrum events create regularity and transparency and minimize the need for meetings not defined in Scrum. The events are the Daily Scrum, Sprint Planning, Sprint Review, Sprint Retrospective, and the Sprint. Often, Scrum events don’t go as planned. Good, lightweight facilitation can help the Scrum Te...

Could the first principles of “Agile” have been defined by “Zeno of Citium in Athens in the early 3rd century BCE?”

A dogmatic approach to Scrum tends to close down discussion and inhibit collaboration. If it’s in the Scrum framework described in the Scrum Guide, it’s there for a reason. But if it is not outlined in the framework, Scrum teams can innovate how to apply Scrum in their unique environment.

La facilitazione permette di guidare persone e team verso obiettivi concordati. Traduzione dell’articolo originale in inglese sul sito scrum.org.

Willkommen zum 6. Artikel der „Scrum im Selbststudium“-Artikelreihe. Solltest du den letzten Artikel verpasst haben, findest du ihn hier. 

Teams are more effective when they operate in environments that make it safe for members to take interpersonal risks. For example, to admit they don't know something, to offer feedback, to offer help, or to ask for help.

La regla de una organización sin silos es un concepto importante que debe considerarse y adoptarse en cualquier estructura organizativa. Al eliminar estos silos, permitimos que las personas trabajen juntos de manera más efectiva y eficiente al mismo tiempo que fomenta una cultura de transparencia ...

The Definition of 'Done' is probably the most misunderstood concept of the Scrum framework. In this article we will discuss:  What Is the Definition of 'Done'  How it can be used in Scrum Events

Do You build "It Right" and at the "Right Time"?

Discover the learning objectives in the PSFS course and explore some supporting learning resources.

3 Practices to Break out of Cruise Control and Drive Change

La facilitación permite crear un espacio colaborativo para ayudar a las personas a moverse hacia los objetivos de una manera que se hagan incluyendo la participación conciente, voluntaria y motivada, el compromiso del resultado como equipo y la creatividad de todos.

Teams are more effective when they operate in environments that encourage learning and experimentation. Yet organizations and teams vary in how they recognize the value of learning and continuous improvement.

Willkommen zum 5. Artikel der „Scrum im Selbststudium“-Artikelreihe. Solltest du den letzten Artikel verpasst haben, findest du ihn hier. 

There is a lot of information out there about how to prepare for a Scrum Master interview. But, how do you land that interview? What are the qualities, mindset and personality traits needed to be a Scrum Master? Learn more in this episode of the Scrum.org Community podcast. (34:36 Minutes)

This is a recording of a facilitation focused presentation by Patricia Kong, Product Owner of Enterprise Agility at Scrum.org at Beyond Agile Israel 2023. (30:42 Minutes)

Willkommen zum 4. Artikel der „Scrum im Selbststudium“-Artikelreihe. Solltest du den letzten Artikel verpasst haben, findest du ihn hier. 

Lassen Sie uns darüber nachdenken, warum die Beantwortung dieser veralteten Daily Scrum Fragen einen negativen Einfluss auf das Scrum-Team hat — Making Your Scrum Work (29).

Systems Thinking is one of the key concepts required for successful agile organization design. It provides a valuable approach to organization design that can help organizations better understand the interrelationships between different elements within the system. By recognizing feedback loops and b...

Complexity science is a discipline unto itself and it’s worthwhile to study it in order to gain a deep understanding of how to make sense of a very complex world. However, for our purposes we can think of complex problems as those with many “unknown unknowns.” That is, there are aspects of the pr...

We can think of simple, complicated and complex problems as a continuum going from simple (where most things are known) to complicated (where we know what we don't know) to complex (where we don't know what we don't know) Simple Problems Simple problems a...

In Scrum, empiricism refers to the idea that solving complex problems, or doing complex work, can only be done using an exploratory process rather than relying on predetermined plans. Learn about empiricism and complex work. Explore why trust is important for empiri

Willkommen zum 3. Artikel der „Scrum im Selbststudium“-Artikelreihe. Solltest du den letzten Artikel verpasst haben, findest du ihn hier. 

プロフェッショナル・スクラム・トレーナーから見て、なぜアジャイルは日本で広がらないのか？現状に関する考察、将来の展望、日本での浸透を進めるヒント

Gregory Fontaine is a Professional Scrum Trainer living in Japan. He discusses the current state of Scrum and Agile Development in Japan and shares his thoughts on what we could do next.

In this vlog, Professional Scrum Trainers, Andreanna Marshall and Scott Adams discuss the Risk Management strategy found in the Scrum framework.

The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal.

During the Sprint Retrospective the Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done.

The Sprint Goal is the single objective for the Sprint. Although the Sprint Goal is a commitment by the Developers, it provides flexibility in terms of the exact work needed to achieve it. The Sprint Goal also creates cohesiveness and focus, encouraging the Scrum Team to work together rather than on...

Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint. This resulting plan is created by the collaborative work of the entire Scrum Team.

The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team.

An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, the Increment must be usable.

The Daily Scrum is a 15-minute event for the Developers of the Scrum Team. To reduce complexity, it is held at the same time and place every working day of the Sprint. If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers.

The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is the long-term objective for the Scrum Team.

The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed and what standards were met as part of the Increment. If a Product Backlog Item does not meet the Definition of Done, it cannot be released yet. Think of the Definition of Done as the ...

During the Sprint Review, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Backlog may also be adjusted to meet new opportunities. The Sprint Review i...

Sprints are fixed length periods of work that last one month or less to create consistency and ensure short iterations for feedback in order to inspect and adapt both how work is done and what is being worked on. If cycles are longer, then the spirit of frequent feedback cycles can be lost. Longer S...

The Scrum Master is accountable for establishing Scrum. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization while serving the Scrum Team as well as the larger organization. 

As a member of the Scrum Team, the Product Owner provides clarity to the team about a product’s vision and goal. All work is derived and prioritized based on the Product Goal in order to deliver value to all stakeholders including those within their organization and all users both inside and out. Pr...

It is important to remember that a Developer is not necessarily a software developer. They can focus on any type of product work whether software or not and any aspect of helping to design, build, test or ship the product. The specific skills needed by the Developers are often broad and will vary ba...

How do the Product Owner and the Scrum Team navigate unexpected customer requests? What happens when a high priority customer issue is discovered mid-Sprint? Should the Scrum Team ignore the emergency or interrupt the Sprint? Like so many things in Scrum, the answer is that it depends.

If you are just getting started, think of Scrum as a way to get work done as a team in small pieces at a time, with experimentation and feedback loops along the way. This learning series explores the pieces that make up the Scrum Framework.