You are 100% right Laura; by "fixed rate" I meant a fixed rate tied to (non-explicit) fixed deliverables, with the variable being hours/effort.<div><br></div><div>If the iron triangle is understood, then yes, the cost can be fixed, of course.<br>
<br><div class="gmail_quote">On Thu, Nov 11, 2010 at 7:05 PM, Laura <span dir="ltr"><<a href="mailto:pinglaura@gmail.com">pinglaura@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Nov 11, 2010, at 2:50 PM, Victor Kane wrote:<br>
<br>
> Fixed rate budgets are a waste of time for everyone first and foremost because they posit the waterfall approach to software development;<br>
<br>
</div>I do not see this connection. Fixed budget can work as part of the iron triangle in agile. You work against the backlog until the budget is spent. It's fixed scope that I see as inherently waterfall. Or do I misunderstand what you are saying?<br>
<font color="#888888"><br>
Laura<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
consulting mailing list<br>
<a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
<a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
</div></div></blockquote></div><br></div>