Release Notes are not documentation. They are part of your product’s conversation with the world. In this blog, you will learn how to write effective Release Notes.

"Technical Debt" is a big topic in the Professional Scrum. This article addresses a specific new pain point: AI generates code fast (increasing Velocity), but creates massive maintenance debt. This warns Scrum Teams against false velocity.

Generative AI removes the natural constraint that expensive engineers imposed on software development. When building costs almost nothing, the question shifts from “can we build it?” to “should we build it?”

Using the AQAL model provides a sophisticated framework for Scrum Teams to diagnose why a team followed the rules of Scrum but still failed in the delivery.

AI has turned code ownership from a theoretical concern into a practical business risk. Developers assume they own AI generated software because they guided the process and shipped the product, but copyright law depends on human authorship, and much of that code may not qualify. This usually does no...

If you drive your car without a destination, you are NOWHERE at the end of the day. The Sprint Goal is the destination of your Sprint trip. You should learn how to effectively create it.

Scrum is everywhere, but too often it’s not delivering the results leaders expect. Join PSTs Robb Pieper and Jason Malmstadt of Responsive Advisors and Scrum.org as they unpack the most common reasons Scrum fails to deliver real value.

Self-managing teams with specialists and experts often fail quietly. The problem is not expertise. In this blog, PST Robb Pieper explains what actually breaks self-management and why most leaders miss it.

AI agents have long promised productivity gains, but until now, they demanded coding skills that most agile practitioners lack or are uncomfortable with. In this article, I share my first impressions on how Claude Cowork removes that barrier.

In my practice, I get the chance to talk to a lot of different individuals from many organizations. Here are some of the things that really stood out to me about 2025.

In vielen Unternehmen hängen die Werte und Prinzipien des Agilen Manifests (wenn überhaupt) irgendwo an der Wand – zwischen Vision-Statement und Kaffeeküche. Gelebt werden sie selten. Stattdessen wird Scrum eingeführt wie ein neues Prozesshandbuch: Meetings ersetzen Denken, Jira ersetzt Verantwortun...

Scrum talks about *adaptation*—but not the kind driven by opinions, pressure, or discomfort. True adaptation only happens after transparency and inspection. Without learning first, teams don’t adapt—they drift. This post challenges how Scrum Teams really use adaptation.

The Scrum Guide is short—but every word is packed with intent. In this series, we explore its language one post at a time, connecting each phrase to real-world professional Scrum practice. You’ll never look at “collective intelligence” or “relationships and interactions” the same way again.

What makes self-managing teams effective? And how are they also cost-effective? In this live Ask a Professional Scrum Trainer session, Professional Scrum Trainers Robb Pieper and Jason Malmstadt will leverage their experiences to tackle your toughest questions about the business impact of self-manag...

I am often asked whether a Developer can support more than one Scrum Team. The answer is yes, but it's not ideal. Being on multiple teams means attending two (or more!) Sprint Plannings, two Sprint Reviews, two Retrospectives, and two sets of refinements. Not to mention two Daily Scrums—every single...

In Scrum, *collectively* doesn’t mean everyone must master every skill. It means the team as a whole has the skills to deliver value. Discover why this matters, how to avoid the “Lego block” myth, and how to grow resilience by sharing and acquiring skills.

Scrum isn’t powered by lone heroes—it thrives when groups of people engage together. From teams to stakeholders to leaders, Scrum creates the structure for collaboration, transparency, and shared purpose. Which groups are you engaging—or leaving behind?

Scrum helps teams solve complex problems, but even skilled practitioners can fall into common pitfalls that hold them back. PST Robb Pieper shares how to spot these mistakes and fix them to restore collaboration and deliver real value.

Scrum isn’t about compliance—it’s about engagement. By giving teams purpose, mastery, and autonomy, Scrum taps into intrinsic motivation. When people are engaged, they care, contribute, and grow. Are your teams engaged—or just going through the motions?

Slack time is not wasted time. It is the breathing room that allows teams to step back, adapt, and grow. Not to mention the ability to deal with any emergencies that happen to come up.

In this episode of the Scrum.org Community Podcast, host Dave West is joined by Dr. Alan Brown—professor, executive advisor, and expert in AI and digital technologies—to explore how Agile teams can adapt and thrive in a rapidly evolving AI landscape. (44:58 minutes)

Redeveloping a software system that manages vast sets of data to provide the advantages of cloud-based automation is a big challenge, especially when the customers include some of the world’s largest energy companies. To efficiently manage this process, the System Development team at rhi relied on a...

Sometimes Scrum gets a bad rap. When I ask why an organization struggled with Scrum, I almost always hear something like “there was too much overhead.” But when I dig deeper, I usually find that the organization had imposed extra rules—rules that have nothing to do with Scrum. In other words, when S...

