<?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: Working Notes 2012 #8 Learning Platforms, Business Analysis, HR and JISC Elevator</title>
	<atom:link href="http://alisonpope.me.uk/journal/archives/2012/02/1266/feed/" rel="self" type="application/rss+xml" />
	<link>http://alisonpope.me.uk/journal/archives/2012/02/1266/</link>
	<description></description>
	<lastBuildDate>Tue, 21 Feb 2012 09:27:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Alison Pope</title>
		<link>http://alisonpope.me.uk/journal/archives/2012/02/1266/comment-page-1/#comment-9606</link>
		<dc:creator>Alison Pope</dc:creator>
		<pubDate>Tue, 21 Feb 2012 09:27:17 +0000</pubDate>
		<guid isPermaLink="false">http://alisonpope.me.uk/journal/?p=1266#comment-9606</guid>
		<description>Thanks Andy, very helpful.</description>
		<content:encoded><![CDATA[<p>Thanks Andy, very helpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy McGregor</title>
		<link>http://alisonpope.me.uk/journal/archives/2012/02/1266/comment-page-1/#comment-9605</link>
		<dc:creator>Andy McGregor</dc:creator>
		<pubDate>Mon, 20 Feb 2012 15:06:37 +0000</pubDate>
		<guid isPermaLink="false">http://alisonpope.me.uk/journal/?p=1266#comment-9605</guid>
		<description>Hi Alison. I&#039;m managing the pilot of the elevator for JISC. This is an experiment for us so all the details are not worked out and there will be some elements of learning as we go. However what I have in mind for the successful projects in terms of documentation will be a very stripped down project plan (a couple of pages) and reporting will be via a project blog, with an emphasis on sharing the lessons that you learn from the project and sharing any outputs you produce. We will also need a final budget report on how the money was spent. That will be it. We already use blogs to replace reporting for a number of projects at the moment and the rule of thumb is that we expect one blog post per month of the project.  As this is an experiment we will also expect projects to dedicate a small amount of time to working with someone pulling together evidence on how the pilot has gone. Does that answer your questions?

I&#039;ll get this added to the FAQ page on elevator.</description>
		<content:encoded><![CDATA[<p>Hi Alison. I&#8217;m managing the pilot of the elevator for JISC. This is an experiment for us so all the details are not worked out and there will be some elements of learning as we go. However what I have in mind for the successful projects in terms of documentation will be a very stripped down project plan (a couple of pages) and reporting will be via a project blog, with an emphasis on sharing the lessons that you learn from the project and sharing any outputs you produce. We will also need a final budget report on how the money was spent. That will be it. We already use blogs to replace reporting for a number of projects at the moment and the rule of thumb is that we expect one blog post per month of the project.  As this is an experiment we will also expect projects to dedicate a small amount of time to working with someone pulling together evidence on how the pilot has gone. Does that answer your questions?</p>
<p>I&#8217;ll get this added to the FAQ page on elevator.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

