linaro-project-management team mailing list archive

[Michael Hope <michael.hope@xxxxxxxxxx>]

On Tue, Aug 16, 2011 at 3:47 AM, Joey Stanford <joey@xxxxxxxxxx> wrote:
> Hi Michael,
>
> Nice details.
>
> Might I suggest you consider
>
> 1) dropping "todo"? When you assign something it moves from backlog to
> in-progress.

Hmm, I was thinking that 'todo' is things they've signed up for this
month but haven't started.  This way I check half way through the
month and easily see if they'll meet the milestone.

> 2) only assigning items to people when they are free to work on them
> (this is a bit harder).  Pragmatically you have to assign (or target)
> a few items for each person each month so they know what to work on.

I'm happy for them to pick from the backlog as they come free, but
this conflicts with the strict monthly delivery model.  Having
blueprints that range for 1/2 month to two months and them
continuously picking seems more efficient...

> This would simplify your working model.
>
> An alternative approach is to split the backlog lane into two:
> unassigned and assigned.  Then you'd have backlog, in-progress, done,
> blocked, postponed.  In progress again would show only the stuff that
> folks are actively working on.

Yip, so 'backlog/assigned' is equivalent to my todo.

-- Michael