linaro-project-management team mailing list archive

[Ilias Biris <ilias.biris@xxxxxxxxxx>]

Hey,

thanks for the feedback see below for some answers.

On 16/10/12 00:52, Jakub Pavelek wrote:
> Hi,
> 
> works well for me. However once I have visited one of those Structures I
> will see that particular structure in every Card I have, related or not to
> that structure. That is annoying a bit.
> 

You mean the area which appears in a card view showing structures? That
one is a quick browser of structures, with handles available to add the
current card into an existing structure. By default it shows the latest
structure you have seen. It comes by default collapsed - if you expand
to see the structure it should tell you if the card is in the structure
or not. Also you have a handle to select which structure to show in that
area - the structures which contain the card you are viewing are already
highlighted in the selection list. See the attached PDF screenshots I
took with this area collapsed and open - try it out on different cards.


> Now for a little off-topic. It got me thinking: we already have hierarchies
> of Blueprints - and those work well for me personally. Hierarchy of cards
> encourages small cards and small cards bring details I'm convinced TSC is
> not interested in. Should we say "Card is a high-level mission" and stop
> worrying too much about a card being the proper size for our 3 months
> iterations? Make Card a roadmap item where the expected delivery matters.
> 

If I understand what you ask correctly, it seems that if we do this then
planning with cards will effectively diminish to setting missions with
no clear delivery horizon. However, high level missions which may finish
any time from a few months to whenever are not very useful to set
expectations eg at the TSC level. Even though BPs are used by
engineering there are other stakeholders which need the plan
transparency at the roadmap level - that means cards.

So my question - how would this improve our planning, and estimates?
Using the cards and planning from Connect to Connect enables us to set a
cadence for synchronisation of our deliverables whilst keeping the
waiting times for the deliverables as predictable as we can (and we can
improve there).

Maybe we can discuss this - would you like to set a meeting at least
between PMs to cover this topic?

Cheers!

-- 
Ilias Biris ilias.biris@xxxxxxxxxx
Project Manager, Linaro
M: +358504839608, IRC: ibiris Skype: ilias_biris
Linaro.org│ Open source software for ARM SoCs

Attachment: Card-View-Structure-Dialog-Collapsed.pdf
Description: Adobe PDF document

Attachment: Card-View-Structure-Dialog-Open.pdf
Description: Adobe PDF document