Articles on Scrum By Example

Scrum wasn't intended to be waterfall done in iterations

Product Backlog Refinement - core to Scrum, yet so often we make it boring.

_Scrum team **Working Agreements** are a simple, powerful way of creating explicit

Boring, Repetitive Retrospectives, create disengagement and lead to inaction

Replace Show and Tell with Show and Play. Saving Boring Sprint Reviews one Step at a Time

Sprint Planning is the most underappreciated Agile event, leading to errors and misunderstandings

Building a real Product? Support issues are inevitable. What are some effective ways of handling them

More Work In Progress leads to less work finished

It is common in the early stages of Scrum implementation for there to be misunderstandings

Mid-Sprint, the Product Owner has discovered unplanned work - what is the harm?

What does it take to be a **great** ScrumMaster? When I was in my early years as a Scrum

The team doesn't understand that Daily Scrum is for them, not a management reporting tool.

Back at the dawn of time Sprint Burndowns were considered a useful tool. Now they Anti-Patterns

How many teams can a ScrumMaster coach effectively at one time

In the long run overtime always leads to poor quality and morale

User Stories are a collaborative journey of understanding, not a static requirement document

Technical debt should be tracked separately from user stories, not disguised as features for the Product Owner

Collaborating and using examples improves the quality and understanding of the Acceptance Criteria

Without clear acceptance criteria, the team couldn't agree on size or what to commit to.

Large stories increase the risk that your team will deliver nothing at the end of the iteration.

Effective Estimation is less about how big the item is and more about a common understanding of the item

New Team members are disruptive, there can be learning and personal challenges. Good ScrumMasters coach both

Effective Teams learn to schedule learning time into their Sprints

Dealing with Technical Debt in Scrum, specificially Sprint Planning

Technical debt slows team velocity as code becomes harder to change safely

When all tasks of one kind flow through one team member, you will get a bottleneck

Good ScrumMsters, Make impediments visible without blame.

Interruptions are killing your team, what are you doing about it?