Estimation is a complementary practice Scrum Teams use in Product Development. The purpose of estimation is to provide a rough idea of how much effort, time, and budget are needed to complete specific features or PBI- Product Backlog Item of the product.

This is part 2 of a video in which I elaborated on a couple of words that are widely used in the Scrum world but are not part of Scrum. In this video, I will talk about Prioritization, Standup, Velocity, and Demo.

Si quieres saber las mejores estrategias para destruir Agile en tu organización, este post del PST Jerónimo Palacios describe las cinco mejores.

Successful teams deal with complexity by embracing it as an opportunity for growth. They prioritise based on customer value, inspect and adapt continuously to overcome challenges in product development.

Explore how transitioning from a Project Manager to a Scrum Master redefines success through a relentless focus on value over outputs.

Before changing their way of working, organizations should know first what business outcomes they want to achieve - which will be unique to each organization. Discover why focusing on Agile practices alone could lead you astray from the ultimate goal: achieving tangible and strategic business success.

In this video, Martin delves into the essence of Agile, moving beyond rituals to a philosophy of innovative product development 🚀. From Daily Scrums to sprint reviews, he explores how these practices, while important, are not the core of Agile's philosophy. 🤔💡

In diesem Artikel stellt PST Simon Flossmann 4 Ideen aus Kanban vor, die Scrum Teams helfen effizienter zu arbeiten.

A Tool for Creating Real Change with Michael Lloyd at the 58. Hands-on Agile Meetup

Listen to the Kanban Guide for Scrum Teams in full - Narrated by one of its co-authors (Yuval Yeret - aka me)

Después de casi dos décadas desde el inicio del movimiento, ¿agile sigue siendo la clave para abordar los desafíos que enfrentan las organizaciones hoy en día? Esto es lo que Guillem Hernandez Sola discute en su artículo siguiente.

A cross-functional team is a fundamental part of effectivity. How does this relate to the Daily Scrum? Check it out! - Back to the foundations of the Scrum framework (57)

Have your clients internally or externally asked how we can know our Scrum Teams are effective? Here are some ways I have helped my clients to communicate this to their managers.

Scrum.orgのプロフェッショナルスクラムトレーナー（Professional Scrum Trainer・PST）をしております、グレゴリー・フォンテーヌと申します。スクラムチームは自己管理型組織です。つまり、多くの決定を自分たちで行います。対照的に、従来型のチームでは、ほとんどの意思決定は特定の人（通常、マネージャー、アーキテクトなど）によって行われます。自己管理型組織の利点は多くあります。しかし、意思決定のスピードはどうでしょうか？私は以前、意思決定のスピードも自己管理型チームが従来のマネージャー主導のチームよりも優れている点だと考えていました。しかし、チームと仕事をすればするほど、相反する例を見つけることが多くなります。特に、コンセンサス主導の意思決定を重視する日本の文化は諸刃の剣となり得ます。両方の長所を生かすためにスクラムチームは協調性を維持しながらも時間効率の良い意思決定をサポートする手法の習得と実践に努めることが重要だと私は考えています。この記事でグラウディアは、私が自分のチームでよく使い、強力な効果があると思う手法の一部を紹介しています。

In this video, Martin discusses the relationship between agile transformation, cultural transformation, and the system within an organisation. 🤔

Assumir o papel de Scrum Master (SM) numa nova equipa e preparar-se para a primeira Sprint envolve desafios que não estão no Guia Scrum e nem nos livros. Este texto aborda tais desafios e apresenta estratégias para aumentar as chances de um início eficaz na sua jornada Agile.

No framework Scrum, o Product Goal surge como um elemento central, ainda que frequentemente subutilizado. Este conceito atua como um farol a guiar a equipa Scrum numa jornada onde o foco primordial é a entrega contínua de valor. Através de entregas regulares e iterativas do produto, o Product Goal estabelece um norte claro, direcionando todas as atividades da equipa. Este artigo visa explorar a importância e a aplicação do Product Goal, realçando como ele pode transformar positivamente o processo de desenvolvimento e a gestão do Product Backlog.

En este artículo del PST Jerónimo Palacios, explica como los Product Owners pueden utilizar inteligencia artificial generativa como ChatGPT para multiplicar su productividad.

In questo articolo, Fabio Panzavolta analizza i cinque livelli di feedback in Scrum, essenziali per ottenere una valutazione qualitativa del lavoro svolto durante lo Sprint. L'autore invita i team Scrum ad identificare il livello attuale di feedback e a lavorare per avanzare verso livelli più efficaci, enfatizzando l'importanza del coinvolgimento di utenti reali e dell'analisi di dati concreti per un'evoluzione empirica del prodotto.

There are good and great Product Owners. Sometimes, the distance from good to great is the hardest part of the journey. If you want your Product Owner to be more effective, show them this.

In diesem Artikel teilt PST Simon Flossmann 3 Kriterien, die Scrum Master beachten sollten, wenn sie die richtigen Probleme wollen:

In this video, Martin discusses the importance of continuously evaluating the direction of your project, product, or organisation. 🔍

