linaro-project-management team mailing list archive
-
linaro-project-management team
-
Mailing list archive
-
Message #00364
Re: Upstream and planning
On Tue, Aug 23, 2011 at 7:53 AM, Joey Stanford <joey@xxxxxxxxxx> wrote:
> Howdy,
>
>>> A developer assigns the BP to themselves and retargets the BP out of
>>> the backlog milestone and into the current monthly milestone.
>>
>> Sorry, in what state do they do this? Does it stay in 'backlog' until
>> accepted upstream?
>
> BPs that are created each quarter by new Roadmap cards go into the backlog.
> At the end of the quarter we clean out the backlog to make room for
> the next quaters BPs.
Diversion: blueprints can be created at any time and are lodged into
the backlog. Blueprints may result from splitting cards as the result
of investigation.
>> How does someone else tell if a blueprint is free
>
> If a BP is in the backlog milestone then it by definition means that
> it's not being worked on. Ideally an engineer would go visit the
> backlog and grab the next highest priority item off it. However what I
> suspect will happen, and this is certainly very good as well, is that
> you as the TL may choose to assign a BP to an engineer in advance.
>
> Think of it like airplanes in a holding pattern over an airport. Once
> the tower is ready to do something with an airplane they move it out
> of the holding pattern and put it on approach. We're doing same
> things. BPs in the backlog are BPs in a holding pattern until
> resources free up to work on them.
>
>> How do I tell what is in progress and what is blocked
>> upstream?
>
> The monthly milestone view. You move a BP from the backlog milestone
> to your current monthly milestone. It will tell you want's done, in
> progress, and blocked for that month.
Yip, so that fits my original method.
So my question stands: we don't control upstream and can't assign a
blueprint to a monthly milestone as we don't have control over when it
will actually land. How should this be handled?
-- Michael
Follow ups
References