Stacking is a facilitation technique which ensures that everyone’s voice is heard. The facilitator acknowledges each person who wants to contribute and establishes an order in which they will share. The result is that each person knows when their turn is and that they won’t be forgotten.
In this third part of our facilitation techniques series, we’re using questions for elaboration to encourage further conversation.
Read the full article…
In part two of our facilitation techniques series, we’ll practice mirroring: what it is and when to use it for effective facilitation.
Read the full article…
This morning I woke to the sad news that Steve Bockman passed away. Steve was a friend, co-worker, creator, problem solver, agilist, and one of my heroes. Steve worked at Agile Learning Labs from 2009 – 2012. In his Hawaiian shirts, his presence was always fun, friendly, and engaging.
Read the full article…
Looking for techniques for effective facilitation? In this first part of our facilitation techniques series, we’ll dive into paraphrasing: what it is and how to use it.
Read the full article…
Still hearing sprint planning being referred to as a two-part event? Ever been in a sprint planning where developers had to explain their plan of work to the product owner and scrum master?
What you may be dealing with are relics of sprint plannings past. To understand how sprint planning has changed, we’ll take a look at the evolution of the event throughout the years.
Read the full article…
Are looking to get an agile job, such as scrum master, product owner, or developer on a scrum team? I recommend using scrum to structure your job search. A job search is complex work, full of unknown unknowns. That’s exactly the sort of work that scrum is good for. Additionally, using scrum and related agile techniques to structure your job search will grow your agile knowledge and skills. Here are a few thoughts on how to use scrum to support your agile job search.
Read the full article…
Here’s an overview of one approach to doing strategic planning in a scaled-up scrum environment. We’ll use twelve weeks as our planning horizon, though the approach works fine for shorter periods as well. We’ll start by looking at how a single team could plan for such a time horizon on their own without considering the broader organizational context, and build up from there.
Read the full article…
Photo by Nick Wright
Now that we’ve examined the history of daily scrum, we can shed some light on common anti-patterns of the event. Many of these are relics from Scrum Guides past: like scrum, the Guide inspects and adapts for continuous improvement. In other words, if you’re still following practices from an older Scrum Guide, you may be doing your team a disservice.
Read the full article…
Photo by Zosia Korcz
Scrum is an ever-evolving framework. And the events within it evolve too. As a result, some artifacts from past iterations of the events will still linger. You might be wondering where they came from.
Read the full article…
