Our IT Service

Service IT Service MVP

Are you a CTO or a projet lead in charge of software developments in your company? Then this page is for you.

What happened in IT services in the 1980s-1990s?

Companies used to sell lines of code

Any industry needs to sell something in a way of its choosing, and for a while people tried to sell lines of code as their currency in exchange for money, following the idea that it’s what they were producing anyway, so why not put a price on them and sell them directly?

The flaw of this plan appeared gradually, as more and more companies were less and less focused on what was actually delivered, so long as it was delivered and making lots of money. So developers started to generate more and more lines of bloated code for less and less value created for the company, meaning that features would convert with time into more and more lines of code, hence pushing the prices up and the service quality of this industry down.

So what was the answer of the IT services industry?

What happened in IT services in the 2000s-2010s?

Companies used to sell hours of work

This issue of the previous decades was fixed by the introduction in the early 2000s of agility, counting time and calculating efficiency in order to prevent developers from overselling bloated source code. This solution kind of worked, for a while anyway, and IT services companies were efficient again.

Then of course developers found another trick in this new situation in order to continue to oversell:

  • when lines of code were sold, they were out of reach from the client and in the hands of the contractor, hence bloating the lines of code generated
  • when time of work was sold, time was out of reach from the client and in the hands of the contractor, hence bloating the time spent on every ticket

So we were back to square one: the IT service quality went down again. So what answer for the 2020s-2030s?

What solution for the future?

Companies can sell tickets, or features, or points of difficulty

Changing the contracts from selling hours into selling tickets or features or points of difficulty is a minuscule change, and yet it achieves everything:

  • because tickets are in the hands of the client, they’re not in the hands of the contractors, so now it’s impossible for them to bloat anything
  • now a client can compare the efficiency of different companies, and challenge them
  • now a client can price his project with great confidence, and move the burden of bug fixes onto the contractor, so out of his way

Calculate your software development costs

By answering those 4 questions you will know how much does adding one feature into your product cost in your company.

- OR -
- OR -

Assuming there are:

  • 220 days of effective work per worker per year
    • excluding holidays & bank holidays
    • excluding sick days
  • -25% from gross to net, +33% from net to gross
  • 10 Fibonacci points per feature
  • +50% from gross to total company cost
    +100% from net to total company cost
    (including HR, accountancy, rent, etc...)
Then

In your company, on average:

  • a developer outputs tickets per day of work
  • a developer takes days to output a ticket
  • your cost per ticket is € gross
  • your cost per feature is € net
  • your total company cost per feature is €
the terms of use of this service

Scenarios

A team of 5 consisting of: 1 backend engineer, 1 frontend engineer, 1 data engineer, 1 infrastructure specialist, 1 project chief; who individually reach an average of 1 ticket per day per developer, will collectively accomplish (for a year of 220 days of work) 220 tickets per trimester, because the project chief will not code so that only 4 persons in the 5 persons team will contribute to the delivery speed, and a trimester being a fourth of the year implies that you need 4 engineers to accomplish 1 year’s worth of work in a quarter, which is 3 months.

Because of the presence of a project chief in a 5 persons’ team, the average delivery speed is 0.8 tickets per person (a fifth of the developer’s average).

In such a team, if the average salary per person is: