Skip to main content
Find resources



Resource search filters
Blog Post
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...
3 from 1 rating
Module
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...
4.5 from 189 ratings
Module
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...
4.7 from 224 ratings
Learning Series
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 empiricism to thrive.
Blog Post
Willkommen zum 3. Artikel der „Scrum im Selbststudium“-Artikelreihe. Solltest du den letzten Artikel verpasst haben, findest du ihn hier. 
0 from 0 ratings
Blog Post
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.
5 from 2 ratings
Blog Post
プロフェッショナル・スクラム・トレーナーから見て、なぜアジャイルは日本で広がらないのか?現状に関する考察、将来の展望、日本での浸透を進めるヒント
5 from 3 ratings
Blog Post
In this vlog, Professional Scrum Trainers, Andreanna Marshall and Scott Adams discuss the Risk Management strategy found in the Scrum framework.
3.8 from 2 ratings
Module
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.
4.8 from 11 ratings
Module
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...
4.9 from 18 ratings
Module
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.
4.6 from 16 ratings
Module
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 ...
4.5 from 22 ratings
Module
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.
4.9 from 10 ratings
Module
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.
4.4 from 13 ratings
Module
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.
5 from 15 ratings
Module
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...
4.5 from 13 ratings
Module
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.
4.9 from 17 ratings
Module
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.
4.8 from 15 ratings
Module
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...
4.8 from 15 ratings
Module
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.
4.8 from 25 ratings
Module
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...
4.7 from 15 ratings
Module
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. 
4.9 from 32 ratings
Blog Post
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.
0 from 0 ratings
Learning Series
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.
Blog Post
Willkommen zum 2. Artikel der „Scrum im Selbststudium“-Artikelreihe. Solltest du den letzten Artikel verpasst haben, findest du ihn hier. 
4.5 from 2 ratings
Blog Post
El Scrum Master brinda servicios de coaching, en ese sentido brinda orientación para ayudar a otros a alcanzar sus metas profesionales o personales. El coaching es una competencia para lograr usar un Scrum Profesional, al hablar del coaching (no del rol de un Agile Coach) conversamos acerca de cómo ...
5 from 1 rating
Blog Post
In this video, PST'S Gregory Crown, Jason Malmstadt and Robert Pieper are going to show you how an Agile Manager Helps Grow a Team. We'll get specific with a few ways you can help your team become better at self-management, improve team dynamics, and grow their product development skills.
0 from 0 ratings
Blog Post
Scrum im Selbststudium: Der Scrum Guide in 19 Artikeln erklärt - Teil 1:
5 from 3 ratings
Blog Post
Take your Daily Scrum from a reporting session to true teamwork and consider why answering the obsolete 3 Daily Scrum questions negatively impacts that ambition.
5 from 2 ratings
Blog Post
El Product Goal es un objetivo a largo plazo que establece la dirección general para el equipo Scrum y se enfoca en el valor que se entregará al cliente. Por otro lado, el Sprint Goal es un objetivo específico que se establece para cada Sprint en particular. Tener ambos objetivos en un equipo Scrum ...
0 from 0 ratings
Blog Post
Hoy me ha venido a la cabeza una idea de la que he estado conversando últimamente: ¿Se supone que los Producto Owners y los Scrum Masters deben estar en una lucha sin fin?. En el artículo verás la respuesta.
4.3 from 2 ratings
Blog Post
In this vlog, PST Joshua Partogi explains why Scrum is not an iterative mini-waterfall project management method.
3.8 from 6 ratings
Blog Post
What transparency can the Scrum Master bring to the Scrum Team and the stakeholders of your product? Transparency, being one of the core underlying concepts of the Scrum framework, we can expect the Scrum Master to actively work on this.
5 from 1 rating
Blog Post
la excelencia técnica en el desarrollo de software es un conjunto de prácticas y técnicas que permiten crear software de alta calidad, de manera rápida y eficiente, que cumpla con los requisitos del cliente y tenga una larga vida útil. Estas prácticas y técnicas, como las pruebas automatizadas, la i...
4 from 1 rating
Blog Post
A do-it-yourself workshop to have Scrum teams clearly express what they need from management, stakeholders, and the supporting organization with “What I Need From You”
0 from 0 ratings
Blog Post
Is a Sprint Review needed for every Sprint? Who should attend? What should we have ready for this Event? Watch this video to find out!
0 from 0 ratings
Blog Post
Success is measured by the value it provides to the end user rather than the delivery of a feature.
5 from 11 ratings
Blog Post
Scrum Teams, die Entwicklung und UX in einem Team vereinen, stehen unweigerlich vor der Frage: „Wie gehen wir mit den Resultaten von Experimenten im Sprint Review um?“ Wenn du auch vor dieser Frage stehst, dann lies weiter:
0 from 0 ratings
Blog Post
Erfahren Sie, was ChatGPT als typische Arbeitsbelastung für einen Scrum Master betrachtet.
0 from 0 ratings
Blog Post
This blog post discusses the Theory of Constraints and how it can be a valuable tool for improving business, organization, and personal performance. The author emphasizes the importance of identifying and focusing on the constraints that are limiting success in order to achieve more with less effort...
5 from 1 rating
Podcast
In this episode of the Agile Innovation Leaders podcast, Dave West joins host Ula Ojiako to chat about Scrum, Water-Scrum-Fall and importance of Kindness. (47:52 Minutes)
0 from 0 ratings
Blog Post
In the quest for short-term gains and rapid productivity, organizations are sacrificing their long-term agility and adaptability, just like the Titanic did. But fear not! We can learn from history and prevent ourselves from meeting the same fate. So, let's explore how companies can avoid becoming th...
5 from 2 ratings
Activity
Circle of Influence and Control ActivityHighly effective teams focus and are proactive on spending energy on the things that they can make a timely impact. By doing so, they not only enable themselves to change things for the better, they also create positive energy and widen their influence over th...
4.9 from 14 ratings
Blog Post
Sentiment surveys at the Sprint Retrospective can be an early warning indicator that something is wrong.
4.5 from 2 ratings
Blog Post
Org Topologies™ is a mapping of recognizable organizational archetypes in product development. Understanding the archetypes will help you to navigate your agile transformation.
5 from 2 ratings
Blog Post
Org Topologies™ is a map with recognizable organizational archetypes that you can use to discover, improve and communicate your agile transformation journey. The map will allow you to talk to Managers, Scrum Masters, Executives, Agile Coaches, and Product Owners using a common language to reflec...
5 from 1 rating
Blog Post
Understanding stakeholders is really important for Scrum Teams to be able to engage them in the right manner. I have found Stakeholder Persona Canvas as a lightweight tool that helps a lot in understanding them better.
5 from 4 ratings
Blog Post
In this vlog, Professional Scrum Trainers, Andreanna Marshall, and Scott Adams discuss five common Scrum mistakes that will ruin your team's progress.
4.6 from 4 ratings
Blog Post
A proper Agile organizational design is critical to achieving your business strategy, and you need to redesign your organization when your capabilities and strategy are incompatible. Redesigning your organization involves rethinking its structure, processes, and people to ensure that they align with...
5 from 2 ratings
Learning Series
There is no one direct path to become a great Scrum Master. However, we've assembled a few insights and ideas on topics such as driving toward goals, living the Scrum Values, enabling collaboration, removing obstacles, instilling self-management, promoting psychological safety, and encouraging a continuous improvement mindset.