linaro-project-management team mailing list archive
-
linaro-project-management team
-
Mailing list archive
-
Message #00300
Re: Can we implement kiko's proposed roadmap flow by the next Connect? (was Re: Updated Roadmap to BP slide deck)
On Fri, Aug 12, 2011 at 4:05 PM, James Westby <james.westby@xxxxxxxxxx> wrote:
> On Fri, 12 Aug 2011 10:57:31 +0200, Alexander Sack <asac@xxxxxxxxxx> wrote:
>> When discussing the monthly model, I got feedback from techleads and
>> PMs that they would like to keep a single page that tracks all the
>> blueprints and work items for the upcoming milestones of all
>> components the team participates in.
>>
>> This seems to be not included in current slidedeck/plan. Here a
>> proposal that would give a team a single page to look at to track
>> their progress for all upcoming deliveries.
>>
>> Proposal for Team Page:
>> * current monthly milestone team page becomes a "upcoming milestones
>> for team" page
>
> Phrasing this as changes to a page, and then throwing away 90% of that
> page makes this pretty hard to understand.
>
> What you seem to be asking for is the following:
>
> * For each team there will be a page for the current month.
> * This will list "upcoming deliverables"
> * Lists the blueprint, the assignee and the completion based on
> workitems DONE.
> * For each it lists the date at which it needs to be delivered and
> the days left until that date.
> * It also lists the component that is being delivered to.
> - How do we map from blueprint to component?
> * This page also lists workitems that are targeted to any milestone in
> the month. This is sorted by target date, and then by importance. It
> shows the assignee and the status as well as the description and a
> link to the blueprint.
>
thats about right.
>
> Given that I've estimated work so far to take up the time until the
> Connect, and this isn't required for Connect planning, just useful for
> execution afterwards, I'm not going to promise this before the Connect.
This was brought up by TLs/PMs as a _current_ problem after they moved
to the new monthly releases. I checked with amit and he found a
partial workaround that serves him good enough until connect. So ack;
not for sprint 1, but let's keep this and joey's performance
requirement near the top of the backlog.
--
- Alexander
Follow ups
References