On 17 May 2011 15:12, Mounir Bsaibes <mounir.bsai...@linaro.org> wrote: > On Tue, May 17, 2011 at 8:40 AM, Peter Maydell <peter.mayd...@linaro.org> > wrote: >> [moving planning away from six-month cycles]
> Not sure how this can be accomplished without also spreading the 6 months > disruption to monthly disruptions. > It is better to have a longer term plan so the engineers would know what > to focus on for a good period of time. > In Agile lingo: > The long term plan or goals is called Product backlog. > The month to month plan (which a sub-set of the Product Backlog) is called > Sprint backlog. > As Linaro is adopting the month to month release, we may have to think of > Product backlog what we are delivering in the cycle Vs the Sprint Backlog > what we will be delivering month to month. Sure. As I understand the idea of an agile product backlog, though, you don't necessarily do full investigation and planning on every item in it (in the way that at the moment we do full down-to-the-work-item blueprints for everything at the start of the six months); instead you can just do broad back-of-envelope estimates and prioritisations and only need to do more detailed planning as things bubble up to the top of the backlog. -- PMM _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
