Estimation Considerations: Technical Proof of Concept |
Relationships
Related Elements | Technical Proof of Concept
Main Description
Due to the wide range of activities that may be needed to develop a Technical Proof of Concept, generalized estimating guidelines cannot be given. There are however many parallels between developing a Technical Proof of Concept and testing. Although the rigors of full system testing are not appropriate for a Technical Proof of Concept, many of the considerations that apply in that case should be considered when estimating the overall costs of a Technical Proof of Concept: 1. Time to build and debug test scripts 2. Time to generate test data 3. Time to find and customize hardware and software 4. Time to execute tests 5. Time to analyze results 6. Time to document conclusions
© Copyright IBM Corp. 1987, 2009. All Rights Reserved.