linaro-project-management team mailing list archive

[Ricardo Salveti <ricardo.salveti@xxxxxxxxxx>]

On Fri, Aug 12, 2011 at 8:16 PM, Joey Stanford <joey@xxxxxxxxxx> wrote:
>> Do you have any ideas about what the process should be for workitems
>> that aren't complete by that monthly milestone?
>
> Would be the same as in the original Monthly presentation...
>
> If we abstract up to the BP level then a BP is either done or not
> done. If it's not done then there needs to be a review of why it
> wasn't done and a decision about what to do about it. That could mean
> carrying it an extra month, breaking it out into smaller pieces,
> discarding part of the work, or all of the above.
>
>> Does it make a difference to that process if those workitems are
>> required for acceptance of the blueprint?
>
> Good question. No it doesn't as far as our thoughts go because we've
> taken into account that these things happens and we beleive the TL
> (with input from others) will make the right decision for the
> business.  Also, with a window of only 4 weeks it's harder to really
> goof something up than with a window of 6 months.  We'll know about
> problems much faster with monthly releases but it will take a tad more
> up front planning to break everything apart and then assemble the
> upcoming month's schedule.

The way I'm handling this is that once the month is over, I go over
the WIs and check if the acceptance criteria matches what was done for
the blueprint. If some WIs are still to be done, but feature is
already covered, I just move the WIs for another blueprint, if it's
still relevant for the next month.

I believe the PM and TL should validate and see what to do on a case
by case, but from my experience the WIs that are not relevant for the
blueprint shouldn't be there in first place (most of the time it
should easily end up in a different blueprint).

Cheers,
-- 
Ricardo Salveti de Araujo