linaro-project-management team mailing list archive
-
linaro-project-management team
-
Mailing list archive
-
Message #00329
Re: Action: monthly WIs
On Tue, Aug 16, 2011 at 9:46 AM, Amit Kucheria <amit.kucheria@xxxxxxxxxx> wrote:
> On Tue, Aug 16, 2011 at 3:15 PM, Zach Pfeffer <zach.pfeffer@xxxxxxxxxx> wrote:
>> I've actually found that by executing each month that I end up with
>> less WIs that are more directed. If something doesn't get done and
>> there's been something tangible completed I split the BP. If nothings
>> really been done I either move the BP to the next month or put it into
>> the backlog.
>>
>> The other nice thing is that its easy to create Headlines and
>> Acceptance criteria on the smaller chunks of work.
>
> I'm willing to give it a try, but I am concerned about how anybody is
> going to figure out what work was done on a feature if it is
> splattered across 5-10 monthly blueprints?
I believe you can just link the engineering blueprints against a card
(that will end up as a blueprint). The card is your feature, the
monthly engineering blueprints is just a chunk of work that you can
easily trace and validate once it's done.
I know it sounds a lot of work, and launchpad brings the impression
that you'll end up wasting a lot of time on that, but once you do for
the first month, you'll see how easy is to follow this way.
Cheers,
--
Ricardo Salveti de Araujo
References