RE: [AM] payment in agile development

depends on client and style of "doing business"

1) forced fixed bid
Not a good way to build/buy software. But, if necessary, then you make your
best coarse-grained estimates and work the contract as agilely as possible.
I could write a chapter on this, as could other folks on this list.

2) Level of Effort
You just have a fixed rate of spend and allow the client's priorities to
dictate what gets built when.

3) Hybrid
LOE or Time & Material to get basic understanding of application to be
built. Then fix bid the detailed construction.



-- jon



> -----Original Message-----
> From: Daniel Brenner [mailto:[email protected]]
> Sent: Sunday, February 01, 2004 3:39 PM
> To: [email protected]
> Subject: [AM] payment in agile development
>
>
> Hallo,
>
> since I am still at the university (and have no experience with that) I
> am curious to know how a agile project is payed.
>
> In traditional approach there is a requirements freeze and based on
> these requirements, you can calculate the time you need to development
> the appropriate software. But how to do this in agile development? Ok,
> you need to do a requirements freeze here as well but following "embrace
> changes" you can not determine the time which is needed to develope the
> software... (bringing me to another question: does "embrace changes"
> also mean to add new features?)
>
> Thanks in advance,
> - Daniel
>
> 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
--^----------------------------------------------------------------