Agile practices are designed to push authority toward the development team, not away.

Scrum stands as a rare and transformative management innovation in a field where technical progress has accelerated but management practices have stagnated.

Use Scrum only when transformative disruption is required. Or use ‘parts’ of Scrum if those parts prove to be better than previous ways-of-working.

People often reach out to me — they're trying to decide whether to take a Scrum course or a Kanban course.

This is a story about a former client. Early plans were to release a “Minimum Viable Experience” before year end. By late Spring, the Product Director described two “problems” and asked for my help: Release dates for the first publicly available version were slipping. And scope was expanding.

The role of the #ScrumMaster is often misunderstood. It's helpful to consider WHO were the early adopters? What was their interest in #Scrum? What did they bring to the role of Scrum Master?

A common question for newcomers to Scrum: What Do You Think About Story Points?

A common question for newcomers to Scrum: Can the Tasks of the Sprint Backlog Be Modified Mid-Sprint?

A common question for those new to the practice of #StoryPoints: Should we assign points to #bugs?

Scrum is an idea. The word ‘Scrum’ comes from the game of Rugby: a whole team working together; their singular mission is to move the ball down the field. The idea grows out of a few important truths about team development and product quality.

Kanban is a Japanese word that translates into English, roughly, as ‘sign’ or ‘sign board’. Let’s jump in…

In a conversation with a new Scrum Master, I shared advice for the first 90 days on the job.

A former student of mine asked me a question: I've just started working with a product development team whose members live in India Standard Time, Central European Time, and East Standard Time I'd like to help to configure our Sprints. Do you have advice about stand-ups? How often? Should we meet later in the day? Any advice would be appreciated.

A couple of months ago, I posted a prompt online. I said: “Hey, do you have questions about Scrum?” I got a tough question from Thomas, who asked: "Whilst everybody has to start somewhere, what do we do about "Masters" who don't know the basics?"

With David Sabine, PST. Video recorded in 2018.

I was recently asked, "Is Scrum dead? Or is it just "rebranded #waterfall"? Or will it be made obsolete by XP? Join me as I discuss these questions.

I was recently asked, "Do you think it's necessary to start every Sprint with each story fully specified?" The short answer: No, I don't. Join me as I discuss the topic.

Common complaint: “Scrum is not working in today‘s software engineering industry.” Response: If Scrum isn‘t “working” in today’s software engineering industry, then perhaps there are counter-signals in the industry that are preventing teams from employing Scrum effectively.

SDLC is an acronym that means either Software Delivery Life Cycle or Systems Development Life Cycle. And it is a lie. A fiction. A total fabrication. Somebody made it up out of thin air many years ago and the idea was cemented deep into corporate bureaucracy.

In this blog post, PST David Sabine shares a real life story focused around transparency.

Unclear language leads to incomplete transparency and ambiguity. The careful use of words like ‘bug’ will improve decision-making in your organization.

Velocity, as a metric used by some Scrum teams, is rife with trouble. David's concise article highlights a common pitfall.

A discussion is raging among Project Managers about the Iron Triangle because the authors of Scrum say “Scrum breaks the Iron Triangle”.