There is no such thing as pre-refinement. Instead, all work associated with adding order, size and detail to items in the Product Backlog is refinement, whether it takes place in a meeting or whether it's work done by an individual outside of a meeting.

Vague terms like "agility" and "value" lead to misunderstandings in product development. By breaking them down into measurable "supporting attributes," teams can create clearer goals and run experiments to achieve them. The three-step approach described here helps product development move beyond buzzwords and toward real progress.

In questo episodio Fabio Panzavolta analizza le origini di Scrum con il documento originale presentato da Ken Schwaber che ha introdotto Scrum al mondo, esplorando le origini del framework e come i suoi principi fondamentali sono rimasti rilevanti fino ad oggi. Scopriremo come Scrum è nato come risposta alla complessità dello sviluppo software e come ha influenzato l'Agile Manifesto.

Trust is an essential ingredient that fuels progress, innovation, and success. Building and maintaining trust requires conscious effort and commitment from everyone involved in the development.

In questo episodio Fabio Panzavolta risponde a due domande fondamentali dei nostri ascoltatori: la prima riguarda i possibili conflitti di interesse nei doppi ruoli in Scrum (Product Owner + Developer, Product Owner + Scrum Master), mentre la seconda esplora come attivare l'innovazione tecnologica in azienda attraverso il framework Scrum.

Framing work as problems to solve encourages individuals to think creatively and generate innovative solutions. Implementing solutions based on this problem-solving approach involves experimentation. Instead of relying on a single solution, teams test their ideas on a smaller scale, gather feedback, and refine their approach based on the results. This iterative process allows for continuous improvement and refinement of solutions.

Answer Leveling ist eine simple Technik um AI-Chatbots wie ChatGPT, Gemini oder Claude aus der Reserve zu locken und spannende, tiefergehende Antworten zu erzeugen. In diesem Blogpost erfährst Du, wie Scrum Master diese Technik nutzen können, auch ohne ausgereiftes Prompt-Engineering detailliertere und durchdachtere Antworten zu teambasierten Problemstellungen aus den LLMs zu gewinnen.

Learn more about addressing impediments imposed by leaders by redefining success, aligning incentives, fostering alignment, and balancing autonomy with standardization.

In diesem Artikel erzählt PST Simon Flossmann, wie er die Professional Scrum Master III mit 95 % bestanden hat.

Eat your own dog food - that is what we (tried to) apply in our first-ever journey of writing a book. It was challenging, sometimes frustrating, but very much rewarding!

In questo episodio Fabio Panzavolta esplora la differenza fondamentale tra performance e risultato in Scrum, analizzando come questi due elementi si relazionano nel contesto aziendale. Scopriremo perché è essenziale distinguerli e come uno Scrum Team può lavorare per migliorare entrambi gli aspetti.

Showing the value you offer to the organization is more critical than ever for Agile Coaches and Scrum Masters. It’s not easy, though. The three recommendations I provide in this blog post might help. If you’re interested, dig deeper into Evidence-Based Management, Kanban, and the scientific research behind Columinity.

In questo episodio, Fabio Panzavolta intervista Silvia Locati, sviluppatrice software e Scrum Master, che ci racconta la sua evoluzione personale attraverso Scrum ed il suo percorso di crescita professionale attraverso l'adozione di Scrum. Scopriremo come il framework ha trasformato non solo il suo team ma anche il suo approccio ai problemi complessi.

In questo episodio Fabio Panzavolta affronta una domanda frequente nel mondo Scrum: è possibile in una piccola realtà ricoprire contemporaneamente i ruoli di Developer e Scrum Master? Esploriamo vantaggi, sfide e considerazioni pratiche per gestire questa doppia accountability in modo efficace.

Scrum is built to solve complex problems—those with more unknowns than knowns. Discover why traditional planning falls short in uncertain environments and how Scrum helps teams experiment, adapt, and thrive.

In diesem Artikel schätzt PST Simon Flossmann die Gehaltschance für Scrum Master ein.

Schluss mit dem Erstellen von Funktionen, die Ihr Produkt nicht braucht. Optimieren Sie stattdessen die Entwicklung, vermeiden Sie eine schleichende Ausweitung des Projektumfangs und konzentrieren Sie sich auf das Wesentliche.

In questo episodio Fabio Panzavolta esplora le prime azioni fondamentali che uno Scrum Master dovrebbe intraprendere quando inizia a lavorare con un nuovo team in una nuova azienda. Scopriremo l'importanza dell'osservazione, della costruzione della fiducia e dell'approccio empirico al miglioramento continuo.

Starting with Scrum can feel overwhelming. It’s a framework with defined events, accountabilities, and artifacts that might seem rigid or even intimidating at first glance. But here’s the truth: it’s okay not to get everything perfect on day one. The real magic of Scrum unfolds as you practice and improve over time.

In questo episodio inauguriamo una nuova rubrica "A domanda risposta" dove Fabio Panzavolta risponde alle domande più frequenti che riceve durante le sessioni di coaching e formazione. Scopriremo come un team Scrum può prendere decisioni efficaci, mantenendo i valori Scrum e promuovendo la psychological safety.

Struggling with long and unfocused Daily Scrums? In the second part of this two-part series, PSTs Robert Pieper and Greg Crown share five more strategies to cut down on wasted time, improve focus, and ensure your Scrum Event stays efficient and productive.

The Product Vision outlines what you aim for, inspires and aligns the team toward a common direction, and provides a sense of purpose. It serves as a foundation for all product-related decisions.

In questo episodio Fabio Panzavolta esplora come superare il concetto di ritardo con Scrum per trasformarlo in un'opportunità di crescita quando Scrum viene applicato con competenza. Scopriremo come l'approccio empirico di Scrum permette di superare la visione tradizionale delle scadenze rigide, favorendo una gestione più efficace dei prodotti complessi.

Have you ever felt like your team spends more time battling over "resources" (a.k.a. people) than strategizing over what is the highest value work? You're not alone. Many organizations struggle with this chaos. Many Product Owners are fighting a constant battle over which work is "actually" the highest priority for the organization, juggling dependencies and scrambling for people to do the work.

Ser un Product Owner exitoso lleva a enfrentar muchos desafíos dentro de entornos de constante cambio. El uso de Scrum ayuda a reducir el riesgo al adoptar el empirismo.Los Product Owners tienen muchos desafíos al gestionar los productos de forma ágil. A continuación, se explican algunas ideas para mejorar sus capacidades.

Think 15-minute Daily Scrums are unrealistic? Think again! PSTs Robert Pieper and Greg Crown share five practical tips in this two-part series to streamline your team’s discussions, stay focused on the Sprint Goal, and minimize distractions.

Stop Building What You Do Not Need, Escape Scope Creep, and Focus on Creating Value!

In diesem Artikel stellt PST Simon Flossmann 5 Methoden zum besseren Product-Backlog-Management vor.

In questo episodio esploriamo una delle sfide più comuni nelle organizzazioni che adottano Scrum: cosa succede quando il Product Owner non ha vera ownership sul prodotto? Insieme al nostro ospite Michael Forni, Agile Coach con esperienza nel settore finanziario, analizziamo le cause, le conseguenze e le possibili soluzioni a questa situazione.

For a Scrum Team to gain autonomy, they must first show they are trustworthy. And how do you build that trust? By making your work visible. By embracing transparency, Scrum Teams can take greater control over their work and deliver even more value to their stakeholders and organizations.

In questo episodio Fabio Panzavolta esplora il fenomeno della "reazione autoimmune aziendale" verso Scrum, analizzando come le organizzazioni tradizionali spesso reagiscono all'introduzione di Scrum come se fosse una minaccia, invece di riconoscerlo come un elemento benefico per lo sviluppo di prodotti complessi.

In the final part of this series, PSTs Robert Pieper and Greg Crown share strategies for working with Scrum teams across time zones. covering co-located team benefits, reducing communication barriers, and practical solutions like rotating off-hours, fostering cultural understanding, and arranging meetups.

Scrum isn’t just about solving problems—it’s about solving them in ways that evolve with changing conditions. Explore how Scrum fosters adaptive solutions to tackle your team’s unique challenges and meet user needs.

In questo episodio, Fabio Panzavolta intervista Stefano Berretta, uno sviluppatore con oltre 20 anni di esperienza che ha guidato l'adozione di Scrum in una piccola software house. Scopriamo come il framework Scrum può essere implementato in realtà più piccole, i benefici ottenuti e le sfide ancora da affrontare.

