Fixed Price
This approach allows minimization of risks resulting from inefficient allocation of time and funds as it is based on strictly defined terms.
The strengths of this approach are:
- strict differentiation of obligations for both sides;
- definition of terms and costs of the software product at the initial stage of cooperation.
The weakness of this approach is absence of a possibility to make alterations that can influence both the terms of the product release and its final costs. However, this drawback should not be viewed as an obstacle for building the developer-customer relationships. This approach allows for breaking the development into fixed spans of time, the so called sprints, and thus provides both sides the possibility of bringing in unplanned changes and making cost estimations at each stage of the project.
Building relations along the lines of the “Fixed Price – Fixed Time” model is most beneficial:
- for customers interested in getting the final product without being engaged in the details of its development process;
- for small projects that have a pre-planned specified volume of work;
- at the initial stage, for projects having an innovative constituent which cannot be exactly appraised and is subject to being divided into smaller components;
- at the initial stage, for projects not having clear scopes and requirements which can be exactly appraised but are subject to clarification in the process of development.
Many customers prefer to use a mixed approach to software development. The “Fixed Price – Fixed Time” model is used in the initial stages of collaboration, when both parties try to determine the key points of project realization. As soon as all key questions have been answered, we can turn to the models with wider possibilities in the plane of collaboration: outstaffing and outsourcing.