Re: Scribing the daily scrum
- --- In email@example.com, Ilja Preuss <it@...> wrote:
>wiki or on
> Jeffrey Faust wrote:
> > > 9. Ask everyone to write their own things down in, e.g., a
> > a card.get
> > We were previously using a scrum software tool. We couldn't even
> > people to update their estimates daily. I don't see thishappening.
> A software tool isn't a good idea, in my experience. Cards on a
> work much better (but even then, some people will need some time toget
> used to it - and probably some prodding...)about
> I've heard (or probably read somewhere, but don't remember where)
> a team that used a wall of cards with tasks that weren't allowed tobe
> bigger than a days work. The cards for the iteration weredistributed
> over three columns - to do, work in progress, and DONE.answering
> In the daily scrum, they made it a ritual that everyone, while
> the three questions, put his card(s) from work in progress to DONE -or
> explained why it wasn't finished, which typically meant that therewas
> some impediment for the SM to tackle - and put the card(s) that heThis is similar to what we are doing, except the cards just can't
> planned to tackle next from to do to work in progress.
> Perhaps you can get some inspiration from this idea...
> Cheers, Ilja
have a task longer than 20 hours.
We also added a column for "Blocked" so the issue stands out and gets
addressed. I don't write down anything during the meeting, but can
capture the blocking issues quickly afterwards by jotting down the
items in the blocked column.
Work spent and work remaining get updated daily by each team member
during the daily scrum, but this took a lot of coaching to finally
get the team doing it consistently. This also gets captured into a
tracking sheet after the daily scrum, so as not to distract the team
from communicating with each other.