linaro-project-management team mailing list archive

[Joey Stanford <joey@xxxxxxxxxx>]

A way to visualize this in LP....

 * Pure backlog are BPs assigned to toolchain but are not targeted to
a milestone
 * your "todo" are those BPs which are targeted to a milestone but not
started (although you could assign them)
   * in-progress are those BPs that are assigned and status is set to
in-progress
   * done are those BPs that are set to done
   * blocked are those BPs that are set to blocked status
   * etc.

At the conclusion of a month you'll have a list of all BPs for the
milestone and their status. Anything that's not targeted is still your
backlog. Since BP's have a priority field, and the priority is taken
from the roadmap card, your backlog is in priority order.

At the end of a quarter there is a little bit of house keeping to
clear out the backlog and push that data back to the TSC "We didn't
get to these low priority items. What do you want to do?" as per the
TSC process. The TSC might say "move on" or they might retarget those
untouched BPs to the next quarter on the roadmap.

Joey

On Mon, Aug 15, 2011 at 5:59 PM, Michael Hope <michael.hope@xxxxxxxxxx> wrote:
> 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
>