RE: [AM] payment in agile development

1. Because the first iteration bears startup costs.
2. Iterations tend to vary between 1 week and 1 month.
3. Most clients I am familiar with do not like to deal with billing periods shorter than a month anyway which is longer than iterations generally are.
 
-----Original Message----- 
From: Ashley McNeile [mailto:[email protected]] 
Sent: Mon 2/2/2004 5:06 PM 
To: [email protected] 
Cc: 
Subject: Re: [AM] payment in agile development



	> I did it this way, and it worked well.
	>
	>   * The first two iterations are a fixed price
	>   * Each iteration after that is a fixed price
	>   * The client is allowed to cancel the project at any time after the
	> end of an iteration, except the end of the first iteration
	
	That seems a nice approach. I would be interested to know:
	
	1. Why the rule about no cancellation after the first iteration?
	2. Can you give use any approximate figure (or range) for the size of an
	iteration, say in man-days?
	3. How did the client(s) react to the rule that mid iteration cancellation
	is not allowed?  Presumably, they can cancel the work, but have to pay you
	the fixed price for the iteration anyway? I would imagine that this could be
	difficult to get past the client's Legal and Contracts people.
	
	Thanks
	Ashley
	
	For more information about AM, visit the Agile Modeling Home Page at www.agilemodeling.com
	
	
	
	


For more information about AM, visit the Agile Modeling Home Page at www.agilemodeling.com
--^----------------------------------------------------------------
This email was sent to: [email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrKDA.bWnbtk.Z2NtYS1h
Or send an email to: [email protected]

TOPICA - Start your own email discussion group. FREE!
http://www.topica.com/partner/tag02/create/index2.html
--^----------------------------------------------------------------