Working with distributed teams as a Scrum Master, Agile Coach or Facilitator can be difficult. There is no substitute for face to face communication, but sometimes this isn’t feasible. When the show must go on, there are some simple tips and tools to try which can help facilitate the session.
As we have progressed as a scrum team, our board has evolved in line with our continuous improvement ethos. Heavily influenced by the Theory Of Constraints, we introduced WIP limits on user stories and the board by restricting the number of lanes. We have seen team and productivity benefits when adopting some of these simple changes.
Retrospectives can be one of the most valuable sessions in Scrum and Agile teams. Often they can become boring and less useful to the team and they can fall into an administrative process with less value. This post is about sharing a recent retrospective session that was fun, engaging and got results using a Top Gear theme to explore, identify and resolve issues to benefit the team and ultimately the business.
Using cumulative flow diagrams to observe workflow within sprints can provide valuable, visual input for teams. Unlike the sprint burndown chats, CFD”s look at the lower level of tasks to see what goes on closer to the work getting done. Used with the burndown, a cumulative flow diagram can be a useful learning aid to support retrospectives, continuous improvement and feedback.