The other to do for the matrix is to link components to definitions.
Many of them have already been defined during the summit pain point
work so it's just a matter of linking to that page (child page of the
matrix) with anchors to the particular component I think. So if
anyone has spare time and knows how to do this in confluence, link on!
-Daphne
On May 22, 2008, at 6:16 PM, Allison Bloodworth wrote:
Hi all,
Today I added components from the Feedback and Layout problem spaces
(formerly there were just placeholders in the matrix for them). It
would be great if folks could read the matrix over and make sure
we've indicated the components are marked with the proper affected
projects (e.g. Sakai, uPortal) as well as whether some of them map
to the UX initiative or Pain Points that we might have missed. I
think some of the items at the bottom of the matrix may have been in
the Pain Points/Problem Spaces (http://wiki.fluidproject.org/pages/viewpage.action?pageId=1706283
) component suggestions, but didn't have time to double check them.
Cheers,
Allison
On May 15, 2008, at 2:01 PM, Daphne Ogle wrote:
On May 14, 2008, at 3:26 PM, Erin Yu wrote:
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.
Allison and I took a first stab at identifying components from the
affinity diagram use case work last week (marked in the Contextual
Inquiry column). We time boxed it and treated it somewhat as a
brainstorm so more eyes on it would be great. I'd suggest that
folks look at the pictures of the affinity diagrams, http://wiki.fluidproject.org/x/PYwk
, as a useful view on the use cases we captured. I displayed
thumbnails on page to preserve space. If you click on the
thumbnail you get a full view and can read the post-its.
Erin, were you thinking of an additional activity?
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. :)
Absolutely! The matrix captures our user research along with Fluid
work that went into identifying and organizing pain points
identified in Sakai, uPortal & Moodle.
As far as scheduling another discussion let's just check in next
week and decide if we need to talk as a group after everyone has
had some time to spend with the matrix.
-Daphne
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
[EMAIL PROTECTED]
cell (510)847-0308
Daphne Ogle
Senior Interaction Designer
University of California, Berkeley
Educational Technology Services
[EMAIL PROTECTED]
cell (510)847-0308
Allison Bloodworth
Senior User Interaction Designer
Educational Technology Services
University of California, Berkeley
(415) 377-8243
[EMAIL PROTECTED]
Daphne Ogle
Senior Interaction Designer
University of California, Berkeley
Educational Technology Services
[EMAIL PROTECTED]
cell (510)847-0308
_______________________________________________
fluid-work mailing list
[email protected]
http://fluidproject.org/mailman/listinfo/fluid-work
