<?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: 3 &#8211; Use Cases</title>
	<atom:link href="http://shipitontheside.com/2008/12/3-use-cases/feed/" rel="self" type="application/rss+xml" />
	<link>http://shipitontheside.com/2008/12/3-use-cases/</link>
	<description>The podcast about building a Software Startup as a side job.</description>
	<lastBuildDate>Tue, 04 May 2010 08:31:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Burns</title>
		<link>http://shipitontheside.com/2008/12/3-use-cases/comment-page-1/#comment-16</link>
		<dc:creator>John Burns</dc:creator>
		<pubDate>Thu, 01 Jan 2009 16:17:59 +0000</pubDate>
		<guid isPermaLink="false">http://shipitontheside.com/?p=32#comment-16</guid>
		<description>Another great episode. What follows are notes as I listened.

Word of the day/week... in this episode it is actually a phrase... BUT that is being much too literal.

I like that you pointed out that &quot;smaller&quot; projects do not require the same effort as &quot;larger&quot; projects - specifically: Use Cases.

I use a calculator program in my courses - handling the 4 common math symbols. It is small AND any person in college should &quot;know&quot; the hows/whys - but converting it to programming concepts does present enough of a challenge that 200 level students do struggle.

Because of this - I think the &quot;size&quot; of project is also dependent on the skill level of the programmer/developer. Less skills = more structure required to the process...enabling them to grasp the concept.

Concept of Actor (as defined in this episode) is something that I have tried to get across to students - but they do struggle to conceptualize &quot;things/people&quot;. I don&#039;t use the term - rather I use the object: server, computer, person. That seems to help.

The bullet list IS how most people I have worked with - &quot;start a project&quot;. That brainstorm usually then splits into required items, would likes, and the 3rd batch &quot;maybes or unlikely&quot;.

The example of Paypal NOT being a use case - is eye-opening! I would considered it one of those &quot;external actors&quot;.

The concepts of &quot;campaign&quot; and &quot;thinking about actor/use cases&quot; has me thinking about the project I am beginning at work. Mind is working.

I like the concepts of people focusing on their smaller tasks and the software &quot;doing&quot; the work.

Concept of NO and qualifying prospects -- The 80:20 rule comes to light.


In listening to your discussion on identifying prospects - I almost think I might require listening to your podcast to understand the &quot;process &amp; discussion&quot; that takes place to define a project. I don&#039;t believe students know how much effort is really necessary... the &quot;let&#039;s start typing&quot; concept that most think is how to get a project off the ground.

Identifying authority and closing sale - especially closing sale -- tough part for non-sales person. I remember this from working in/managing retail store. My sales people had varying degrees of success, even after training/practice sessions. &quot;Will that be cash or credit&quot;... is a tough step for many people.


OK - writing code to enable UML Lounge characters to have movement/positions is great. But... Curtis almost died... Martin... you have to &quot;warn him&quot;... As much as Curtis wants to edit... It&#039;s great to hear what sounds like &quot;real time&quot;. I really think this is better than more scripted/processed productions.

Candidate design != Demo != final application</description>
		<content:encoded><![CDATA[<p>Another great episode. What follows are notes as I listened.</p>
<p>Word of the day/week&#8230; in this episode it is actually a phrase&#8230; BUT that is being much too literal.</p>
<p>I like that you pointed out that &#8220;smaller&#8221; projects do not require the same effort as &#8220;larger&#8221; projects &#8211; specifically: Use Cases.</p>
<p>I use a calculator program in my courses &#8211; handling the 4 common math symbols. It is small AND any person in college should &#8220;know&#8221; the hows/whys &#8211; but converting it to programming concepts does present enough of a challenge that 200 level students do struggle.</p>
<p>Because of this &#8211; I think the &#8220;size&#8221; of project is also dependent on the skill level of the programmer/developer. Less skills = more structure required to the process&#8230;enabling them to grasp the concept.</p>
<p>Concept of Actor (as defined in this episode) is something that I have tried to get across to students &#8211; but they do struggle to conceptualize &#8220;things/people&#8221;. I don&#8217;t use the term &#8211; rather I use the object: server, computer, person. That seems to help.</p>
<p>The bullet list IS how most people I have worked with &#8211; &#8220;start a project&#8221;. That brainstorm usually then splits into required items, would likes, and the 3rd batch &#8220;maybes or unlikely&#8221;.</p>
<p>The example of Paypal NOT being a use case &#8211; is eye-opening! I would considered it one of those &#8220;external actors&#8221;.</p>
<p>The concepts of &#8220;campaign&#8221; and &#8220;thinking about actor/use cases&#8221; has me thinking about the project I am beginning at work. Mind is working.</p>
<p>I like the concepts of people focusing on their smaller tasks and the software &#8220;doing&#8221; the work.</p>
<p>Concept of NO and qualifying prospects &#8212; The 80:20 rule comes to light.</p>
<p>In listening to your discussion on identifying prospects &#8211; I almost think I might require listening to your podcast to understand the &#8220;process &amp; discussion&#8221; that takes place to define a project. I don&#8217;t believe students know how much effort is really necessary&#8230; the &#8220;let&#8217;s start typing&#8221; concept that most think is how to get a project off the ground.</p>
<p>Identifying authority and closing sale &#8211; especially closing sale &#8212; tough part for non-sales person. I remember this from working in/managing retail store. My sales people had varying degrees of success, even after training/practice sessions. &#8220;Will that be cash or credit&#8221;&#8230; is a tough step for many people.</p>
<p>OK &#8211; writing code to enable UML Lounge characters to have movement/positions is great. But&#8230; Curtis almost died&#8230; Martin&#8230; you have to &#8220;warn him&#8221;&#8230; As much as Curtis wants to edit&#8230; It&#8217;s great to hear what sounds like &#8220;real time&#8221;. I really think this is better than more scripted/processed productions.</p>
<p>Candidate design != Demo != final application</p>
]]></content:encoded>
	</item>
</channel>
</rss>
