November 2017
« Aug    


There are many reasons why software projects often fail to deliver their promised value, but one of the primary causes is that the project owners do not understand software. They understand the project process and its tools – specifications, budgets, schedules, staffing, subcontractors, etcetera – but they cannot read code and therefore have to accept a lot of what they receive on faith. While faith is good, testing is better.

Testing is one of the best tools managers have for verifying the results of a software project – and not just upon delivery. Testing should be planned into the project from the start, and the project software team should be able to provide test feedback as the project progresses.

The initial test guidelines can be simple, not least because their goal is verification that the product delivers what was promised in the project’s specifications. The project software development team should preferably include test staff – and always include a test plan.

There are many different types of testing, but the general concepts are not very technical – and well worth the time of anyone responsible for a software project. In this article, Dan Mygind discusses software testing with Brian Nielsen, Associate Professor at Aalborg University in Denmark.

For more details about the terms they refer to, visit

Leave a Reply




You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>