In large organizations, a Scrum Master’s focus is often a team; the Agile Coach works with multiple teams and their environments, and the Enterprise Agile Coach works with the broader organization. Be mindful of the consequences. It can limit the ability to remove impediments and improve team- and organizational effectiveness.

In diesem Artikel erklärt PST Simon Flossmann, wie eine einzige Person der Product-Owner-Verantwortung gerecht werden kann.

Psychologischen, organisatorischen und strategischen Gründe warum Führungskräfte das Product Operating Model unterstützen, wenn "Agile" zuvor nicht erfolgreich war.

Words shape how we understand and apply Scrum. This post brings together all entries in the ‘Scrum Guide Explored’ series, diving into the key terms of the Scrum Guide and their professional meaning. Easily navigate through the series, organized by the guide’s structure, and gain deeper insights into how these words drive value, collaboration, and agility.

In questo episodio Fabio Panzavolta intervista Alessandro Bignami, un professionista con oltre 25 anni di esperienza nel mondo del software development, di cui gli ultimi 7 dedicati all'Agile e Scrum. Esploriamo come il mindset agile sia una caratteristica naturale che paradossalmente dimentichiamo con il tempo, e come riscoprirlo possa portare a risultati sorprendenti nei progetti software.

Motivation in professional teams goes far beyond traditional incentives like bonuses or perks. Drawing from software industry experience, I explore three fundamental aspects of motivation that can transform team engagement: product connection, technical craftsmanship, and team spirit. While rarely achieved together, even one of these elements can significantly change how teams approach their work.

In Part 2 of this 3-part series, PSTs Robert Pieper and Gregory Crown focus on the importance of building trust and streamlining tools for globally distributed teams. Learn how to limit tool sprawl, foster a culture of autonomy, and set effective overlap times to support your team’s productivity.

🎙️ In questo episodio speciale, Fabio Panzavolta intervista Emanuele Vecchio, sviluppatore software e appassionato di Scrum. Scopriamo il suo percorso di adozione di Scrum, i benefici ottenuti nel suo team e le sfide affrontate. Un'intervista ricca di spunti e riflessioni sul valore dell'empirismo e dell'approccio Scrum non solo nel lavoro ma anche nella vita.

If Product Owners fail to maximise the value produced by the team, the entire product development can be derailed. Failing to understand and validate value leads to the team missing the intended goals.

🎙️ In questo episodio, Fabio Panzavolta intervista Luca Giancristofaro, ingegnere dell'automazione con esperienza nello sviluppo hardware e firmware. Scopriremo il suo percorso di adozione di Scrum in un contesto di prodotti fisici, le sfide affrontate e i benefici ottenuti nel passaggio da un approccio waterfall a Scrum.

There’s a persistent myth out there that a Product Owner should only support one Scrum Team. The idea behind this is that having more than one team will stretch the Product Owner too thin, leading to burnout and unnecessary stress. But that’s actually a huge misconception!

Working across multiple time zones poses unique challenges for Scrum Teams. In this Part 1 of a 3-part series, learn strategies from PSTs Gregory Crown and Robert Pieper to ensure your global team stays connected and productive.

The Agile Product Operating Model (APOM) is a natural progression for your agile transformation. It provides an ‘in-between’ stage between the whole enterprise change and delivery team change with the idea of products. By aligning to products, you can incrementally change the organization, allowing each product group to adopt a different operating model. Of course, that comes with some challenges, including how products are funded, comfort in parts of the organization operating differently, and where authority and decision-making reside.

This article uncovers the psychological, organizational, and strategic reasons behind this seeming contradiction, exploring what motivates leaders to believe that a new approach will succeed where others have not.

In diesem Artikel gibt PST Simon Flossmann 3 Tipps, wie Product Owner besser ihre Meetings moderieren können.

🎙️ In questo episodio Fabio Panzavolta legge la Guida Scrum, il documento scritto da Ken Schwaber e Jeff Sutherland che definisce il framework Scrum. Scopriremo la teoria, i valori, gli eventi e gli artefatti che compongono Scrum, direttamente dalla fonte ufficiale tradotta in italiano.