<?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"
	>
<channel>
	<title>Comments on: 3 Hour Full Code Press</title>
	<atom:link href="http://liveandletlearn.net/3-hour-full-code-press/feed/" rel="self" type="application/rss+xml" />
	<link>http://liveandletlearn.net/3-hour-full-code-press/</link>
	<description>Living and learning for life</description>
	<pubDate>Thu, 20 Nov 2008 22:31:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Five things all clients want to know at live and let learn</title>
		<link>http://liveandletlearn.net/3-hour-full-code-press/#comment-21141</link>
		<dc:creator>Five things all clients want to know at live and let learn</dc:creator>
		<pubDate>Mon, 16 Jul 2007 05:28:55 +0000</pubDate>
		<guid isPermaLink="false">http://liveandletlearn.net/3-hour-full-code-press/#comment-21141</guid>
		<description>[...] processes, and needing to communicate these to get your next pay (hopefully activities like the 3Hr Full Code Press help to some [...]</description>
		<content:encoded><![CDATA[<p>[...] processes, and needing to communicate these to get your next pay (hopefully activities like the 3Hr Full Code Press help to some [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://liveandletlearn.net/3-hour-full-code-press/#comment-18555</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Sun, 10 Jun 2007 21:08:06 +0000</pubDate>
		<guid isPermaLink="false">http://liveandletlearn.net/3-hour-full-code-press/#comment-18555</guid>
		<description>Thanks Jen, Andy and Jesse.

Glad you three all took lots away from the experience! Great points about knowing when to move on - it's too easy to get stuck on some detail (colours, wording, semantics) that really shouldn't have a high priority for a quick prototype (especially with 3 hours hey!).

Jesse, I think your recommendations for the way the group should operate are pretty well founded - although I think Jen and Andy's group did manage to do both - split up to Get Things Done, while still working together to learn for the good bits. Probably depends on the group that you're in.

I'm glad it was a fun learning experience for you guys! I was also hoping to get some feedback from people who perhaps didn't enjoy their group dynamics as much as what you three did, to see if it was still a worthwhile &lt;em&gt;learning experience&lt;/em&gt; in their eyes...</description>
		<content:encoded><![CDATA[<p>Thanks Jen, Andy and Jesse.</p>
<p>Glad you three all took lots away from the experience! Great points about knowing when to move on - it&#8217;s too easy to get stuck on some detail (colours, wording, semantics) that really shouldn&#8217;t have a high priority for a quick prototype (especially with 3 hours hey!).</p>
<p>Jesse, I think your recommendations for the way the group should operate are pretty well founded - although I think Jen and Andy&#8217;s group did manage to do both - split up to Get Things Done, while still working together to learn for the good bits. Probably depends on the group that you&#8217;re in.</p>
<p>I&#8217;m glad it was a fun learning experience for you guys! I was also hoping to get some feedback from people who perhaps didn&#8217;t enjoy their group dynamics as much as what you three did, to see if it was still a worthwhile <em>learning experience</em> in their eyes&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse</title>
		<link>http://liveandletlearn.net/3-hour-full-code-press/#comment-17995</link>
		<dc:creator>Jesse</dc:creator>
		<pubDate>Wed, 06 Jun 2007 23:39:40 +0000</pubDate>
		<guid isPermaLink="false">http://liveandletlearn.net/3-hour-full-code-press/#comment-17995</guid>
		<description>I thought it was great!

Having a deadline will help us to practice estimating time better and we get the chance to experience working under pressure.

It is important to delegate tasks to those who are most suited because of time constraints. I would recommend the groups do not split up to do their task, but watch and learn from the more experienced person(s). Or the more experienced person could sit back and instruct the others so they can get some practice (just an idea, but do whatever helps you learn better or gets the task done).

I agree with Andy, knowing when to move on is very important. Byron and I decided to get a rough layout of the site done first and this gave us more time to worry about making it pixel perfect and getting the right colours.

Looking forward to the next challenge!</description>
		<content:encoded><![CDATA[<p>I thought it was great!</p>
<p>Having a deadline will help us to practice estimating time better and we get the chance to experience working under pressure.</p>
<p>It is important to delegate tasks to those who are most suited because of time constraints. I would recommend the groups do not split up to do their task, but watch and learn from the more experienced person(s). Or the more experienced person could sit back and instruct the others so they can get some practice (just an idea, but do whatever helps you learn better or gets the task done).</p>
<p>I agree with Andy, knowing when to move on is very important. Byron and I decided to get a rough layout of the site done first and this gave us more time to worry about making it pixel perfect and getting the right colours.</p>
<p>Looking forward to the next challenge!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://liveandletlearn.net/3-hour-full-code-press/#comment-17780</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Wed, 06 Jun 2007 03:37:37 +0000</pubDate>
		<guid isPermaLink="false">http://liveandletlearn.net/3-hour-full-code-press/#comment-17780</guid>
		<description>It was great to work on something with clear goals and a definite deadline (and no maintenance cycle concerns :P )

Although we struggled towards the end to get details wrapped up, I don't think it was because the scope of the project was too large, but because not many of us had experience in managing the multiple aspects (and people) of a project within a short time limit. Knowing when and how to say "let's move on" is difficult.

Assessing team member skills and delegating appropriate tasks came out as important. My group was great in that both Jen and Vikki suggested things they knew they could do, looked in my direction for agreement, then dove straight into it. We're a pretty collaborative class and we all have a rough idea of each other's skills, but even then I think we had our moments of vagueness as to what role to play. It's easy to see how having a team of unknowns would make a deadline impossible without honest self-assessment, disclosure and delegated responsibility beforehand.

I think the review afterwards taught us a lot about planning better next time. It'll be interesting to see how it goes with the teams shuffled and people taking on different roles.

It was a really great exercise overall.</description>
		<content:encoded><![CDATA[<p>It was great to work on something with clear goals and a definite deadline (and no maintenance cycle concerns :P )</p>
<p>Although we struggled towards the end to get details wrapped up, I don&#8217;t think it was because the scope of the project was too large, but because not many of us had experience in managing the multiple aspects (and people) of a project within a short time limit. Knowing when and how to say &#8220;let&#8217;s move on&#8221; is difficult.</p>
<p>Assessing team member skills and delegating appropriate tasks came out as important. My group was great in that both Jen and Vikki suggested things they knew they could do, looked in my direction for agreement, then dove straight into it. We&#8217;re a pretty collaborative class and we all have a rough idea of each other&#8217;s skills, but even then I think we had our moments of vagueness as to what role to play. It&#8217;s easy to see how having a team of unknowns would make a deadline impossible without honest self-assessment, disclosure and delegated responsibility beforehand.</p>
<p>I think the review afterwards taught us a lot about planning better next time. It&#8217;ll be interesting to see how it goes with the teams shuffled and people taking on different roles.</p>
<p>It was a really great exercise overall.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jen Cork</title>
		<link>http://liveandletlearn.net/3-hour-full-code-press/#comment-17719</link>
		<dc:creator>Jen Cork</dc:creator>
		<pubDate>Tue, 05 Jun 2007 22:23:00 +0000</pubDate>
		<guid isPermaLink="false">http://liveandletlearn.net/3-hour-full-code-press/#comment-17719</guid>
		<description>Well,
this morning was a great!! It was a really awesome hands on experience of all aspects of web design.
There was a lot of content to cover so it was brilliant to have to work quickly and under pressure for a deadline.
Everyone came up with something it was a great learning experience good and bad.
For the next time the project, I would allocate more time to the coding of the site.

Overal great fun, excellent experience in utilizing all of the skills we have learnt so far in the course.

Nice one Michael!!</description>
		<content:encoded><![CDATA[<p>Well,<br />
this morning was a great!! It was a really awesome hands on experience of all aspects of web design.<br />
There was a lot of content to cover so it was brilliant to have to work quickly and under pressure for a deadline.<br />
Everyone came up with something it was a great learning experience good and bad.<br />
For the next time the project, I would allocate more time to the coding of the site.</p>
<p>Overal great fun, excellent experience in utilizing all of the skills we have learnt so far in the course.</p>
<p>Nice one Michael!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
