We have a problem…
We must completely change the direction of the project that we are going in – stop the presses! The last thing anyone working on a project wants to hear is that we are stopping what we are doing and reworking the project in a new direction. Ugh, what a waste of time, right?!
Whatever the project is that you are working on, I can guarantee you that there is a major aspect to keep in mind – budget. Usually, there are two aspects to consider when it comes to budget: 1. What the project should cost, and 2. The actual cost of the project. Ah, yes, the practical side of the business that many of us tend to forget when we have our blinders on and are working away like mad, only to find out that changes are coming…
Do you know that more than 50% of software costs go to project rework and repairs, and not the original project cost itself? Yes, that’s baffling information to digest when reading it out loud (or inside) to yourself. A large portion of the rework comes after the initial launch of the project when corrections and implementations come up during the testing period. How can we fix these extra project costs?
Fortunately for you, there are a few ways to remove reworking time and extra costs. Integrate your test design into the requirement/overall process of the project, apply model-based technology to functional testing and specification timelines, and invest in test-driven development processes (i.e. incremental development). These methods will not only save on the costs and resources involved but your own sanity if you are lucky!
(Copy: Jordan Rinaldi / illustration: Carlos Ponce)
