linaro-project-management team mailing list archive

[James Westby <james.westby@xxxxxxxxxx>]

On Wed, 17 Aug 2011 15:44:12 +0200, Alexander Sack <asac@xxxxxxxxxx> wrote:
> OK, to be honest, I wasn't exactly sure about what was proposed in kiko
> slides.
> 
> Please correct me:
> What I think we are discussing here is if and how we can make the milestone
> page useful to a TL/PM/engineering role to support their day by day
> tracking, planning and management of their team work/commitments - and all
> that broken down to work item level?

Yes, that's what I think. Most of the rest of the roadmap discussions
are focused on the interaction with the roadmap. This is more about the
engineering team seeing their work day to day, and is rather independent
of the roadmap process, as it's something that has been requested for
the past couple of months.

> The other discussion we could have is if we want to (rather) make milestone
> pages better at conveying "what is in a milestone release for a component or
> set of components and what is planned to be in the next release etc.". So
> basically tuning for different type of audience.
> 
> Personally I feel that those are kind of conflicting as adding the detail
> needed by TL/PM/engineering will make the page less useful for the other
> audience and vv.

Yes.

> So, which audience should the milestone page address?
> I am currently in the camp of saying:
> 
> ... make milestone pages more useful to "communicate what's in and what's
> planned for a milestone release"
> 
> ...make status.linaro.org a very nice specialized "team work" page that
> gives TLs/PMs/engineers exactly what they want and nothing more :).
> 
> Happy to hear what others think!

I agree. However, there are lots of things to do there, and we have to
decide whether to do the high-level roadmap progress stuff first, or the
engineering team day to day stuff first if we're going to develop this
ourselves.

If we do the high-level stuff first then we're looking at at least
another few months without the "team work" pages. If we do those first
then it makes delivering the high-level stuff prior to the Connect a
bigger risk.

Therefore I'd like to see if we can do this with no development, at
least as a stop-gap measure, so that we can have some of the
functionality, without increasing the risk on the roadmap work.

Thanks,

James