Quantcast
Channel: Agile – Agile Pain Relief
Browsing latest articles
Browse All 100 View Live

Scrum by Example: Product Backlog Refinement in Action

In Scrum, Product Backlog Refinement is an essential meeting of the Product Owner and the Development Team to gain clarity and a shared understanding of what needs to be done through discussion and...

View Article


Scrum by Example – The Story of an Incomplete Sprint

A Scrum Sprint is incomplete when the Team can’t deliver the working features they committed to. We cover the reasons for this and how you can help your Team. Dramatis Personae Steve – a ScrumMaster...

View Article


Scrum Anti-Patterns: The Hardening Sprint

Hardening Sprints are one of the most common kinds of Scrum Anti-Patterns: ways of addressing recurring problems that seem like effective solutions at the time but in fact hamper productivity or create...

View Article

Scrum by Example – How to Handle Production Support Issues in Scrum

Whenever you are building and deploying a complex system, there are always going to be bugs, defects, and unforeseen problems with usability — commonly referred to as Production Support issues. Today,...

View Article

Scrum by Example – Team Friction Inspires Working Agreements

Working Agreements are a simple, powerful way of creating explicit guidelines for what kind of work culture you want for your Team. They are a reminder for everyone about how they can commit to...

View Article


Scrum Anti-Patterns: Micromanagement

A design pattern is a description of a solution to a recurring problem. It outlines the elements that are necessary to solve the challenge without prompting the reader to address the issue in a...

View Article

Scrum Anti-Patterns – How We Hold Back Our Scrum Teams

In software development work, a design pattern is a description of a solution to a recurring problem. It outlines the elements that are necessary to solve the problem, including context and the...

View Article

Choosing a Scrum Sprint Length – Shorter Beats Longer

How long should a Scrum Sprint be? A Scrum Sprint is a short period of time when the Scrum Team works, but there is no hard rule as to how long that should be – in this post, we cover the pros and cons...

View Article


Definition of Done vs. User Stories vs. Acceptance Criteria

One of the more frequently asked questions in my Scrum workshops is around the difference between Definition of “Done” and Acceptance Criteria, and how they relate to User Stories. While Acceptance...

View Article


What is the Recommended Scrum Team Size?

Nearly every client I work with asks me this question at some point. The Scrum Guide offers very limited guidance, suggesting 3-9 people per team (exclusive of ScrumMaster and Product Owner), without...

View Article
Browsing latest articles
Browse All 100 View Live