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 consequences of certain actions, without prompting the reader to solve the problem a specific way, leaving them with the agency to write code […]
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 specific way. Unfortunately, we also regularly see recurring patterns of ineffective behaviour. These are called Anti-Patterns. The following is an exploration […]
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 respectful behaviour and communication. In this post we’ll help you understand why these agreements are useful, and how you can help […]
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, our ScrumMaster and their Team grapple with these issues, to help you understand how they affect a Scrum Team and what you can do […]
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 more problems later on. Here we introduce why they are used, why they are not an effective design pattern, and how you can […]
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 and the hero of our story Paula – the Product Owner of Steve’s Team Tonia – the Team’s Quality Assurance […]
