How To Run A Proof Of Concept
This topic provides knowledge on running a software Proof of Concept (POC). Please add any best practices, recommendations, guidance and thoughts.
A Proof of concept (POC) is an experiment or pilot project in order to determine feasibility, or a demonstration in principle with the aim of verifying that some concept or solution has practical potential. A proof of concept is typically small and may or may not demonstrate complete system functionality. Evidence deriving from the POC should demonstrate that a design concept, business proposal, or solution, etc. is feasible.
There are two parts to every business. You already have a lot of blood, sweat and tears poured into developing a new technology. Now, you have to sell it. But selling new technology is often easier than it sounds. You need a way to change how customers think about technology and convince them to embrace your new product.
To avoid late or overly costly projects, one must make sure that the vendor knows how to implement the systems. But it is not enough that the vendor knows what to do and how to do it. Without help from the buyer, or ICT, and eventual users, or business, no system can be implemented and deployed successfully.
An example of documentation prepared to support an architectural assessment completed for a small system. This document is a good example of how the methodology can be employed on a project of any scale. Due to the small scale of this project, three documents were combined into this document: Current Situation Assessment, Requirements Definition, and the Proof of Concept evaluation.
I find it hard to understand why anyone would buy enterprise software, let alone BPM software, without going through a Proof-of-Concept (POC). I love POCs. I really do. I find them challenging, I find them exciting, I find them creative... I also believe that they are in the customer's best interests.
In this article series, I will explore the utility, structure, and design of the Proof of Concept through examples, stories and practical advice. I will also attempt to reveal tips and tricks about creating Proof of Concepts that my students and I have discovered over my 15 years of teaching User Experience.
To successfully deploy a Citrix solution, it's important to be aware of how users are interacting with the environment, understand the purpose of the environment, and plan how the environment fits into the support structure. In the course of my 8+ years with Citrix I have seen countless customer environments, and being aware of the items above can make or break your deployment.