[samigo-team] Planning for SAMigo 2.10 on September 6: discuss commonalities in top 3 list items?

[Ward, Lynn E.]

Hi all,

Just a quick reminder that we have a our regular meeting today at
11am-noon PDT  / Noon MDT / 2-3 EDT / 18:00 UCT. Following up on Keli's
note below, I too the liberty of creating a child page under

https://confluence.sakaiproject.org/display/SAM/Top+3+Samigo+Priorities+%28
Short-+and+Long-Term%29

That clusters the data in the short-term priorities table by functional
area.  This makes it a little easier to see the common themes/requests.
The URL for the child page is:

https://confluence.sakaiproject.org/display/SAM/Top+3+Near-Term+Priorities+
by+Functional+Area

Looking forward to our call this afternoon.

Lynn


==========================

Lynn Ward, Principal Systems Analyst, Instructional Technology Systems and
Services
University Information Technology Services <http://uits.iu.edu/>
Indiana University-Purdue University Indianapolis
Information Technology and Communications Complex (IT 225D)
535 West Michigan Street, Indianapolis, IN 46202
Phone: 317-278-5713  E-mail: leward at iupui.edu






On 8/31/11 3:11 PM, "Keli Sato Amann" <kamann at stanford.edu> wrote:

Hello,
As code freeze nears for SAMigo 2.9, we are going to try to get ahead on
planning for SAMigo 2.10. We  suggested during our last SAMigo community
team meeting that our homework was to add needs directly to the 2.10
confluence page, however, it probably makes more sense to simply look
through the Top 3 page.

https://confluence.sakaiproject.org/display/SAM/Top+3+Samigo+Priorities+%28
Short-+and+Long-Term%29

Our next meeting is currently scheduled for Tuesday September 6  11am PDT
/ Noon MDT / 2-3 EDT / 18:00 UCT. I would suggest we talk through the
items that were mentioned by more than one school (see below), as these
will likely end up being our priorities. I encourage interested members of
the schools who added to the top three to attend; if you were unable to
but wanted to, please let us know and we will either try to choose a
better time or find a way to include your feedback asynchronously.

As a first stab, these are the commonalities I could find (not necessarily
listed in order of priority).

1) Stability (assume this means no lost data or discrepancy):  (indiana,
Longsight, Delaware)

2) Reduce user confusion in settings (UF, Stanford, Florida, Longsight(?))

3) Allow Retakes and customized settings: Includes gradebook work
(Indiana, Stanford, Florida, Rice)

4) Performance for viewing and downloading data in classes with 1000+
students: (Florida, UNISA, Rice (?))

5) Question pool: ability to edit question in random draw (Florida,
Indiana, Longsight(?))

6) Better Gradebook integration (Indiana only, but this is probably going
to have a wide impact)

 We will need to better understand what each school means (perhaps they
are not grouped as above) and perhaps we can do a first pass at what the
goals and specific tasks are, as well as acceptance criteria.
Prioritization may depend not just on the impact on users (and user
support) but on whether certain changes need to be made first--I'm not a
developer but maybe (4) has to precede (1). Or perhaps changes in settings
reduces conflicts that result in lost data.

See you Tuesday,

Keli Amann
User Experience Specialist
Academic Computing Services, Stanford University
_______________________________________________
samigo-team mailing list
samigo-team at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/samigo-team