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

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

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...

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 ...

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.

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 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.

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 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.

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 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.

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...

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.

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...

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...

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.

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. 

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.

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

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 ...

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.

Scrum im Selbststudium: Der Scrum Guide in 19 Artikeln erklärt - Teil 1:

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.

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 ...

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.

In this vlog, PST Joshua Partogi explains why Scrum is not an iterative mini-waterfall project management method.

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.

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...

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”

Success is measured by the value it provides to the end user rather than the delivery of a feature.

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!

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:

Erfahren Sie, was ChatGPT als typische Arbeitsbelastung für einen Scrum Master betrachtet.

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...

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)

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...

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...

Sentiment surveys at the Sprint Retrospective can be an early warning indicator that something is wrong.

Org Topologies™ is a mapping of recognizable organizational archetypes in product development. Understanding the archetypes will help you to navigate your agile transformation.

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...

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.

In this vlog, Professional Scrum Trainers, Andreanna Marshall, and Scott Adams discuss five common Scrum mistakes that will ruin your team's progress.

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...

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.

Do you have to go to the Daily Scrum every day? Do you need to stand up? Should the Scrum Master and/or Product Owner attend every one? Watch this video to find out!

La paradoja de Jevons, también conocida como la "paradoja del progreso", se refiere a la observación de que a medida que aumenta la eficiencia en el uso de un recurso, su consumo total puede aumentar en lugar de disminuir. Esta paradoja fue nombrada en honor al economista británico William Stanley J...

Read on and learn what ChatGPT considers to be a Scrum Master’s typical workload, excluding the removal of impediments.

Kleine Scrum-Missverständnisse wuchern schnell zu ernsthaften Erkrankungen aus. Möchtest du dies verhindern, solltest du frühzeitig und konsequent handeln. Natürlich ist nicht jede kleine Regelabweichung gleich besorgniserregend. Allerdings gibt es drei Erkrankungen, die Grund zur Sorge bereiten. Di...

Este artículo presenta la relación entre el marco de trabajo Scrum y la inteligencia artificial (IA) en el desarrollo de soluciones. La IA se ha convertido en una herramienta esencial para mejorar la calidad, la eficiencia y la velocidad de entrega, y los equipos de Scrum pueden aprovechar la IA par...

En este artículo, un Scrum Master trabaja en una startup de tecnología y se enfrenta al desafío de un equipo que se resiste a participar en la daily scrum. El equipo tiene varias razones para no querer participar, incluyendo la percepción de que es una pérdida de tiempo, que interrumpe su trabajo di...