linaro-project-management team mailing list archive
-
linaro-project-management team
-
Mailing list archive
-
Message #00417
Re: First mockup of the roadmap views in status.linaro.org
On Tue, 30 Aug 2011 11:14:26 -0600, Joey Stanford <joey@xxxxxxxxxx> wrote:
> Hi James,
>
> Nice mock up :-)
Thanks.
> So far I agree with all the comments. I'd like to "me too" on the
> heath check bit. Maybe just an icon on the card display (green check
> mark or a red X)? Then when you click on the card you can get all the
> card details plus the health check in a checklist view. I want the
> health check to be binary: healthy or not healthy.
You are talking about the card display on the lane view, correct?
One concern I have with providing this information at the top level is
that if not done carefully it may taken to be meaning something
different to what is intended.
For instance, if we put green check marks on things, may people confuse
that with "delivered", or "on track", or "assigned", or "committed" or
something?
The mockup of the lane view currently shows one card with an exclamation
icon on it, in that case intended to convey that the card is "blocked."
Perhaps we could use that, and extend it to one of any problem,
including a failed health check.
That would mean that most cards (hopefully) wouldn't show anything, but
some cards would show a warning icon indicating that the card deserves
attention, and drilling down could uncover whether that's a blocked
workitem, missing acceptance criteria, no associated blueprints, etc.
Also, I'm not sure that we need to be providing health check information
in the lane view. Perhaps it's better to put it in a more PM/engineering
focused view? Is this something we want the TSC/Partner companies to pay
attention to? If not then perhaps we should decide if we should rather
have the information presented elsewhere.
> I'd like to see is a reordering of the sections on the mockup. I'd
> like them to read similar to this order which highlights current
> activities and blockers:
>
> 1. in progress
> 1. blocked
> 1. ready
> 1. planned
> 1. incomplete
> 1. deferred
> 1. done (with a little ajax firework display :-)
>
> We could probably make a case for moving incomplete under blocked but
> since incomplete only happens at quarter end, it's likely to be in
> planned or ready status for a long while and the current order would
> keep that showing. I want people to have to go through all the other
> stuff before they see what's done to force an awareness of all the
> other states before they taste victory.
I'm fine with this, I chose to put done first in the spirit of
emphasising to partner companies what we have delivered that they have
asked for, rather than emphasising the things that we haven't completed
yet.
I'm going to change the mockup to what you have requested. If someone
disagrees with you then we'll discuss at that point.
Thanks,
James
Follow ups
References