<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Agile @ Adobe</title>
	<atom:link href="http://blogs.adobe.com/agile/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.adobe.com/agile</link>
	<description>Ideas, experiences, and challenges related to Adobe&#039;s journey towards Agility.</description>
	<lastBuildDate>Tue, 27 Nov 2012 07:43:57 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Scrum: the Model-T of Agile?</title>
		<link>http://blogs.adobe.com/agile/2012/11/27/scrum-the-model-t-of-agile/</link>
		<comments>http://blogs.adobe.com/agile/2012/11/27/scrum-the-model-t-of-agile/#comments</comments>
		<pubDate>Tue, 27 Nov 2012 07:43:57 +0000</pubDate>
		<dc:creator>Peter Green</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.adobe.com/agile/?p=99</guid>
		<description><![CDATA[Several years ago during a break in a scrum training class, a student approached me and asked “what do you think will come after scrum?”. At the time, I had no answer for this question. The several teams that I &#8230; <a href="http://blogs.adobe.com/agile/2012/11/27/scrum-the-model-t-of-agile/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://blogs.adobe.com/agile/2012/11/27/scrum-the-model-t-of-agile/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Talk to your customers</title>
		<link>http://blogs.adobe.com/agile/2012/11/13/talk-to-your-customers/</link>
		<comments>http://blogs.adobe.com/agile/2012/11/13/talk-to-your-customers/#comments</comments>
		<pubDate>Tue, 13 Nov 2012 18:00:40 +0000</pubDate>
		<dc:creator>Peter Green</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Agile]]></category>

		<guid isPermaLink="false">http://blogs.adobe.com/agile/?p=93</guid>
		<description><![CDATA[I have heard something multiple times this week, something that has me a bit concerned. The gist of the sentiment is something like this: &#8220;Oh, we discourage the developers from talking to customers; we don&#8217;t want them to be distracted &#8230; <a href="http://blogs.adobe.com/agile/2012/11/13/talk-to-your-customers/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://blogs.adobe.com/agile/2012/11/13/talk-to-your-customers/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Premiere Pro Agile Adoption Experience Report from Agile 2012</title>
		<link>http://blogs.adobe.com/agile/2012/08/17/premiere-pro-agile-adoption-experience-report-from-agile-2012/</link>
		<comments>http://blogs.adobe.com/agile/2012/08/17/premiere-pro-agile-adoption-experience-report-from-agile-2012/#comments</comments>
		<pubDate>Fri, 17 Aug 2012 04:37:19 +0000</pubDate>
		<dc:creator>Peter Green</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.adobe.com/agile/?p=78</guid>
		<description><![CDATA[Hi all, I had the opportunity to present an experience report about the Adobe Premiere Pro team&#8217;s adoption of scrum at the Agile 2012 conference today. I&#8217;ve uploaded the 10 page paper here, as well as the slides from the &#8230; <a href="http://blogs.adobe.com/agile/2012/08/17/premiere-pro-agile-adoption-experience-report-from-agile-2012/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://blogs.adobe.com/agile/2012/08/17/premiere-pro-agile-adoption-experience-report-from-agile-2012/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Agile 2012 day 1: Leadership Agility</title>
		<link>http://blogs.adobe.com/agile/2012/08/14/agile-2012-day-1-leadership-agility/</link>
		<comments>http://blogs.adobe.com/agile/2012/08/14/agile-2012-day-1-leadership-agility/#comments</comments>
		<pubDate>Tue, 14 Aug 2012 05:23:05 +0000</pubDate>
		<dc:creator>Peter Green</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.adobe.com/agile/?p=74</guid>
		<description><![CDATA[This week I am attending the 2012 Agile conference. Below is a quick recap of some highlights for me today: In the morning, I started out attending a session but found it to be, shall we say, &#8220;uninspiring&#8221;, for me. &#8230; <a href="http://blogs.adobe.com/agile/2012/08/14/agile-2012-day-1-leadership-agility/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://blogs.adobe.com/agile/2012/08/14/agile-2012-day-1-leadership-agility/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>What got you here won&#8217;t get you there</title>
		<link>http://blogs.adobe.com/agile/2012/07/23/what-got-you-here-wont-get-you-there/</link>
		<comments>http://blogs.adobe.com/agile/2012/07/23/what-got-you-here-wont-get-you-there/#comments</comments>
		<pubDate>Mon, 23 Jul 2012 23:05:32 +0000</pubDate>
		<dc:creator>Peter Green</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Scrum master]]></category>

		<guid isPermaLink="false">http://blogs.adobe.com/agile/?p=71</guid>
		<description><![CDATA[The famous quote that is the title of this post typically refers to how an individual&#8217;s approach needs to change as they move into management and then executive leadership. I like to think of it in a broader context. In &#8230; <a href="http://blogs.adobe.com/agile/2012/07/23/what-got-you-here-wont-get-you-there/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://blogs.adobe.com/agile/2012/07/23/what-got-you-here-wont-get-you-there/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Does every item in the product backlog require a User Story?</title>
		<link>http://blogs.adobe.com/agile/2012/06/20/does-every-item-in-the-product-backlog-require-a-user-story/</link>
		<comments>http://blogs.adobe.com/agile/2012/06/20/does-every-item-in-the-product-backlog-require-a-user-story/#comments</comments>
		<pubDate>Wed, 20 Jun 2012 22:02:21 +0000</pubDate>
		<dc:creator>Peter Green</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Product Backlog]]></category>
		<category><![CDATA[User Story]]></category>

		<guid isPermaLink="false">http://blogs.adobe.com/agile/?p=64</guid>
		<description><![CDATA[At a recent workshop on agile requirements, I was surprised by the number of attendees who had been told that EVERYTHING in their product backlog had to be written in the form of a user story, and specifically in the &#8230; <a href="http://blogs.adobe.com/agile/2012/06/20/does-every-item-in-the-product-backlog-require-a-user-story/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://blogs.adobe.com/agile/2012/06/20/does-every-item-in-the-product-backlog-require-a-user-story/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Measuring the success of an agile adoption</title>
		<link>http://blogs.adobe.com/agile/2012/06/08/measuring-the-success-of-an-agile-adoption/</link>
		<comments>http://blogs.adobe.com/agile/2012/06/08/measuring-the-success-of-an-agile-adoption/#comments</comments>
		<pubDate>Fri, 08 Jun 2012 06:41:53 +0000</pubDate>
		<dc:creator>Peter Green</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.adobe.com/agile/?p=57</guid>
		<description><![CDATA[Over the past several years scrum has grown to become the most commonly used product development method at Adobe Systems. Large desktop software products like Premiere Pro and After Effects, Platform tools like Adobe AIR, and Software as a Service &#8230; <a href="http://blogs.adobe.com/agile/2012/06/08/measuring-the-success-of-an-agile-adoption/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://blogs.adobe.com/agile/2012/06/08/measuring-the-success-of-an-agile-adoption/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The benefits of the Daily Scrum part 1: Building Trust</title>
		<link>http://blogs.adobe.com/agile/2012/06/04/the-benefits-of-the-daily-scrum-part-1-building-trust/</link>
		<comments>http://blogs.adobe.com/agile/2012/06/04/the-benefits-of-the-daily-scrum-part-1-building-trust/#comments</comments>
		<pubDate>Mon, 04 Jun 2012 21:27:52 +0000</pubDate>
		<dc:creator>Peter Green</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.adobe.com/agile/?p=54</guid>
		<description><![CDATA[The daily scrum is one of the most recognized parts of the scrum framework. Even for non-scrum teams, it is a simple practice that can bring a lot of benefit to a project. There are lots of great things that &#8230; <a href="http://blogs.adobe.com/agile/2012/06/04/the-benefits-of-the-daily-scrum-part-1-building-trust/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://blogs.adobe.com/agile/2012/06/04/the-benefits-of-the-daily-scrum-part-1-building-trust/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>The Heart, Mind, and Tactics of Agile</title>
		<link>http://blogs.adobe.com/agile/2012/05/11/heart-mind-tactis-agile/</link>
		<comments>http://blogs.adobe.com/agile/2012/05/11/heart-mind-tactis-agile/#comments</comments>
		<pubDate>Fri, 11 May 2012 18:27:18 +0000</pubDate>
		<dc:creator>Peter Green</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.adobe.com/agile/?p=12</guid>
		<description><![CDATA[At the Scrum Gathering in Atlanta this week, my friend Petri Heiramo (@pheiramo) and I were discussing the different agile frameworks, how they were similar and how they were different, and which parts of those frameworks were most important to &#8230; <a href="http://blogs.adobe.com/agile/2012/05/11/heart-mind-tactis-agile/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://blogs.adobe.com/agile/2012/05/11/heart-mind-tactis-agile/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Time, Priorities, and Innovation</title>
		<link>http://blogs.adobe.com/agile/2012/05/04/time-priorities-and-innovation/</link>
		<comments>http://blogs.adobe.com/agile/2012/05/04/time-priorities-and-innovation/#comments</comments>
		<pubDate>Fri, 04 May 2012 04:46:24 +0000</pubDate>
		<dc:creator>Peter Green</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.adobe.com/agile/?p=7</guid>
		<description><![CDATA[Does your team constantly feel under the gun to deliver more stuff faster? Are you often told that &#8220;these features HAVE to be in by the deadline&#8221; (or it will trigger the apocalypse, I presume). Oh, and by the way, &#8230; <a href="http://blogs.adobe.com/agile/2012/05/04/time-priorities-and-innovation/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://blogs.adobe.com/agile/2012/05/04/time-priorities-and-innovation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
