Proof of Concept

If you're having a hard time nailing down the requirements of an application or the solution to a business problem, we recommend implementing a simplified short-term solution. This is often the most cost-effective way to validate preliminary requirements, since it brings form to an idea, and allows stakeholders to "kick the tires" so to speak.

In the Proof of Concept process, many implementation details can be sidestepped, as the key objective is to validate the key assumptions related to a project, and ensure that all key stakeholders are active participants in the process.

In a nutshell, here is our approach for implementing Proof of Concept applications:

• Identify key risks faced by the project - both business and technological
• Design and create a prototype to test and mitigate these risks, perhaps in multiple iterations
• Document the key assumptions that are embodied in the prototype application
• Document the outcomes of the Proof of Concept process
• Determine a risk management strategy for the project, based upon the lessons learned in the Proof of Concept and the assumptions made in the creation of the prototype application

In many cases, the prototype application can be extended to create the final solution.

But even if the underlying implementation needs to be rewritten, the Proof of Concept application can act as a tangible reference point for the final production system implementation, greatly increasing the likelihood of a successful delivery.