Update "Potential Component Roadmap" shared iteration task

[Erin Yu]

As you mentioned, it would be good to do the use-case matrices before  
we discuss and get the results from our user research feed into our  
decision making.

I think this would help us see at a quick glance what areas are  
important, used frequently, and/or problematic. It'll be our users'  
voice when we discuss our roadmap!
Also... I'm all for getting the most out of our hard work. :)


On 14-May-08, at 4:59 PM, Daphne Ogle wrote:

> Hi there,
>
> I just wanted to make sure everyone knows what Fluid-575, that we  
> all have 2 hours assigned to this iteration, is all about.  I  
> entered this task to represent the time we all said we'd spend to do  
> some cross-referencing, double checking, adding community interest  
> and the such to the Roadmap matrix, http://wiki.fluidproject.org/x/8QEa 
> .  I believe we wanted to get back together to discuss once the  
> matrix is updated so that's the 2nd hour.
>
> Should a discussion be our next step (after people have had a chance  
> to review and update) or is their work we can/should still do the  
> visual matrix to help us see priorities, alignments, etc.?  , Also,  
> we should probably put a deadline on this task (particularly if we  
> also want to get another discussion in this iteration).  How about a  
> week from today, EOD Wednesday,  5/21?
>
> Daphne Ogle
> Senior Interaction Designer
> University of California, Berkeley
> Educational Technology Services
> daphne at media.berkeley.edu
> cell (510)847-0308
>
>
>