<?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: How To Start The Use Case Process For Agile Software Development</title>
	<atom:link href="http://tynerblain.com/blog/2007/03/28/how-to-start-use-cases/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2007/03/28/how-to-start-use-cases/</link>
	<description>Software product success.</description>
	<lastBuildDate>Thu, 18 Mar 2010 20:39:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2007/03/28/how-to-start-use-cases/comment-page-1/#comment-566949</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Tue, 09 Mar 2010 15:58:06 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/03/28/how-to-start-use-cases/#comment-566949</guid>
		<description>Thanks, FaustoChi (&lt;a href=&quot;http://twitter.com/faustochi&quot; rel=&quot;nofollow&quot;&gt;@faustochi&lt;/a&gt; on Twitter), and welcome to Tyner Blain.

Remember that &quot;agile does not equal lack of scope!&quot;  At some level, scope is usually locked, and at the next level of detail it is evolving and collaborative.  Just like we make decisions about how to rework our solutions iteratively, we make decisions about how to redirect our efforts iteratively.

&lt;a href=&quot;http://twitter.com/sehlhorst&quot; rel=&quot;nofollow&quot;&gt;@sehlhorst&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Thanks, FaustoChi (<a href="http://twitter.com/faustochi" rel="nofollow">@faustochi</a> on Twitter), and welcome to Tyner Blain.</p>
<p>Remember that &#8220;agile does not equal lack of scope!&#8221;  At some level, scope is usually locked, and at the next level of detail it is evolving and collaborative.  Just like we make decisions about how to rework our solutions iteratively, we make decisions about how to redirect our efforts iteratively.</p>
<p><a href="http://twitter.com/sehlhorst" rel="nofollow">@sehlhorst</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FaustoChi</title>
		<link>http://tynerblain.com/blog/2007/03/28/how-to-start-use-cases/comment-page-1/#comment-566597</link>
		<dc:creator>FaustoChi</dc:creator>
		<pubDate>Mon, 08 Mar 2010 04:08:47 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/03/28/how-to-start-use-cases/#comment-566597</guid>
		<description>I have had good results using use cases in two flavors: large projects and small projects. The fast way (small projects) let to the team and users agree on how the system provides functionality to users. It’s important for programmers to know how the user will test the functionality developed and this specification is contained in separate artifact called test case. In agile methods the user story has in the same place both agreement about functionality and how them will be tested. In this perspective is better to have both descriptions in one place.
I agree with your blog and it has some common concepts with requirement discipline of RUP, and some kind of scope is out in agile methods because they put emphasis on the collaboration.</description>
		<content:encoded><![CDATA[<p>I have had good results using use cases in two flavors: large projects and small projects. The fast way (small projects) let to the team and users agree on how the system provides functionality to users. It’s important for programmers to know how the user will test the functionality developed and this specification is contained in separate artifact called test case. In agile methods the user story has in the same place both agreement about functionality and how them will be tested. In this perspective is better to have both descriptions in one place.<br />
I agree with your blog and it has some common concepts with requirement discipline of RUP, and some kind of scope is out in agile methods because they put emphasis on the collaboration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2009-11-25 &#8226; Bare Identity</title>
		<link>http://tynerblain.com/blog/2007/03/28/how-to-start-use-cases/comment-page-1/#comment-539557</link>
		<dc:creator>links for 2009-11-25 &#8226; Bare Identity</dc:creator>
		<pubDate>Thu, 26 Nov 2009 00:02:07 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/03/28/how-to-start-use-cases/#comment-539557</guid>
		<description>[...] How To Start The Use Case Process For Agile Software Development &#124; Tyner Blain (tags: prod productmanagement agile requirements tynerblain usecases) [...]</description>
		<content:encoded><![CDATA[<p>[...] How To Start The Use Case Process For Agile Software Development | Tyner Blain (tags: prod productmanagement agile requirements tynerblain usecases) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2008-04-01 &#171; steinarcarlsen</title>
		<link>http://tynerblain.com/blog/2007/03/28/how-to-start-use-cases/comment-page-1/#comment-337908</link>
		<dc:creator>links for 2008-04-01 &#171; steinarcarlsen</dc:creator>
		<pubDate>Tue, 01 Apr 2008 21:30:49 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/03/28/how-to-start-use-cases/#comment-337908</guid>
		<description>[...] How To Start The Use Case Process For Agile Software Development &#124; Tyner Blain (tags: agile usecase) [...]</description>
		<content:encoded><![CDATA[<p>[...] How To Start The Use Case Process For Agile Software Development | Tyner Blain (tags: agile usecase) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What is the key to writing a good Use Case?: Ask A Good Product Manager: Your product management questions answered</title>
		<link>http://tynerblain.com/blog/2007/03/28/how-to-start-use-cases/comment-page-1/#comment-290402</link>
		<dc:creator>What is the key to writing a good Use Case?: Ask A Good Product Manager: Your product management questions answered</dc:creator>
		<pubDate>Mon, 04 Feb 2008 22:38:14 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/03/28/how-to-start-use-cases/#comment-290402</guid>
		<description>[...] Answer from Scott Sehlhorst of Tyner Blain: This is really a great question. As with many good questions, the answer starts with &#8220;It depends.&#8221; You point out that your team is resisting the RUP as being too heavy-weight. I&#8217;m going to answer your question in terms of both process and format - as they go hand in hand. I wrote about how to approach writing use cases as part of an agile project about a year ago, and that approach works really well in that environment. I&#8217;ve found since then, that it also works extremely well on non-agile projects. [...]</description>
		<content:encoded><![CDATA[<p>[...] Answer from Scott Sehlhorst of Tyner Blain: This is really a great question. As with many good questions, the answer starts with &#8220;It depends.&#8221; You point out that your team is resisting the RUP as being too heavy-weight. I&#8217;m going to answer your question in terms of both process and format &#8211; as they go hand in hand. I wrote about how to approach writing use cases as part of an agile project about a year ago, and that approach works really well in that environment. I&#8217;ve found since then, that it also works extremely well on non-agile projects. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
