If technical debt is the plague of our industry, why isn’t the Scrum Guide addressing the question of who is responsibly dealing with it?

I was working with various groups over the last year and noticed some commonalities in the problems they faced. In this blog I want to share some common collaboration problems and solutions I experimented with.

This is the start of a series of articles about the Scrum.org PSM II class. It will address the most common questions asked. This article is focused on the difference between the PSM and PSM II class.

Hearing a senior executive announce "We're committed to becoming agile!" is not the bombshell moment it used to be. It no longer indicates a personal revelation or board-room epiphany.

The Scrum Guide is markedly ambitious in the standard of professionalism it demands of a team. Development Team members must be self-organizing and cross-functional, to the point that they will repeatedly and sustainably create a valuable product increment...

Scrum stands on the three legs of transparency, inspection, and adaptation. Of these, transparency can arguably be said to come first. Unless a situation is made clear it cannot be inspected, and any consequent adaptation arising therefrom is likely to prove futile.

Scrum prescribes one person in the role of Product Owner (PO). Not multiple people, not a committee, just one person.

A couple of weeks ago we looked at Monte Carlo analysis. We saw how this technique can be used to forecast Sprint capacity, and to anticipate the likely completion schedule for a given backlog of work.

In this Scrum Tapas video, Professional Scrum Trainer Steve Porter looks at the impact that undone work has on technical debt and discusses some techniques to use when dealing with such issues.  Steve discusses value creation and what needs to be done to ensure value is a consideration in the proces...

In this post, we explain the Liberating Structure 'What, So What, Now What' and how we use this structure within the context of Scrum.

Agile coaching is a journey into irony. One of the chief discoveries you can make on this voyage is that the more experienced you become, the worse at the job others often think you get.

Big organizations use Scrum as a driver of agility. But often after launching, management start focusing on the speed of development instead of quality. DoD is often weak and the company's agility is reduced as a result. In this article we will use system diagrams to analyze the reasons why it happe...

In this Scrum Tapas video, Professional Scrum Trainer Todd Miller discusses the concept of Technical Debt and ideas on how to work to remove it. He looks at different concepts and why removal over time is important to the long-term viability of a product.

This is the third in a series of posts exploring Scrum Mastery. In our first post, we introduced the 4 dimensions of Scrum Mastery. In the second post, we explored how to grow a strong team identity. Now we will explore the team process dimension.

Behavior Driven Development (BDD) and Test Driven Development (TDD) are Agile Practices that are complementary to the Scrum framework. Both are focused on improving the quality of the software product under development. That said, they approach building valuable software from different perspectives.

The purpose of Scrum is to deliver Increments of releasable functionality. So at each Sprint Review, a “Done” Increment is required to make transparent the progress made by the team.

What we avoid is still being processed and affecting our thoughts, emotions, and behaviors.  Sometimes we are aware this is running in the background, and we catch ourselves thinking about it.  Then we try to distract ourselves.  Often we don’t even have awareness, and the effects still show up.

In this blog article, we provide a quick overview of the most viewed blog articles over the past 18 months, giving readers insight into what they mind valuable to read.

Leveraging Scrum as a Competitive Advantage: Product ownership is about more than mechanics: it’s about taking accountability and focusing on value in everything you do. In The Professional Product Owner, two leading experts in Scrum product ownership show how to identify, measure, and maximize valu...

As a Product Owner, there is nothing more frustrating than having to use valuable development time to deal with technical debt. Like death and taxes, it’s just never a good time when those lurking defects decide to unravel.

“Most executives, many scientists, and almost all business school graduates believe that if you analyze data, this will give you new ideas. Unfortunately, this belief is totally wrong. The mind can only see what it is prepared to see.” - Edward de Bono If you are ever hired as an agile coach,...

You’ve implemented Agile into your organization and hired professionals with Agile experience on their résumé to back it up. Yet, something is still not right. The gains that Agile promised don’t seem to be coming to fruition. Delivery times aren’t faster than they were before.

This document provides an overview of the changes made to the Nexus Guide over time.

There is a frustrating misunderstanding of reality when one thinks that the Product Owner can reject a single story at the Sprint Review. This is the fallacy of the rejected backlog item and the misguided belief that this backlog item can just be left out of this delivery. That backlog item that was...

"See it all. See it fairly. Be truthful, be sensible and be careful with language" - Henry Grunwald In Scrum we care about the precise and considered use of language, since any obfuscation reduces transparency. When we try to implement Scrum, we can sometimes find that the pressure is on to c...

Release Planning As a Product Owner, you are responsible for managing expectations of customers, users and other stakeholders. You are also responsible for Product Backlog Management, for deciding that to built when and what not to built. Also, you'll need to decide what to deliver (release) to cus...

Product Backlog Management As a Product Owner, you are responsible for Product Backlog Management, in order to maximize the value of the Product. The Product Backlog is the single source of truth which contains all the work to be done on the Product. As a Product Owner, you will have to make some c...

