Is it normal for changes to occur during the development process?
Posted: Mon Jan 06, 2025 6:02 am
The most common way to reduce customer costs is to create an MVP. The minimum viable version of the product assumes that the team will be busy developing only the basic functions. Everything else is finalized after the release and feedback from users.
This option is often used by startup models to test the hypothesis of whether an IT solution will be in demand. Launching an MVP requires a minimum budget and time frame, and any brazil whatsapp phone number shortcomings of the initial ideas can be easily corrected later with product support.
Another method to reduce the cost of a project is to develop it on the basis of a CMS. With this approach, the amount of work of IT specialists is reduced, because the solution is not built “from scratch”, but on the basis of a template designer.
This way, the customer gets the necessary tools at lower costs and timeframes. This method is especially suitable for those who are bringing a solution to the market for the first time - when the product is not yet profitable, its owner most often does not yet make sense to invest in developing his own solution.
However, there are limitations here too. For example, difficulties in implementing functionality not provided for in the CMS or the product's dependence on a cloud solution - if it stops working, then the customer's platform will too.
Following the blocking and departure of foreign IT companies from the Russian market, many companies have already lost access to their websites or were forced to transfer them to alternative platforms due to the blocking of the Wix , Ecwid and Weebly constructors .
Read on the topic: Custom development or boxed solution: what is important to remember when choosing
Innovations in the creation of a digital product are a typical practice that is often encountered in IT projects. New information and needs may arise both from the customer and from external factors.
For example, if the initial plan was to integrate one payment system, but in the end it was decided to make another one with a different API, the planned timeframe and budget may differ significantly from the initial estimate.
However, situations where no changes occur, but the cost increases and the release dates are shifted, are not normal. If the reason for the changes is that some work was not initially taken into account in the estimate, the costs should be borne by the contractor, or he is obliged to notify the client about this and come to a compromise with him.
This option is often used by startup models to test the hypothesis of whether an IT solution will be in demand. Launching an MVP requires a minimum budget and time frame, and any brazil whatsapp phone number shortcomings of the initial ideas can be easily corrected later with product support.
Another method to reduce the cost of a project is to develop it on the basis of a CMS. With this approach, the amount of work of IT specialists is reduced, because the solution is not built “from scratch”, but on the basis of a template designer.
This way, the customer gets the necessary tools at lower costs and timeframes. This method is especially suitable for those who are bringing a solution to the market for the first time - when the product is not yet profitable, its owner most often does not yet make sense to invest in developing his own solution.
However, there are limitations here too. For example, difficulties in implementing functionality not provided for in the CMS or the product's dependence on a cloud solution - if it stops working, then the customer's platform will too.
Following the blocking and departure of foreign IT companies from the Russian market, many companies have already lost access to their websites or were forced to transfer them to alternative platforms due to the blocking of the Wix , Ecwid and Weebly constructors .
Read on the topic: Custom development or boxed solution: what is important to remember when choosing
Innovations in the creation of a digital product are a typical practice that is often encountered in IT projects. New information and needs may arise both from the customer and from external factors.
For example, if the initial plan was to integrate one payment system, but in the end it was decided to make another one with a different API, the planned timeframe and budget may differ significantly from the initial estimate.
However, situations where no changes occur, but the cost increases and the release dates are shifted, are not normal. If the reason for the changes is that some work was not initially taken into account in the estimate, the costs should be borne by the contractor, or he is obliged to notify the client about this and come to a compromise with him.