<?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: Deprivation</title>
	<atom:link href="http://www.nixit.co.nz/wordpress/2007/deprivation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nixit.co.nz/wordpress/2007/deprivation/</link>
	<description></description>
	<lastBuildDate>Mon, 10 Jan 2011 20:53:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tangled up in Purple :: End of an Affair</title>
		<link>http://www.nixit.co.nz/wordpress/2007/deprivation/comment-page-1/#comment-18467</link>
		<dc:creator>Tangled up in Purple :: End of an Affair</dc:creator>
		<pubDate>Sun, 11 Mar 2007 18:55:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.nixit.co.nz/wordpress/2007/03/07/deprivation/#comment-18467</guid>
		<description>[...] last couple of weeks has been difficult. Not only have I been deprived of many of my normal communication channels (and there is a whole lot more to say about that), but it&#8217;s also been a period where I have [...]</description>
		<content:encoded><![CDATA[<p>[...] last couple of weeks has been difficult. Not only have I been deprived of many of my normal communication channels (and there is a whole lot more to say about that), but it&#8217;s also been a period where I have [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nix</title>
		<link>http://www.nixit.co.nz/wordpress/2007/deprivation/comment-page-1/#comment-18460</link>
		<dc:creator>nix</dc:creator>
		<pubDate>Sun, 11 Mar 2007 17:42:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.nixit.co.nz/wordpress/2007/03/07/deprivation/#comment-18460</guid>
		<description>6. Predicted response time for ms_9?</description>
		<content:encoded><![CDATA[<p>6. Predicted response time for ms_9?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Artichoke</title>
		<link>http://www.nixit.co.nz/wordpress/2007/deprivation/comment-page-1/#comment-18349</link>
		<dc:creator>Artichoke</dc:creator>
		<pubDate>Sun, 11 Mar 2007 02:56:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.nixit.co.nz/wordpress/2007/03/07/deprivation/#comment-18349</guid>
		<description>Counting days has much to commend it Nix - it leads to new insights- 

This week, whilst you are preparing your ict_pd cluster milestone report to meet all expected deadlines so that amongst other things your cluster schools can be paid - you might care to ponder the stats from our cluster milestone experiences last year. 

Let us call these Clusters, Thing 1 and  Thing 2 - 

A quick check on the time taken from when the milestone is recorded as arriving at HQ and the time the ms_response letter pings back again makes an interesting maths project 

1.  Determine the average milestone response time for Thing 1 from the following data- Response times of ms_5 51 days, ms_6 65 days, ms_7 63 days and ms_8 102 days

2.  Express this average ms response time in weeks.

3.  Determine the average milestone response time for Thing 2 from the following data- Response times of ms_1 50 days, ms_2 66 days, ms_3 60 days and ms_4 102 days

4. Express this average ms response time in weeks.

5.  Find a word to describe the usefulness of feedback that arrives so long after the event reported on. 

Ours commonly arrive as the next milestone report is being collated. 

Makes me suspect that ms response time is not part of everyone&#039;s job description.

Must get back to writing mine - deadlines to be met and all that</description>
		<content:encoded><![CDATA[<p>Counting days has much to commend it Nix &#8211; it leads to new insights- </p>
<p>This week, whilst you are preparing your ict_pd cluster milestone report to meet all expected deadlines so that amongst other things your cluster schools can be paid &#8211; you might care to ponder the stats from our cluster milestone experiences last year. </p>
<p>Let us call these Clusters, Thing 1 and  Thing 2 &#8211; </p>
<p>A quick check on the time taken from when the milestone is recorded as arriving at HQ and the time the ms_response letter pings back again makes an interesting maths project </p>
<p>1.  Determine the average milestone response time for Thing 1 from the following data- Response times of ms_5 51 days, ms_6 65 days, ms_7 63 days and ms_8 102 days</p>
<p>2.  Express this average ms response time in weeks.</p>
<p>3.  Determine the average milestone response time for Thing 2 from the following data- Response times of ms_1 50 days, ms_2 66 days, ms_3 60 days and ms_4 102 days</p>
<p>4. Express this average ms response time in weeks.</p>
<p>5.  Find a word to describe the usefulness of feedback that arrives so long after the event reported on. </p>
<p>Ours commonly arrive as the next milestone report is being collated. </p>
<p>Makes me suspect that ms response time is not part of everyone&#8217;s job description.</p>
<p>Must get back to writing mine &#8211; deadlines to be met and all that</p>
]]></content:encoded>
	</item>
</channel>
</rss>