The Scrum Framework The Scrum Framework is a lightweight framework that defines three Roles, three Artifacts and five Events, which is used to develop and maintain complex Products in complex environments. Scrum doesn't prescribe a lot of things you must do, the Scrum Framework doesn't include exte...

As a Product Owner, you are responsible for stakeholder management. It's important that you know your stakeholders, their interests, what they need from you and your Product and how they may be able to help you out as well!

One of the most common critiques about Scrum that I've heard from smart software engineers are "Scrum does not care about technical practices, Scrum is for wimps". I've also heard managers down the hallway say that "Scrum is for wreckless developers because its main concern is only about fast delive...

Today I facilitated the workshop "The Scrum Master as a Manager" at the conference "Agile Spain 2017" in Sevilla. In this blog post I'll share the outline of the workshop "The Scrum Master as a Manager". This gives you the opportunity to facilitate the workshop within your own organisation as well.

As a travelling Scrum and DevOps consultant I’m constantly asked “should our team use Scrum”? Now you might think that being a Professional Scrum Trainer – and serious Scrum fanboy – I would always answer “Yes!”. Well, you would be wrong. I frequently talk people out of Scrum – for the right reasons...

When multiple Scrum Teams are working on one product, shared DoD becomes necessary. DoD helps to ensure that each increment is transparent by the end of every Sprint and creates a shared understanding of what “Done” means.

“The secret of success is to be ready when your opportunity comes” - Benjamin Disraeli A glance back at “Done” A few weeks ago we looked at the Definition of Done, which describes the conditions which must be satisfied before a team’s deliverables can be considered fit for release. Th...

I hear it all the time. Whether it is a consulting engagement or in a Professional Scrum Course, the desire to modify Scrum comes up frequently. 4 Questions to Ask 1. Where does the transparency hurt? Transparency usually brings pain, especially when you are early in your Scrum adoption....

This blog post will focus on how to get started and succeed with Zombie-Scrum. What do you really need to have in place? What are the tips & tricks to give your Zombie-Scrum implementation a kick-start? How to make it sustainable? This article will offer you some nice recommendations.

Recently I attended training on Nexus at Scrum.org’s Boston headquarters. Nexus is based on the core principles and values of Scrum and allows companies to apply Scrum at scale while retaining the bottom-up intelligence of self-organisation.

“Scrum begins with Done”. The assertion might seem counter-intuitive, as though we must start by defining the end.

“Do not accustom yourself to consider debt only as an inconvenience; you will find it a calamity” - Samuel Johnson A few weeks ago we looked at the problem of technical debt, and at the challenges a Development Team faces when managing it. Technical debt can be defined as the longer term cons...

It was only about 30 minutes into the meeting when the senior developer uttered the dreaded words: “Rewrite”. That was the point where what should have been a simple 6-step upgrade turned into a 9 month nightmare upgrade/rewrite costing us millions with nothing new to show for it and left us with a ...

"There are no shortcuts when it comes to getting out of debt" - Dave Ramsey Technical debt can be defined as the longer term consequences of poor design decisions. In a sense it’s like any other debt - there ought to be a clear understanding of why it is incurred, and how and when to pay it b...

As I get older, I'm turning into one of those annoying nostalgic-types who reminisces too much. Things were better back in the day, son. We had standards see, and there was less of this "dumbing-down". Yip.

"Gross ignorance is 144 times worse than ordinary ignorance" - Bennett Cerf Acceptance Criteria: The conditions under which a piece of work may be held to be complete and fit for potential release. Acceptance Test Driven Development (ATDD): A development approach in which acceptance crit...

This myth is my favorite. There are three challenges with this myth. First, it misses the point of Scrum. Second, it sets teams up for failure. Third, it's impossible to prove.

I was honored to participate in the Women in Agile panel discussion last week. If you missed it, you can watch the recording. I learned three things from this experience: 1) an hour goes by very fast, 2) I have a lot more to say on the topic, and 3) I want more opportunities to help women. We r...

One of the arguments used against Scrum and a common misconception at the same time is the idea that quality is traded for speed in Scrum. As a PST with years of experience in Quality Assurance I decided to challenge this myth. I believe and I have seen many times that proper way of implementing Scr...

In the Professional Scrum Product Owner course, we teach that high performing Product Owners are entrepreneurial. They not only act with the business in mind, they have the authority to make important decisions. What should we do now versus later? What choices give us the best return on investment? ...

Organizations who don’t understand why they want to become Agile also often take the wrong path to get there. Agility requires empowering teams and helping them make decisions on their own, learning from their experiences as they go. They must organize themselves, yet they often have Agile practices...

Glossary of Scrum Terms This glossary is meant to represent an overview of Scrum-related terms. Some of the mentioned terms are not mandatory in Scrum, but have been added because they are commonly used in Scrum. To learn more about the Scrum framework, to identify which of these terms are requir...

This glossary represents an overview of terms specific to software development teams using Scrum and agile software development techniques. To learn more about the Scrum framework, we highly recommend that you reference the Scrum Guide™ and the Scrum Glossary. A A/B Testing: extends the ide...