I have been writing about story walls and how agile teams might use them to manage their work. But some agile teams feel rushed because, although they can see what needs doing today, they don’t know what is coming next.
So in this article, I will extend the idea of using a story wall to look into the future.
Continue reading “Notes on story walls – longer term planning”
In my last article, I talked about “story walls” but in fact, I focused on task walls. The difference is minor but choosing one over the other can help improve collaboration among the team.
Task walls, predictably, are about tasks – “today I will do task 1” while story walls focus on the thing being built – “today I am working on story 3.”
Most agile teams use story walls – either physical walls or online tools to store their stories.
But a lot of those teams see the wall as a burden rather than a tool that makes life easier for them. This is a shame because the only reason you want to have a wall is because it makes it quicker and easier for the team to get their work done.
From the perspective of the TEAM, the story wall makes their work visible so that they can more easily collaborate and get things done
Since different teams work differently, they are likely to want different types of story walls. This is the first in a series of articles that run through different types of walls that might be useful to different teams. There is no best practice – just things that suit different teams.
James King 