<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Agile Dossier » Julia Salem</title>
	
	<link>http://www.agiledossier.com</link>
	<description>Essays on Agile, Product Management, Teams, Trends and more</description>
	<lastBuildDate>Mon, 25 Feb 2013 13:42:50 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/AgileDossierJuliaSalem" /><feedburner:info uri="agiledossierjuliasalem" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>Agile Works for Web UX</title>
		<link>http://feedproxy.google.com/~r/AgileDossierJuliaSalem/~3/6qyPHB7ZFhs/agile-works-for-web-ux</link>
		<comments>http://www.agiledossier.com/agile-works-for-web-ux#comments</comments>
		<pubDate>Mon, 26 Mar 2012 02:54:33 +0000</pubDate>
		<dc:creator>agilegeneralist</dc:creator>
				<category><![CDATA[agile]]></category>
		<category><![CDATA[Customer Experience]]></category>
		<category><![CDATA[Julia Salem]]></category>
		<category><![CDATA[Product Manager]]></category>
		<category><![CDATA[Product Owner]]></category>
		<category><![CDATA[Trends in Agile Space]]></category>
		<category><![CDATA[UX]]></category>
		<category><![CDATA[Agile and UX]]></category>
		<category><![CDATA[agile product development]]></category>
		<category><![CDATA[Product Success]]></category>

		<guid isPermaLink="false">http://www.agiledossier.com/?p=459</guid>
		<description><![CDATA[by Julia Salem &#60;re-posted from Oxford Technology Ventures blog with due permission&#62; Agile works well for products that need continuous improvement, but it could be hard to adapt to a new development process without taking time to adjust the process while people are learning. Here are a several reasons why Agile can work for your UX team. Direct [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.agiledossier.com%2Fagile-works-for-web-ux"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.agiledossier.com%2Fagile-works-for-web-ux&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p><em>by</em> <strong><a title="Contributors" href="http://www.agiledossier.com/contributors">Julia Salem</a></strong></p>
<p>&lt;re-posted from Oxford Technology Ventures <a href="http://oxfordtechnologyventures.com/agile-works-web-ux/" target="_blank">blog </a>with due permission&gt;</p>
<p>Agile works well for products that need continuous improvement, but it could be hard to adapt to a new development process without taking time to adjust the process while people are learning. Here are a several reasons why Agile can work for your UX team.</p>
<p><span id="more-459"></span></p>
<p><strong>Direct Access to Developers—</strong>More opportunities to meet with the developer because Agile encourages more communication.</p>
<p><strong>See Your Work in Action Sooner—</strong>See the project come together as it’s being built and catch any issues within days rather than weeks.</p>
<p><strong>Agile Requirements Work for the Team—</strong>As a group, the team agrees on how aspects of  the project will come together.</p>
<p><strong>If the First Pass Doesn’t Work, You Won’t Be Stuck—</strong>Agile allows you to catch mistakes and failures quicker and propose a fix in the next iteration.</p>
<p><strong>Progress Can Be Seen Almost Immediately—</strong>No longer do you have to wait for the whole product to be built before you can test it out.</p>
<p><strong>80-hour Workweeks Are Gone—</strong>By wasting less time by only doing what is important in the project, you and your employees can almost cut your workweek in half.</p>
<p><strong>Your Voice Is Heard—</strong>You get to talk directly with the developers to advocate in the process of building the product.</p>
<p><em>Source: <a href="http://www.usabilitycounts.com/2009/03/30/reasons-why-agile-and-scrum-works-for-web-user-experience/" target="_blank">usabilitycounts</a></em></p>
<h2></h2>
<img src="http://feeds.feedburner.com/~r/AgileDossierJuliaSalem/~4/6qyPHB7ZFhs" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.agiledossier.com/agile-works-for-web-ux/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.agiledossier.com/agile-works-for-web-ux</feedburner:origLink></item>
	</channel>
</rss>
