<?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 for Scaled Agile Framework</title>
	<atom:link href="http://scaledagileframework.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://scaledagileframework.com</link>
	<description>Enterprise Scale Agility</description>
	<lastBuildDate>Tue, 15 May 2012 21:53:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>Comment on New Detail Pages: Spikes, Tasks and Scrum/Agile Master by DeanLeffingwell</title>
		<link>http://scaledagileframework.com/new-detail-pages-spikes-tasks-and-scrumagile-master/#comment-21</link>
		<dc:creator>DeanLeffingwell</dc:creator>
		<pubDate>Tue, 15 May 2012 21:53:49 +0000</pubDate>
		<guid isPermaLink="false">http://scaledagileframework.com/?p=1932#comment-21</guid>
		<description>NFRs are a complicated question. We&#039;ve modeled them as &quot;constraints on the backlog&quot; (both Team and Program; see the little NFR icon that anchors the backlog) rather than backlog items, as backlog items can be safely deleted when completed (subject to the persistence of acceptance tests which guard against regression problems). NFRS are usually here to stay and have to be reconsidered for much new functionality. It is an important topic and I devote an entire chapter to them in Agile Software requirements.</description>
		<content:encoded><![CDATA[<p>NFRs are a complicated question. We&#8217;ve modeled them as &#8220;constraints on the backlog&#8221; (both Team and Program; see the little NFR icon that anchors the backlog) rather than backlog items, as backlog items can be safely deleted when completed (subject to the persistence of acceptance tests which guard against regression problems). NFRS are usually here to stay and have to be reconsidered for much new functionality. It is an important topic and I devote an entire chapter to them in Agile Software requirements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New Detail Pages: Spikes, Tasks and Scrum/Agile Master by Manny Sullano</title>
		<link>http://scaledagileframework.com/new-detail-pages-spikes-tasks-and-scrumagile-master/#comment-12</link>
		<dc:creator>Manny Sullano</dc:creator>
		<pubDate>Tue, 01 May 2012 03:35:13 +0000</pubDate>
		<guid isPermaLink="false">http://scaledagileframework.com/?p=1932#comment-12</guid>
		<description>Great&#160;work so far!&#160;Just quick question, so&#160;when&#160;do NFRs&#160;get done?&#160;Should&#160;an&#160;NFR&#160;become a backlog item (like a Story) in&#160;an iteration that Agile&#160;Team&#160;should&#160;tasked out? Also,&#160;how do we handle compliance type items,&#160;like&#160;an NFR?</description>
		<content:encoded><![CDATA[<p>Great&nbsp;work so far!&nbsp;Just quick question, so&nbsp;when&nbsp;do NFRs&nbsp;get done?&nbsp;Should&nbsp;an&nbsp;NFR&nbsp;become a backlog item (like a Story) in&nbsp;an iteration that Agile&nbsp;Team&nbsp;should&nbsp;tasked out? Also,&nbsp;how do we handle compliance type items,&nbsp;like&nbsp;an NFR?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Release Management Team by Jim O'Leary</title>
		<link>http://scaledagileframework.com/scaled-agile-framework/program/release-management-team/#comment-9</link>
		<dc:creator>Jim O'Leary</dc:creator>
		<pubDate>Fri, 30 Mar 2012 04:51:42 +0000</pubDate>
		<guid isPermaLink="false">http://scaledagileframework.com/?page_id=148#comment-9</guid>
		<description>Some other RMT members to suggest include tech support/service, training and documentation, and finance/accounting.
&#160;
Seems like the regular coordination activities would also cover what adjustments the non-development groups need to make based on scope updates coming from the dev&#160;team.</description>
		<content:encoded><![CDATA[<p>Some other RMT members to suggest include tech support/service, training and documentation, and finance/accounting.<br />
&nbsp;<br />
Seems like the regular coordination activities would also cover what adjustments the non-development groups need to make based on scope updates coming from the dev&nbsp;team.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

