Testing and Costing
How Much and Will it Work?
Wernher von Braun said “One test is worth a thousand expert opinions.” EPPORA supports the mapping of each terminal requirement to test cases verifying the functionality, diagnostic and performance of each terminal requirement.
Estimating costs has been like throwing darts at a board that is moving randomly in all directions. We have all heard of the projects that were supposed to cost X yet the final cost were X quadrupled. What is needed is a new method for estimating costs that organizations can depend on and with which the individual requirement costs can readily be determined. The reasons costs help contribute to project portfolio failures is that their very inaccuracy causes organizations to make bad decisions because of faulty information. If we knew what a project would actually cost, we would often never implement the project, or in the reverse, if we knew that we could implement a project for significantly less than what was estimated, it would often make sense to move forward and implement the project.
As there is no purpose conducting a project without thoroughly testing all of its requirements, EPPORA helps assure that every requirement is tested. In EPPORA a Project Manager, Business Analyst and/or Project Portfolio Manager links each terminal requirement to whatever test cases are needed to fully verify the requirement’s functionality.
Executives are continuously fighting budgets and need accurate project-cost estimation in a timely manner. EPPORA supports them by determining the cost of any project feature, as well as the cost of the entire project.
EPPORA cost estimations are based on the fact that what a project is all about are the requirements. EPPORA links each terminal requirement to the appropriate project tasks needed for their implementation to determine the cost of every project feature.