PROOF OF CONCEPT
“Proof of Concept” is very similar to a “Change Request” but can differ in the depth of execution, presence of QS and more
When is it required to perform Proof of Concept in Software Development?
One of the moments to perform Proof of Concept is when there are doubts about having enough knowledge and experience with new technologies, where there is a need to explore the field in more depth, discover latest developments in software libraries.
On the other hand, when there is enough experience and confidence there could be a need to:
- make sure that the chosen method of operation is correct and the software can withstand the load, test its performance
- make sure that the task execution is possible at all within predefined limitations
- define limiting conditions for given task, explore what will happen if conditions are met
- identify execution details or acquire a software prototype
- investigate which technologies are required and are optimal for task execution
What are the main limiting conditions to perform a Proof of Concept?
Those are time, budget and technologies.
As a rule of thumb we first do the research if something similar was already developed. The existing experience is studied and summarised, conditions necessary for execution are identified, and then we perform the Software Development Proof of Concept. All obstacles and problems during Proof of Concept executions are logged to be analised at the end and presented to the client.