<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: UNC&#039;s Sakai Evaluation Results</title>
	<atom:link href="http://mfeldstein.com/uncs-sakai-evaluation-results/feed/" rel="self" type="application/rss+xml" />
	<link>http://mfeldstein.com/uncs-sakai-evaluation-results/</link>
	<description>What We Are Learning About Online Learning...Online</description>
	<lastBuildDate>Fri, 18 May 2012 06:39:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Bruce</title>
		<link>http://mfeldstein.com/uncs-sakai-evaluation-results/#comment-1587</link>
		<dc:creator>Bruce</dc:creator>
		<pubDate>Wed, 26 May 2010 19:58:37 +0000</pubDate>
		<guid isPermaLink="false">http://mfeldstein.com/?p=1166#comment-1587</guid>
		<description>Thanks Nate, Michael.

On the &quot;usability is in the eye of the beholder&quot; point, I came across a quite nice discussion of this over at the Moodle site ...

http://docs.moodle.org/en/Usability

... in particular the &quot;Avoid the word &quot;intuitive&quot;&quot; section.</description>
		<content:encoded><![CDATA[<p>Thanks Nate, Michael.</p>
<p>On the &#8220;usability is in the eye of the beholder&#8221; point, I came across a quite nice discussion of this over at the Moodle site &#8230;</p>
<p><a href="http://docs.moodle.org/en/Usability" rel="nofollow">http://docs.moodle.org/en/Usability</a></p>
<p>&#8230; in particular the &#8220;Avoid the word &#8220;intuitive&#8221;" section.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Feldstein</title>
		<link>http://mfeldstein.com/uncs-sakai-evaluation-results/#comment-1586</link>
		<dc:creator>Michael Feldstein</dc:creator>
		<pubDate>Wed, 26 May 2010 19:42:32 +0000</pubDate>
		<guid isPermaLink="false">http://mfeldstein.com/?p=1166#comment-1586</guid>
		<description>Nate is right; there&#039;s just been a lot of concerted effort on this over time.

I would add that the Sakai community does have an unusually rich talent pool of usability experts. Two of the Foundation Board members---past board member Mara Hancock from UC Berkeley and current board member Jutta Treveranus from University of Toronto---run usability teams at their respective schools and have brought resources in to help improve the system. Going forward, the Sakai 3 effort is *very* usability-focused.

Keep in mind, though, that usability means different things to different people. For faculty that are used to one platform, usability means anything that works like what they already know. But that&#039;s a poor measure. You want to know (a) how easy is it for new users to learn from scratch, and (b) once you know how to use it, how many clicks do you need to make for common tasks? How hard is it to make a major mistake (like delete your entire course, for example)? And so on.</description>
		<content:encoded><![CDATA[<p>Nate is right; there&#8217;s just been a lot of concerted effort on this over time.</p>
<p>I would add that the Sakai community does have an unusually rich talent pool of usability experts. Two of the Foundation Board members&#8212;past board member Mara Hancock from UC Berkeley and current board member Jutta Treveranus from University of Toronto&#8212;run usability teams at their respective schools and have brought resources in to help improve the system. Going forward, the Sakai 3 effort is *very* usability-focused.</p>
<p>Keep in mind, though, that usability means different things to different people. For faculty that are used to one platform, usability means anything that works like what they already know. But that&#8217;s a poor measure. You want to know (a) how easy is it for new users to learn from scratch, and (b) once you know how to use it, how many clicks do you need to make for common tasks? How hard is it to make a major mistake (like delete your entire course, for example)? And so on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate Angell</title>
		<link>http://mfeldstein.com/uncs-sakai-evaluation-results/#comment-1585</link>
		<dc:creator>Nate Angell</dc:creator>
		<pubDate>Wed, 26 May 2010 19:29:08 +0000</pubDate>
		<guid isPermaLink="false">http://mfeldstein.com/?p=1166#comment-1585</guid>
		<description>Bruce: Briefly, I think Sakai 2 usability has improved substantially
due to the maturity of the product—once basic functionality was
achieved and Sakai started to be used deeply and widely, more
resources were turned to usability, finding solutions based on real
user experience. The year-old Sakai development process and Product
Council were also formed to provide more formal frameworks and
stewardship for Sakai, with usability being one of the goals.
http://confluence.sakaiproject.org/display/MGT/How+Sakai+Development+Works
http://confluence.sakaiproject.org/display/MGT/Sakai+Product+Council

As for Sakai 3, one benefit for usability is that the project as a
whole is following a more user-centered design approach unlike the
more classic developer/ment-led design of Sakai 2. The following links
may give you some insight to the activities underway:

You might find the work of the 3akai UX group interesting:
http://confluence.sakaiproject.org/display/3AK/Sakai+3+Home

As well as the work of the Sakai Teaching &amp; Learning Working Group
around Sakai 3 Learning Capabilities:
http://confluence.sakaiproject.org/display/3AK/Teaching+and+Learning+Capabilities
http://confluence.sakaiproject.org/pages/viewpage.action?pageId=21954623

When it comes to formal Sakai 3 user testing, you can see some
documentation here:
http://confluence.sakaiproject.org/display/3AK/Sakai+3+User+Testing</description>
		<content:encoded><![CDATA[<p>Bruce: Briefly, I think Sakai 2 usability has improved substantially<br />
due to the maturity of the product—once basic functionality was<br />
achieved and Sakai started to be used deeply and widely, more<br />
resources were turned to usability, finding solutions based on real<br />
user experience. The year-old Sakai development process and Product<br />
Council were also formed to provide more formal frameworks and<br />
stewardship for Sakai, with usability being one of the goals.<br />
<a href="http://confluence.sakaiproject.org/display/MGT/How+Sakai+Development+Works" rel="nofollow">http://confluence.sakaiproject.org/display/MGT/How+Sakai+Development+Works</a><br />
<a href="http://confluence.sakaiproject.org/display/MGT/Sakai+Product+Council" rel="nofollow">http://confluence.sakaiproject.org/display/MGT/Sakai+Product+Council</a></p>
<p>As for Sakai 3, one benefit for usability is that the project as a<br />
whole is following a more user-centered design approach unlike the<br />
more classic developer/ment-led design of Sakai 2. The following links<br />
may give you some insight to the activities underway:</p>
<p>You might find the work of the 3akai UX group interesting:<br />
<a href="http://confluence.sakaiproject.org/display/3AK/Sakai+3+Home" rel="nofollow">http://confluence.sakaiproject.org/display/3AK/Sakai+3+Home</a></p>
<p>As well as the work of the Sakai Teaching &#038; Learning Working Group<br />
around Sakai 3 Learning Capabilities:<br />
<a href="http://confluence.sakaiproject.org/display/3AK/Teaching+and+Learning+Capabilities" rel="nofollow">http://confluence.sakaiproject.org/display/3AK/Teaching+and+Learning+Capabilities</a><br />
<a href="http://confluence.sakaiproject.org/pages/viewpage.action?pageId=21954623" rel="nofollow">http://confluence.sakaiproject.org/pages/viewpage.action?pageId=21954623</a></p>
<p>When it comes to formal Sakai 3 user testing, you can see some<br />
documentation here:<br />
<a href="http://confluence.sakaiproject.org/display/3AK/Sakai+3+User+Testing" rel="nofollow">http://confluence.sakaiproject.org/display/3AK/Sakai+3+User+Testing</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce</title>
		<link>http://mfeldstein.com/uncs-sakai-evaluation-results/#comment-1584</link>
		<dc:creator>Bruce</dc:creator>
		<pubDate>Wed, 26 May 2010 14:38:41 +0000</pubDate>
		<guid isPermaLink="false">http://mfeldstein.com/?p=1166#comment-1584</guid>
		<description>On the usability question, this indeed is crucial. Do you have any opinions about why Sakai&#039;s usability has improved? Is there something in particular the community has done in terms of process or structure to address this?

Also, am I correct that formal usability testing is a part of the Sakai 3 process?</description>
		<content:encoded><![CDATA[<p>On the usability question, this indeed is crucial. Do you have any opinions about why Sakai&#8217;s usability has improved? Is there something in particular the community has done in terms of process or structure to address this?</p>
<p>Also, am I correct that formal usability testing is a part of the Sakai 3 process?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Academic Study of Blackboard vs. Sakai at UNC School of Medicine</title>
		<link>http://mfeldstein.com/uncs-sakai-evaluation-results/#comment-1583</link>
		<dc:creator>Academic Study of Blackboard vs. Sakai at UNC School of Medicine</dc:creator>
		<pubDate>Thu, 04 Feb 2010 16:50:17 +0000</pubDate>
		<guid isPermaLink="false">http://mfeldstein.com/?p=1166#comment-1583</guid>
		<description>[...] Since the entire UNC system is currently evaluating a move from Blackboard to Sakai (I wrote a post recently about their evaluation results to-date), it looks like the School of Medicine&#8217;s [...]</description>
		<content:encoded><![CDATA[<p>[...] Since the entire UNC system is currently evaluating a move from Blackboard to Sakai (I wrote a post recently about their evaluation results to-date), it looks like the School of Medicine&#8217;s [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Korcuska</title>
		<link>http://mfeldstein.com/uncs-sakai-evaluation-results/#comment-1582</link>
		<dc:creator>Michael Korcuska</dc:creator>
		<pubDate>Fri, 16 Oct 2009 17:30:20 +0000</pubDate>
		<guid isPermaLink="false">http://mfeldstein.com/?p=1166#comment-1582</guid>
		<description>Good summary of an excellent summary of a thorough pilot. Lots of credit to the UNC Sakai team and especially Kim Eke. They&#039;ve clearly done a great job. I&#039;m sure this work will pay dividends in a smooth transition to Sakai (:-)).</description>
		<content:encoded><![CDATA[<p>Good summary of an excellent summary of a thorough pilot. Lots of credit to the UNC Sakai team and especially Kim Eke. They&#8217;ve clearly done a great job. I&#8217;m sure this work will pay dividends in a smooth transition to Sakai (:-)).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate Angell</title>
		<link>http://mfeldstein.com/uncs-sakai-evaluation-results/#comment-1581</link>
		<dc:creator>Nate Angell</dc:creator>
		<pubDate>Fri, 16 Oct 2009 00:29:17 +0000</pubDate>
		<guid isPermaLink="false">http://mfeldstein.com/?p=1166#comment-1581</guid>
		<description>I thought UNC&#039;s report was a valuable read as well, and showed how Sakai can perform well in a rigorous adoption process like UNC followed. The report also covered the value of using commercial vendor support for Sakai.

The only thing missing from the report was mention of the specific Sakai commercial affiliate UNC used during its pilot evaluation phase. A hint is in the screenshot of UNC&#039;s Sakai instance in the report, which reveals it to be rSmart ;) The team at rSmart likes to think a significant part of the success of UNC&#039;s pilot can be attributed to our assistance with Sakai configuration, training, hosting and support. I don&#039;t post this just to toot rSmart&#039;s horn, but to make sure others looking at UNC&#039;s success with Sakai know all the ingredients that stood behind it.</description>
		<content:encoded><![CDATA[<p>I thought UNC&#8217;s report was a valuable read as well, and showed how Sakai can perform well in a rigorous adoption process like UNC followed. The report also covered the value of using commercial vendor support for Sakai.</p>
<p>The only thing missing from the report was mention of the specific Sakai commercial affiliate UNC used during its pilot evaluation phase. A hint is in the screenshot of UNC&#8217;s Sakai instance in the report, which reveals it to be rSmart <img src='http://mfeldstein.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  The team at rSmart likes to think a significant part of the success of UNC&#8217;s pilot can be attributed to our assistance with Sakai configuration, training, hosting and support. I don&#8217;t post this just to toot rSmart&#8217;s horn, but to make sure others looking at UNC&#8217;s success with Sakai know all the ingredients that stood behind it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

