Is that magic or craftsmanship?

This is how a customized software is finished on time.

“Danger recognized, danger averted” is the proverbial saying. If you apply this rule to software projects, then it comes down to the early detection of problems. With a project status report, you can determine at any time whether the project is still within the calculated effort. And, as we all know, these have an impact on the schedule and programming costs. The earlier you detect discrepancies, the more time you have for the introduction of effective countermeasures.

Continuously determine the status of a software project.

Once the software development is started, many framework parameters are unchangeable. There is an estimate of the programming effort per request key and also a maximum total budget for programming the software. In most cases, the schedule and the available programming capacities are also already fixed. It is particularly important at this stage to keep a close eye on the project.

For this purpose, an exact database is required. It is best to have an effort estimate with the following information:

  • Request Key
  • Calculated effort in hours

The project status report requires the “% Done” value to be entered. This tells how far the programming task behind the Request Key has been completed. This consideration is independent of the required programming time. It is only about the degree of technical completion. If you maintain this value per request key, then you can easily calculate the equivalent value of completion in hours and the equivalent value of hours not yet completed in Excel. By summing them up, you get the number of hours that reflects the technical functional completion. In the chart to the right, this is 41.8 hours.

Example of a project status report

On the other hand, the programmers should have entered the actual programming time needed in a ticket system or another system suitable for this purpose. In the diagram this is 72 hours. So more time was needed than originally planned. If you form a quotient from the two values and multiply this by the calculated number of hours (in the example: 72/41.8 * 67 = 115.5), then you get a forecast for the hours until the programming is completed.

Contact now

This is a required field
This is a required field
This is a required field
This is a required field