One of the key aspects of Scrum is that each Sprint should result in a Done, usable increment of product. But what happens if your team struggles to achieve this? Here are ten practical ideas that your team may consider adopting to help improve your ability to get to Done.

Digital.ai releases an annual 'State of Agile' report which I am eagerly anticipating. While I wait for the 18th report to be released, I want to take a moment to look at how we have talked about Agile has changed over time.

One practice from Kanban that I think is often overlooked is related to the flow of work. Work on the Scrum board should flow from left to right - but it shouldn't flow backwards.

Lean thinking is foundational to Scrum—but too often, teams overload themselves with wasteful rituals and bloated backlogs. This post explores how Scrum encourages clarity, simplicity, and focus on what truly matters.

If you’ve ever been a Developer on a Scrum Team, you’ve probably experienced this moment: you’ve completed all of the work you originally planned for the Sprint, and there are still a few days left. What now? It might seem like a good idea to just pull more work into the Sprint, but that sometimes c...

I tried the new ChatGPT Agent mode, a valuable new tool for those who cannot program?

48 posts in, and we’ve only scratched the surface. This post wraps up our deep dive into the first two sections of the Scrum Guide—revealing just how much meaning lives in every word. Read the highlights, reflect on your learning, and get ready for Scrum Theory.

Scrum.org has launched "Professional Scrum Fundamentals," a new self-paced course. This course offers a flexible learning option for those new to Professional Scrum or looking to strengthen their existing capabilities, and it includes a complimentary attempt at the PSM I certification test upon comp...

The Scrum Master’s purpose is to improve the adoption of Scrum. Sometimes that means facilitating Scrum events — when asked or when needed. So yes, that often puts me - as the Scrum Master - in the position of leading the Daily Scrum.

As a Scrum trainer, I get the chance to speak with people from many different industries—finance, healthcare, tech, education, government. Because of my unique position, I get a chance to notice trends in the industry. Here is what I am hearing a lot about lately.

This blog covers the two techniques - Slicing and Splitting. Are they same? Are they different? When to use which?

Transparency is a core pillar of Scrum—but what happens when the environment punishes openness? In this episode of the Scrum.org Community Podcast, Professional Scrum Trainer David Spinks joins host Dave West to explore the complexities of transparency in unhealthy organizational cultures. (29:13 Mi...

Continuous delivery is achievable for any software, regardless of complexity. Success depends on investment in automation, quality, and process improvement—not technical barriers.

In this ScrumPulse Webinar, PST Ben Day explores how to use GitHub Projects to implement Scrum in your software development process.

When a new Scrum Team first starts working together, they go through some common growing pains. Knowing what to expect for a new Scrum Team can help make things go a little smoother.

Product Discovery is not a phase; rather, Product Discovery is a continuous process to learn fast, test early, and de-risk product decisions. It helps teams avoid building the wrong thing by validating user needs and assumptions before investing in delivery.

Scrum Teams treat feedback and data as a neutral and objective input, not a tool to confirm biases. By basing their decisions on objective results rather than optimism or personal opinion, Scrum Teams ensure they are continuously learning and adapting based on what the data actually reveals, not wha...

This week we had a great Q&A on Forecasting and Release Planning. During the "Ask a PST" session, we answered many questions. We got so many questions, that we could not answer all of them. This blog post tries to remedy that and answers most of these from my (Dominik Maximini) perspective.

In this Ask a PST episode of the Scrum.org Community Podcast, guest host Lindsay Velecina is joined by Professional Scrum Trainer Dominik Maximini to answer listener questions about forecasting and release planning.

Is the outcome of your meeting to schedule another meeting? In this short video, I identify three deeper challenges behind this frustrating dynamic and walk you through how to shift the pattern, starting with what’s in your control.

How often do you have to escalate? In this short video, I identify three common causes behind this frustrating dynamic and walk you through how to shift the pattern, starting with what’s in your control.

A fast-growing food industry company transformed its approach to product development and collaboration by adopting Professional Scrum—across both software and culinary teams.

Scrum Events nerven Entwickler? In diesem Artikel erklärt PST Simon Flossmann, was Scrum Master dagegen unternehmen können.

Most teams plan a Sprint with one question in mind: "What can we deliver this Sprint?" But here's a different take. What if, within every Sprint, we planned across all three horizons of innovation?

Scrum isn’t a finished product—it’s a starting point. What completes it? The collective intelligence of your team. This post explores what that really means, what gets in the way, and how you can unlock it in your day-to-day Scrum practice.

In this episode of the Scrum.org Community Podcast, host Dave West and Brendan Mcsheffrey, Managing Partner at Kendall AI explore the Kendall Framework—a method for training AI using principles from lean, agile, and design thinking. (33:42 Minutes)

Sprint capacity planning is one of the most often used complementary practices by Scrum Teams. This article from PST Dr. Pawel Rola provides all the basic information and practical examples to help you plan your next Sprint capacity.