Patterns

Scrum is a timeboxed framework. We have sprints of fixed length (i.e. two weeks) and during the Sprint Planning event the team decides what will be completed during this time. If additional work comes up it would ideally be put into the product backlog and pulled into a future sprint once prioritized by the product owner, and given the team’s capacity for this work. However, it is not uncommon that we have requests which cannot be delayed until future sprints (i.e. 3rd level/production support). I will describe an approach on how these can be dealt with below. ...

With the world working remotely, I have managed to join a few meetup sessions which I would not normally have access to. A couple of days ago I was talking with James Coplien1, who along with the likes of Kent Beck, Ward Cunningham, Grady Booch, founded the the Hillside group2. Inspired by the architect Christopher Alexander3 work in pattern languages they have been running PLoP (Pattern Languages of Programming) writers workshops. With Jeff Sutherland4 and several other authors, Coplien has documented and collected patterns related to how Scrum teams organise and create value into a scrum book5. Most of these patterns are available online6. It includes all your favourites, from Sprint Goal and Daily Stand-up, to some more guild like patterns, i.e. Birds of a Feather (where similar roles, i.e. BAS or QAs, from different teams get together to share knowledge). ...