As the name suggests the customer will be charged based on the resources utilized and the time spent for the project.
This is the best method for implementing projects which are longer in duration and where the project specifications evolve as the implementation progresses. Large scale and complex projects are best executed using this approach.
The objective of any software project is to find a solution to a business problem. This model allows the software service provider and the client together to arrive at that solution. The best suitable solution possible to resolve the business problem can be delivered to the client. The focus is more on the solution and the specifications evolve to fit the business solution.
This model has a start point from various stages viz. post specification, pre-specification, post architectural design etc. A comprehensive scenario will involve problem definition, solution definition, research, business analysis, specifications, visual mapping, architectural design, documentation, coding, change management, testing, roll out and support.
The effort estimation for all the elements for all stages at the beginning of the project is usually involved and complex. You and Us prioritize and scope each element. ERC prepares an effort estimate for that stage, defines the promised deliverables for that element and states the assumptions involved.
The implementation of each element is embarked upon with a provision for change management and assumption updates. The effort is charged on a pre-agreed hourly or a monthly rate based on the quality of resource engaged. ERC and Client agree on a change management practice and provide room for the same.
ERC’s effective project management ensures that effort is estimated and implemented in an effective and controlled fashion to reduce time and cost overruns.
This process is repeated for each of the elements until the solution is delivered in its entirety
This mode of engagement is ideally suited for developing known and well understood solutions with relatively low to medium levels of complexity. This model is well suited for projects that have clear specification documents and sufficient amount of detail so that all risks are identified and all assumptions are explicit.
These projects typically leave little scope for changes and additions during the project execution. As a customer dealing with this model, you would be a knowledgeable person in the business domain and will have an understanding of the software development process. This model's success hinges on the active cooperation of the client. It assumes that the client will provide timely and relevant feedback & decisions.
You will provide a detailed specification document to NDPL. NDPL along with you will review the specifications and ensure that all assumptions, details are made explicit. NDPL will prepare an effort analysis and propose a fixed price and fixed time frame for the project execution. NDPL also will highlight the scope of change and possible risks during the execution phase.
You and ERC will enter to in an agreement that covers visual aspects, documentation, application design, testing, support period, change management, communication protocols, milestones, timelines and commercial details. The project is executed as per the agreement.
We can help you in evolving the specifications for the particular project at a fee. ERC’s business analyst discusses the project in detail and prepares a low level specification document laying bare the various elements of the project.
As the name suggests everything is fixed in this model. There is limited risk to both parties as the scope, price and timelines are fixed in this model. The advantage of this model is the mitigated risk that it offers to the stakeholders. This risk reduction is however based on the quality effort that precedes the agreement phase. The higher the detailing, lower are the surprises. ERC offers business consulting services during the specification stage.
There will be minimal scope to implement any new ideas or new requirements during the execution of the project. The application will be designed based on mutually agreed specifications. This obviously limits the changes that can be included during the execution of the project. This is a good model for all projects where the specifications of the project / product are clear and well documented with all aspects of estimation and change management mutually agreed upon.
See how we are listed on the 1st page of GOOGLE for some of the below keywords shown below