Have you attended (or participated) in this daily stand-up meeting?
Q. What did I do yesterday?
A. I worked on (pointing) this card yesterday.
Q. What am I doing today?
A. I'll continue working on this card today.
Q. What's in my way?
A. Nothing is in my way.
If this continues for an entire iteration the team looses credibility and trust with themselves and other stakeholders and teams. One technique my teams use to provide visibility to potential risks is a "Daily Tally" on every user story/defect card.
|5 Point User Story Card with Daily Tallies|
Black - Developers
Orange - Testers
Red & Highlighter - Back Flow
Every day we place a tally mark on the card. Developers and testers have unique color markers and we tally from the the left to the right of the card to represent a timeline. The colors tell us how long we've been working on a card and how the time has been split between the developers and testers.
We also add a red tally when a card is returned to the developers from the testers. A red tally indicates that we missed an acceptance test scenario or introduced a defect.
The team uses the information from the daily tally in two primary ways:
- Retrospective Item - A red tally mark shows when we have an opportunity to improve by reviewing the causes for the back flow and determine if we want to prevent it in the future.
- Pushing help - When the number of tally marks equal the card's point estimate it triggers the team to ask "How can we help?". This is not a failure of an individual or the team. It is a mechanism that makes the team aware to potential risks as early as possible.
We still use more traditional tracking methods, but we've found this technique effective for spotting trouble early and providing examples (with data) for retrospective meetings.