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.

Despite 25 years of the Agile Manifesto, countless books, conferences, and armies of consultants, we’re still collectively struggling to make Agile work.

One of the biggest mistakes I’ve seen in Agile adoption is the separation of design and development into different teams, each with their own Product Owner and their own Product Backlog.

Agile teams face ethical challenges. However, there is a lightweight framework that integrates with existing practices, protecting sensitive data and human expertise while enabling teams to confidently realize AI benefits without creating separate bureaucratic processes.

Case Study on Breaking the Tech Barrier: Implementing Scrum in Both Technical and Non-Technical Teams to Drive Measurable Business Outcomes.

Scrum isn’t about ticking boxes or increasing velocity—it’s about achieving meaningful goals. This post unpacks how goal clarity fuels effective Scrum and what happens when teams forget that purpose comes first.

Stop treating AI as a team member to “onboard.” It’s a tool.

People tend to highlight that Scrum is best suited as training wheels. However, what most people forget is Scrum is a means to an end; it's not a silver bullet. It is only as good as the members of the Scrum Team. If your team is not getting the desired results with Scrum, then it probably is not Sc...

Softwarearchitektur ist mehr als nur die Auswahl von Technologien und Patterns – sie ist das Rückgrat, das sicherstellt, dass ein Produkt langfristig erfolgreich ist. Doch wie funktioniert Softwarearchitektur in einem agilen Kontext, in dem immer wieder auf neue Anforderungen eingegangen werden muss...

New Scrum Teams aren't perfect, but when you use Scrum to get better, you get better at Scrum. So often, when you first start using Scrum, it can feel like you're just going through the motions. And while that can be frustrating, it's also a part of learning.

Scrum is a powerful framework for reducing risk, but only when its key mechanisms are fully understood and implemented. In this video, PST Robert Pieper outlines how Scrum helps teams manage uncertainty, reduce waste, and deliver value predictably through its built-in feedback loops and structure.

Points are not for measuring individual performance. Points are for forecasting future delivery. We don't need to fake the data to make developers look better, because that's not what points are for.

Unlock effective Scrum! Learn the distinct roles of accountability, responsibility & authority. Discover why empowering Product Owners, Developers and Scrum Masters with real decision-making authority is fundamental to self-management & value delivery. While often used interchangeably, accountabilit...

In this Scrum Pulse webinar, PST Simon Reindl explores how Scrum Masters, Product Owners and Developers can grow when working with many teams, and how they can manage scaling challenges.

Many teams struggle with Scrum—not because it doesn’t work, but because they modify it too soon. Before tweaking the framework, ask yourself: Have you truly tried Scrum as designed? Discover why ‘trying it as is’ matters and challenge your team to commit to five full Sprints before making changes.

Should all of the tasks be assigned in sprint planning and by whom?

Learn why succeeding with vibe coding requires a balanced approach: use it for rapid prototyping while maintaining rigorous standards for production code, with developers evolving from code writers to architects and code auditors.

In diesem Artikel erklärt PST Simon Flossmann die 3 größten Refinement-Probleme

Many organisations continue to struggle to adopt Scrum successfully as a framework for delivering great products. This post discusses some of the topics that these organisations have struggled with. The irony is that the elements of Scrum that they challenge are the very elements that can help solve...

Scrum’s repetition isn’t about doing the same thing over and over—it’s about evolving with every cycle. Learn how the rhythm of Scrum drives continuous improvement, reduces complexity, and ensures teams deliver value Sprint after Sprint.

Erfahren Sie mehr darüber, wie Sie die Ausrichtung auf die Nutzwertkette etablieren und Ihr Product Operating Model erstellen können.

Can AI generate high-quality code that is extensible, maintainable, and scalable? This experiment was a simple test to first evaluate the quality of AI-generated code for a basic kata against technical excellence principles—assessing its structure, modularity, and maintainability. Next, AI was...

Myth # 39: Technical Debt is the Developer's Problem. They caused it, so they should fix it on their own time.

Every now and then some one talks about or highlights a practice which has nothing to do with Scrum. Yet, due to widespread usage of the practice, people think that the specific practice is part of Scrum and should be followed to do Scrum in the right way. Sometimes, the Scrum Masters for the lack o...

At Argus, the maintenance team in Edmonton faced a challenge: ensuring consistent, high-quality repairs while dealing with an unpredictable workload.

Rigid, long-term forecasts stifle agility and increase risk, but figuring out how to do shift to agile forecasting is challenging. We'll explore for core practices that enable agility through adaptable investment decisions: re-forecasting, decreasing precision, bracketing, and aligning forecasts wit...

Scrum isn’t about blindly following a plan—it’s about inspecting, learning, and adjusting. But not all changes are improvements. Discover how small, goal-oriented, data-driven tweaks can make the difference between continuous improvement and chaotic change.

In this webinar, PST Joanna Plaskonka explores why psychological safety is essential for Scrum success, delving into how it fosters trust, transparency, and innovation within teams.

An Increment in Scrum must be both useful and usable to deliver value. Explore the differences between these two key qualities, why they matter, and how your Scrum Team can ensure every Increment solves real problems and is ready to be leveraged by users.

Ser un desarrollador efectivo no consiste únicamente en escribir código. Las habilidades para resolver problemas de manera colaborativa y mejorar de manera continua son fundamentales.

In Scrum, a valuable Increment delivers meaningful outcomes to users, not just features. Explore how value is subjective, how to understand your users’ needs, and why releasing frequently is key to ensuring your Increment truly moves toward the Product Goal.

The Scrum framework is simple, with just enough - but not too much - structure to enable teams to collaborate around value delivery in complex environments. The problem is that a lot of teams add unnecessary complexity to the Scrum framework itself, which results in a lot of wasted effort. Here are ...

In this episode of the Scrum.org Community Podcast, Dave West sits down with Sander Dur and Ryan Brook, authors of Solving for Value: A Journey of Ambition and Stupidity. (32:22 Minutes)