<?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: Of kickoffs and walk throughs</title>
	<atom:link href="http://www.fuzzylizard.com/archives/2008/12/02/985/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fuzzylizard.com/archives/2008/12/02/985/</link>
	<description>Web development and design with a little VFX thrown in for fun</description>
	<lastBuildDate>Fri, 14 Jan 2011 22:45:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Jeff Santini</title>
		<link>http://www.fuzzylizard.com/archives/2008/12/02/985/comment-page-1/#comment-31185</link>
		<dc:creator>Jeff Santini</dc:creator>
		<pubDate>Tue, 02 Dec 2008 15:00:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/?p=985#comment-31185</guid>
		<description>I spent some time in a project where I seemed to see the things that you are experiencing.  In the situation I was in the problem stemmed from the people who are required at these meetings having other goals that were not aligned with the day to day goals of the development team, and that fact that there were about 30 of us and fundamentally 2 of them.

As I understand, great improvements were realized on this project later, when all the people who are responsible to sign off a story are on the same LITTLE team.  So a team of 60 people can be split and aggregated around a set of related stories.  If all the people responsible for sign off are on the same team of 6-8 ppl I garauntee that the whole implementation process will be smooth.  BAs/QAs/Business ppl will be sitting right next to you and can sign off whenever your heart desires.

On your other theme of trust, I have a great time using technology to implement a business functionality.  I can impress my colleagues(on occasion), and change the existing system according to my understanding, but I give myself no credit for completing a story until a business person tells me it is what they wanted.  I think it not important whether the others trust you to complete the story, it is more important that you recognize your limitations to complete the story until the business person has signed it off.

Hope that is helpful feedback.

Jeff</description>
		<content:encoded><![CDATA[<p>I spent some time in a project where I seemed to see the things that you are experiencing.  In the situation I was in the problem stemmed from the people who are required at these meetings having other goals that were not aligned with the day to day goals of the development team, and that fact that there were about 30 of us and fundamentally 2 of them.</p>
<p>As I understand, great improvements were realized on this project later, when all the people who are responsible to sign off a story are on the same LITTLE team.  So a team of 60 people can be split and aggregated around a set of related stories.  If all the people responsible for sign off are on the same team of 6-8 ppl I garauntee that the whole implementation process will be smooth.  BAs/QAs/Business ppl will be sitting right next to you and can sign off whenever your heart desires.</p>
<p>On your other theme of trust, I have a great time using technology to implement a business functionality.  I can impress my colleagues(on occasion), and change the existing system according to my understanding, but I give myself no credit for completing a story until a business person tells me it is what they wanted.  I think it not important whether the others trust you to complete the story, it is more important that you recognize your limitations to complete the story until the business person has signed it off.</p>
<p>Hope that is helpful feedback.</p>
<p>Jeff</p>
]]></content:encoded>
	</item>
</channel>
</rss>

