Estimates of Fixed-Price Contracts

Hello!.

Recently, I increasingly have to perform. SWAGi. for multiple projects at various stages ( most often on. pre. -. sale. ). And the main problem is that no matter what the contract:. Time. -. Material. or. Fixed. -. Price. usually requires the customer to define project budget. This is, in principle, it is reasonable, since no preliminary data on the budget manager at the customer usually just not able to move the project (even if he manages money).

In the wilds. LESBIAN. came across a small article about the cost estimates in the. Fixed. -. Price. projects:.

http://www. enter-agile. com/2010/10/fixed-price. html? spref = fb. The article carries with it a. only. useful thing to remember is planning any project, regardless of contract type. The idea of ​​a simple and reasonable:.

Judge not modules ( implementation) and functionality ( requirements).

it. really important and very useful as it allows the ' play' with the content (. scope. ) Project as well as. obvious. allows us to show customers ' severity ' of each. features. Although I must say, there are other situations:.

a. Sometimes the need to separate species. of. (eg, development and testing) as they will be performed by various subcontractors and funded from a variety of. budgets.

2. It is often easier to stretch the imagination and develop a plan consisting of a ' modular ' blocks in the decomposition of which make up the deep problems of the type ' to develop a class A' weighing no more than 8-16 hours, because the only way to show the expected duration of the project to the customer, which . Agile. The main thing - do not even try to use this plan in the future! .

Good luck! .