<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Kommentare zu: Managing user expectations on software projects - Lessons from the trenches (Petter, in press)</title>
	<link>http://blog.budzier.com/2008/10/07/managing-user-expectations-on-software-projects-lessons-from-the-trenches-petter-in-press/</link>
	<description>Summaries of Project Management Research Studies</description>
	<pubDate>Thu, 09 Feb 2012 10:30:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>Von: admin</title>
		<link>http://blog.budzier.com/2008/10/07/managing-user-expectations-on-software-projects-lessons-from-the-trenches-petter-in-press/#comment-65</link>
		<author>admin</author>
		<pubDate>Fri, 10 Oct 2008 02:21:50 +0000</pubDate>
		<guid>http://blog.budzier.com/2008/10/07/managing-user-expectations-on-software-projects-lessons-from-the-trenches-petter-in-press/#comment-65</guid>
		<description>Well, I am a big follower of continuous QfD for RuP/agile project developments. While I do see that smaller projects can easily live by a good prototyping approach, not much is gained if you do large scale projects (ERPs, core business systems). 
Personally I think the best approach is to have mixed demand-supply side teams, at least for the specification part. 
If that is done properly, call it super-user and IT business analyst, this can be a fruitful collaboration mode. Which of course manages user expectations almost automatically, throughout the entire lifecycle of the project.</description>
		<content:encoded><![CDATA[<p>Well, I am a big follower of continuous QfD for RuP/agile project developments. While I do see that smaller projects can easily live by a good prototyping approach, not much is gained if you do large scale projects (ERPs, core business systems).<br />
Personally I think the best approach is to have mixed demand-supply side teams, at least for the specification part.<br />
If that is done properly, call it super-user and IT business analyst, this can be a fruitful collaboration mode. Which of course manages user expectations almost automatically, throughout the entire lifecycle of the project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: PM Hut</title>
		<link>http://blog.budzier.com/2008/10/07/managing-user-expectations-on-software-projects-lessons-from-the-trenches-petter-in-press/#comment-57</link>
		<author>PM Hut</author>
		<pubDate>Tue, 07 Oct 2008 18:54:01 +0000</pubDate>
		<guid>http://blog.budzier.com/2008/10/07/managing-user-expectations-on-software-projects-lessons-from-the-trenches-petter-in-press/#comment-57</guid>
		<description>Is the user involvement during the whole project (Agile) or just in the requirements phase?

In Software Projects, whether you're using Agile or not, the best way is to properly gather requirements and ask all the possible questions (if you don't ask, the client won't answer). Software Projects are always risky because the clients typically don't know exactly what they want.

I have an excellent document about &lt;a href='http://www.pmhut.com/the-technical-requirements-specification-trs-in-web-projects' rel="nofollow"&gt;The Technical Requirements Specification (TRS) in Web Projects&lt;/a&gt;. I think it greatly relates to your article.

Still, going Agile is probably the best way in Software Projects.</description>
		<content:encoded><![CDATA[<p>Is the user involvement during the whole project (Agile) or just in the requirements phase?</p>
<p>In Software Projects, whether you&#8217;re using Agile or not, the best way is to properly gather requirements and ask all the possible questions (if you don&#8217;t ask, the client won&#8217;t answer). Software Projects are always risky because the clients typically don&#8217;t know exactly what they want.</p>
<p>I have an excellent document about <a href='http://www.pmhut.com/the-technical-requirements-specification-trs-in-web-projects' rel="nofollow">The Technical Requirements Specification (TRS) in Web Projects</a>. I think it greatly relates to your article.</p>
<p>Still, going Agile is probably the best way in Software Projects.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: topwebbusinesses &#187; Blog Archive &#187; Managing user expectations on software projects - Lessons from the &#8230;</title>
		<link>http://blog.budzier.com/2008/10/07/managing-user-expectations-on-software-projects-lessons-from-the-trenches-petter-in-press/#comment-54</link>
		<author>topwebbusinesses &#187; Blog Archive &#187; Managing user expectations on software projects - Lessons from the &#8230;</author>
		<pubDate>Tue, 07 Oct 2008 15:25:53 +0000</pubDate>
		<guid>http://blog.budzier.com/2008/10/07/managing-user-expectations-on-software-projects-lessons-from-the-trenches-petter-in-press/#comment-54</guid>
		<description>[...] Original Alex [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Original Alex [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