Working agreements stand as the backbone of collective success. They provide a foundation for self-management and consensus on how to engage, which is crucial for navigating complexity.

The DoD and the acceptance criteria are two fundamental concepts in product development. While DoD is part of Scrum, Acceptance Criteria is an additional practice.

This post highlights the shift from traditional stakeholder engagement to continuous, collaborative involvement in Scrum.

En este post, el PST Alex Ballarin te explicará como la inteligencia artificial (#IA) puede ayudarte a crear mejores estrategias identificando a los usuarios y sus necesidades, las posibles funcionalidades, los indicadores holísticos del producto, así como también procesando los datos para sacar conclusiones (insights) accionables. Con esto crearemos estrategias más efectivas y centradas en los usuarios. ¿Te animas a explorar como? 👇

Each of the five events in Scrum is time boxed. This means that every Scrum event has a maximum (but not a minimum) amount of time the Scrum Team will spend on the event every Sprint. By limiting the time spent in each Event, the Scrum framework pushes Scrum teams to maximize the quality of their time together.

In this video, Martin discusses the importance of adaptation for businesses in today’s fast-paced and ever-changing market. 🌎

Four steps of proactive research to identify suitable employers or clients for getting hired as a Scrum Master and avoid disappointment later.

This article highlights the importance of stakeholder feedback during Sprint Reviews. It also delves into the transformative potential of incorporating Sprint Review Feedback Forms. It highlights how these forms serve as a vital tool for capturing comprehensive, structured, and actionable insights from stakeholders.

In diesem Artikel gibt PST Simon Flossmann Einblicke, wie er in Meetings und Workshops Konflikte frühzeitig entschärft und Differenzen überwindet.

En el dinámico mundo del desarrollo, la microgestión ha sido una constante preocupación. Esta semana, Guillem Hernandez Sola se sumerge en una reflexión provocativa: ¿Es Agile realmente una herramienta de microgestión?

In this video, Martin explores the nuanced philosophy of Scrum leadership. 🧭 He delves into how Scrum Masters can effectively lead without traditional authority, focusing on influence, respect, and skill to drive team success. 🚀

Descubre cuales son los mitos y falacias más comunes de Scrum en este post del PST Jerónimo Palacios

A cross-functional team is a fundamental part of effectivity. How does this relate to Sprint Planning? Check it out!

My thoughts on the recent ‘Agile is Death’ claims

Product Backlog refinement is the act of breaking down work. Further defining Product Backlog Items into smaller and more clear items can improve the Team's focus, flow of work, and the Product Backlog ordering.

In diesem Artikel gibt dir PST Simon Flossmann eine Anleitung, wie du dich für das Mögliche öffnest und dein Scrum Team auch durch unvorhersehbare Situation führen kannst.

Conway, Brooks, Hackman, Goodhart, Larman und Parkinson in der Praxis

In this video, Martin explores the nuanced decision-making process in product development, delving into when to pivot, persevere, or walk away. 🤔💼 He discusses the balance of factors influencing these decisions, from business needs to customer and team desires, and the challenges of avoiding the sunk cost fallacy. 🏦🔄

The Scrum.org Professional Scrum with User Experience I (PSU I) assessment is a 60-minute timeboxed assessment. You need to score over 85% to pass and gain the PSU I certification. The assessment contains 60 questions in English of multiple choice type.

The Scrum Master accountability is not fading. However, the Scrum Master role is evolving rapidly to be more capable and standing for true leadership in an ever-changing work environment.

Agile is not a mere indulgence; it is a more innovative and more efficient way to navigate the intricacies of delivering products and services, particularly when the products or services being developed require creativity and complex problem-solving to deliver them.

Acompáñanos a descrubrir en este viaje cuales son los motivos principales por el que las retrospectivas en Scrum fracasan

A Scrum Master can leverage data effectively to help the team by asking the right questions sooner and by using valuable insights to drive continuous improvement.

Foster a collaborative, cross-functional team environment. This post delves into how embracing Scrum’s values and practices enhances teamwork, driving innovative and efficient outcomes.

In this episode, Mike, Jeff and Pat predict 2024 trends in the Agile world.

What are the top things you should never do in Scrum? Do I have to just follow all the Scrum rules? Can I break some? In this Scrum Lightning Round, PST's Jason Malmstadt, Robb Pieper, and Greg Crown talk about what they feel are the most egregious offenses commonly done but should never be done when using Scrum.

En este post, el PST Alex Ballarín explica como la Inteligencia Artifical (IA) no es una amenaza para los Scrum Masters o Agile Coaches, sino una gran oportunidad para fortalecer los conocimientos y aplicarlos de manera más efectivas al contexto de los equipos. Esto va a ser una revolución: ¿quieres conocerla?

When picturing an effective and truly agile product development team, one often imagines a software development team, pushing some software to production every day, maybe multiple times a day, ala Amazon. By doing so, these teams gain the ability to test their assumptions early and often about the solutions they are building from both a technical and business perspective. But not all industries, business models or technologies allow for this to happen. What do you do then?