When you only see the tip of the iceberg, or why to avoid change requests during web development

[suchona.kani.z]

At AITOM, we refer to these works as “ Change requests ” – these are tasks and assignments that are carried out beyond the scope of the project assignment and are therefore not included in the order or contract. We have developed detailed assignments for the entire project and we stick to them. And above all, according to this assignment, we have set a work schedule so that we can meet it.

How does the coder see the change request?
Modern websites are deeply interconnected. A seemingly small change, such as moving a logo, can be very demanding in terms of code . And if the website is optimized for mobile devices, i.e. responsive, these changes are even more challenging.

You can imagine such a website as a house. Imagine that you choose a standard house from a catalog and start building. When you have the foundation ready, you decide that you only want a very small cash app database change – to expand one room by half a meter. That is a negligible difference for a house, right? But you need to take into account the possible impact on the statics, recalculate the material, redraw the project and, of course, also redo the already finished foundation. From the user's point of view, a small change in the specification can then mean a fundamental difference in the price and implementation date.

What the user ultimately sees is just the tip of the iceberg . It's not enough to just modify the code, you also need to test and check everything on all possible devices.

What does a change request look like?

Kodér's Glacier
Let's show you the individual steps of how we handle change requests at AITOM using examples. Every quality development agency has an established procedure for transferring all code changes to the final presentation so that there can be no errors, downtime, etc. Let's imagine model examples:

Example 1: Editing a button


Step Time-
consuming
The coder studies the assignment and finds the optimal solution 10 minutes
Creating a feature branch (basically a copy of the code) 5 minutes
Running a copy of the pages on a local server on your computer 10 minutes
Making the appropriate adjustment 5 minutes
Testing the change on all necessary devices 30 minutes
Upload changes back to the production server 10 minutes
TOTAL 70 minutes
Example 2: Adding more items and a slider effect.