<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.7.3" -->
<rss version="2.0">
	<channel>
		<title>Kick-Starting Your Projects; What You Should Know about Defining Scope</title>
		<description>Comments for Kick-Starting Your Projects; What You Should Know about Defining Scope at http://www.projecttimes.com , comment 1 to 5 out of 5 comments</description>
		<link>http://www.projecttimes.com</link>
		<lastBuildDate>Sat, 31 Jul 2010 02:38:57 +0100</lastBuildDate>
        <generator>FeedCreator 1.7.3</generator>
		<item>
			<title>...</title>
			<link>http://www.projecttimes.com/scope-management/kick-starting-your-projects-what-you-should-you-know-about-defining-scope.html#comment-219</link>
			<description>Nice article.  However the &quot;business requirement&quot; definition reads more like a system or functional/non functional requirement.  These definitions often get confused and also lead to problems in defining scope in a project as the team starts talking solution before understanding the real business requirement.  This leads to building a product that has delivers all the features it set out to, but does not address the business needs as the article describes further on.

Adrian - adrian_ing</description>
			<pubDate>Sat, 06 Jun 2009 02:40:15 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://www.projecttimes.com/scope-management/kick-starting-your-projects-what-you-should-you-know-about-defining-scope.html#comment-218</link>
			<description>I find defining scope will become easier as you repeat the same type of projects over and over with taking lessons learned /experiences from one project to another.  - mazalam</description>
			<pubDate>Fri, 05 Jun 2009 07:12:29 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://www.projecttimes.com/scope-management/kick-starting-your-projects-what-you-should-you-know-about-defining-scope.html#comment-217</link>
			<description>very interesting, define the problem first. The first step to succeed a project is to understand the problem to solve and avoid to jump to the solution too fast. Examples help to understand the concept. - romain.beaulieu</description>
			<pubDate>Thu, 04 Jun 2009 08:20:09 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://www.projecttimes.com/scope-management/kick-starting-your-projects-what-you-should-you-know-about-defining-scope.html#comment-215</link>
			<description>Very well explained, loved the examples. - markosantos</description>
			<pubDate>Wed, 03 Jun 2009 11:53:01 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://www.projecttimes.com/scope-management/kick-starting-your-projects-what-you-should-you-know-about-defining-scope.html#comment-214</link>
			<description>Good, basic article. Examples well used to present points. - dfuller</description>
			<pubDate>Wed, 03 Jun 2009 11:44:17 +0100</pubDate>
		</item>
	</channel>
</rss>
