<?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: Finally &#8211; an agile workflow</title>
	<atom:link href="http://conviviality.ca/2009/11/finally-an-agile-workflow-approach/feed/" rel="self" type="application/rss+xml" />
	<link>http://conviviality.ca/2009/11/finally-an-agile-workflow-approach/</link>
	<description>simple, powerful, resonant</description>
	<lastBuildDate>Fri, 15 Jan 2010 22:03:42 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: davidp</title>
		<link>http://conviviality.ca/2009/11/finally-an-agile-workflow-approach/comment-page-1/#comment-75</link>
		<dc:creator>davidp</dc:creator>
		<pubDate>Wed, 18 Nov 2009 19:06:33 +0000</pubDate>
		<guid isPermaLink="false">http://conviviality.ca/?p=227#comment-75</guid>
		<description>Thanks for your comments, Scott.  Always appreciated

However, I think the diagram describes more than an IP clearance process.  Embedded within it are processes called:  creation, quality control and technical.  I know I have heard you speak (lament) on the quality control (or lack thereof) item at various stages of OER development processes.

These are macro process categories, that while not described in any detail, announce that there are multiple steps in the OER creation and reuse process that also need to be further described and/or built-out in a more convivial manner.  

For me, this diagram represents a high-level view that could form the basis for a more detailed &quot;how-to,&quot; or form the basis of a workshop series that explored all of the *actual* behaviours and practices you note. It might then begin to frame the optimal processes in a *useful and usable* set of resources that could attract more instructors to both create and reuse in whatever manner seemed most efficacious *to them.*</description>
		<content:encoded><![CDATA[<p>Thanks for your comments, Scott.  Always appreciated</p>
<p>However, I think the diagram describes more than an IP clearance process.  Embedded within it are processes called:  creation, quality control and technical.  I know I have heard you speak (lament) on the quality control (or lack thereof) item at various stages of OER development processes.</p>
<p>These are macro process categories, that while not described in any detail, announce that there are multiple steps in the OER creation and reuse process that also need to be further described and/or built-out in a more convivial manner.  </p>
<p>For me, this diagram represents a high-level view that could form the basis for a more detailed &#8220;how-to,&#8221; or form the basis of a workshop series that explored all of the *actual* behaviours and practices you note. It might then begin to frame the optimal processes in a *useful and usable* set of resources that could attract more instructors to both create and reuse in whatever manner seemed most efficacious *to them.*</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Leslie</title>
		<link>http://conviviality.ca/2009/11/finally-an-agile-workflow-approach/comment-page-1/#comment-74</link>
		<dc:creator>Scott Leslie</dc:creator>
		<pubDate>Wed, 18 Nov 2009 18:22:39 +0000</pubDate>
		<guid isPermaLink="false">http://conviviality.ca/?p=227#comment-74</guid>
		<description>Not sure I get why this is helpful. Seems like pretty basic rights clearance workflow. If this is what you were looking for, an abstracted idealized workflow that doesn&#039;t reflect actual practice or tools, then I have misunderstood the quest for an &quot;agile OER workflow.&quot; I guess I always simply understood that assessing the rights of a resource to be used is sort of fundamental *if* copyright is even a consideration in reusing materials (an assumption I think we should question in education, where *actual* behaviour seems to largely skip over the copyright issue altogether.)</description>
		<content:encoded><![CDATA[<p>Not sure I get why this is helpful. Seems like pretty basic rights clearance workflow. If this is what you were looking for, an abstracted idealized workflow that doesn&#8217;t reflect actual practice or tools, then I have misunderstood the quest for an &#8220;agile OER workflow.&#8221; I guess I always simply understood that assessing the rights of a resource to be used is sort of fundamental *if* copyright is even a consideration in reusing materials (an assumption I think we should question in education, where *actual* behaviour seems to largely skip over the copyright issue altogether.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
