<?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: Fitting UX people into scrum team</title>
	<atom:link href="http://www.dmitriev.com/blog/2009-02-26/fitting-ux-people-into-scrum-team/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dmitriev.com/blog/2009-02-26/fitting-ux-people-into-scrum-team/</link>
	<description>This is a private blog of mine where I share my thoughts, concerns or anything else I care to write about.</description>
	<lastBuildDate>Thu, 20 May 2010 18:01:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Marit Søholt Stokes</title>
		<link>http://www.dmitriev.com/blog/2009-02-26/fitting-ux-people-into-scrum-team/comment-page-1/#comment-5823</link>
		<dc:creator>Marit Søholt Stokes</dc:creator>
		<pubDate>Tue, 26 May 2009 12:08:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.dmitriev.com/blog/2009-02-26/fitting-ux-people-into-scrum-team/#comment-5823</guid>
		<description>Interesting topics and still a lot to do in this area!
IT-projects and contracts - these aspects still needs attention:

1. Goals and requirements for the system/product to be made (all contracts have this)

2. Goals and requirements for the processes to be used (most IT-contracts lack this).
This means lack of the minimum requirements for -
- How to plan, run and manage the project
- Design of how the communication between supplier and customers should be handled
- Roles, responsibilities and authorities
- Good (and flexible enough) QA-processes
- Suppliers&#039;  QA
- Customers&#039; QA!?
- External QA</description>
		<content:encoded><![CDATA[<p>Interesting topics and still a lot to do in this area!<br />
IT-projects and contracts &#8211; these aspects still needs attention:</p>
<p>1. Goals and requirements for the system/product to be made (all contracts have this)</p>
<p>2. Goals and requirements for the processes to be used (most IT-contracts lack this).<br />
This means lack of the minimum requirements for -<br />
- How to plan, run and manage the project<br />
- Design of how the communication between supplier and customers should be handled<br />
- Roles, responsibilities and authorities<br />
- Good (and flexible enough) QA-processes<br />
- Suppliers&#8217;  QA<br />
- Customers&#8217; QA!?<br />
- External QA</p>
]]></content:encoded>
	</item>
</channel>
</rss>
