Tag: scrum ceremony
Case Study: Enhancing Team Work Using Dojo’s
The issue: knowledge sharing & alignment It is frequently seen that even though people are working on the same delivery there still is misalignment on the way of working, with what degree of finish (D.O.D. interpretations), etc. This especially happens with different skills and contexts that imply different perspectives on how to look at software. Either way you place it: knowledge sharing is lacking. One of the...
Surprise Surprise: Benefits of Cross-Functional Teams
Stage Backlog Refinement session. Purpose Our Product Owner came up with new stories to be estimated. 14 to be precise. It required some preparation however. We have 2 teams, and they do the Backlog Refinement together. Around 20 people in one room, partly offshore, estimating together is quite a challenge! Meeting Progress The meeting was slowly progressing and at the same time the activity was...
Splitting Backlog Items Part 3: How
In a sequence of blog posts based on our “Sharpen your story splitting skills” at XPDays 2015 to frame our useful deck of cards with splitting patterns, we bring you the last blogpost about how to split backlog items. Background Many times during our session we got questions like: "What’s the best pattern?" "Can you give us advice on how to split?" "When to apply which pattern?"...
Splitting Backlog Items Part 2: Who
After XPDays 2015 in our session “Sharpen your story splitting skills”, we concluded that some additional framing was needed for our useful deck of cards with splitting patterns. This article is the successor of the "Splitting Backlog Items Part 1: When" post, and will handle about the people and aims to help you understand dysfunctions that make item splitting a pain and the reasons for good practices. Background Quite frequently we see...
Why Sprint n-1 Analysis is a BAD idea…
(commonly known as the Scrummerfall anti-pattern) Consider the following familiar situation The team has taken a story in the sprint, and during the sprint, shit hits the fan. They rework, rework again several times to get it to done. Then the “we-could-have-avoided-this” feeling enters the minds of the team... In the Retro the conclusion is clear: We could have avoided this!! We had to analyse this better!...