The Speed of Software Development

I preach IT solutions and tools that bring quick wins and have a relatively short implementation cycle.

At the same time, projects for the implementation of such solutions go through generally accepted stages:

  • Consultations, identification of user needs, assessment of the scope of the project, coordination of deadlines and acceptance criteria.
  • Coordination of business requirements, functional specifications, formats of intersystem interaction with other IT solutions of the customer.
  • Development, testing and documentation.
  • User testing, training, acceptance.

What ensures the speed of implementation? - the speed of implementation is ensured by reducing the level of bureaucracy, as well as due to the fact that there is no need to pass the baton between a business analyst, a system analyst, a programmer, a tester, there is no effect of a broken phone.

When is the division of labor beneficial? - when automation tasks are of the same type, they flow one after another, and each IT specialist works quickly, clearly and efficiently, as on a conveyor belt.

But it usually turns out that these projects are very different from each other. It is impossible to make a conveyor belt. As soon as it becomes possible to make a conveyor, someone very smart comes up with the idea to automate the conveyor.

And I get it, the approach is not conveyor, but boutique.

It follows from this that it makes sense to contact me only when your task is atypical. I will not do a typical task cheaper than it is done on the assembly line.

But I have ready-made services, this is exactly what you can call an automated pipeline. And I can provide ready-made services cheaper than large companies, because my costs are lower. I don't have bosses who take the lion's share of the profits and take time away from programmers.

My professionalism alone is not enough for a successful timely implementation. A quick reaction and good motivation on the part of the customer are also necessary.

My solutions can be successfully implemented in strategic IT projects, which will allow long-term projects to maintain the trust of the sponsor, customers and other stakeholders.