Are you or your IT Department considering a Proof of Concept (POC) or Proof of Technology (POT)? If so, here are a few things to think about:

1) What do you need the vendor to provide in the Proof of Concept / Proof of Technology?

2) Do you have concrete business requirements to ensure that you’re measuring the Proof of Concept / Proof of Technology correctly? If not, it’s important to ensure that both you and the vendor understand the requirements for the Proof of Concept / Proof of Technology.

3) Do you need to use a legal agreement for the Proof of Concept / Proof of Technology? If you’re unsure, check with your contract management, procurement or legal team and ask them. In fact, they may need an Agreement in place before the Proof of Concept / Proof of Technology begins. Ask them ahead of time to ensure that this is included in your project planning, as Proof of Concept / Proof of Technology engagements can take anywhere from a few days to a few months. In addition, the contracting effort may take a few months itself if your legal team and the vendor don’t agree on the contract terms.

4) Are you evaluating a cloud solution in the Proof of Concept / Proof of Technology? Some vendors may tell you that a Proof of Concept / Proof of Technology isn’t feasible for a cloud solution, but this isn’t correct. You can evaluate a cloud solution with a Proof of Concept / Proof of Technology.

Here are a few articles that will assist you as you consider the Proof of Concept / Proof of Technology:

- 10 Do’s and Don’ts for Running Proof of Concept Projects in the Cloud
- How to do a Proof of Concept in the Cloud
- POC, Prototype, or Pilot? When and Why
- Proof of Concept, Prototype, Pilot, Agile…Confused?
- Does a Proof of Concept Really Prove Anything?

Reblogged this on Project Management in Practice.

Thank you for reblogging my post! Really appreciate it and enjoy your blog as well!

Not a problem. A slightly different take to POC, which was very well put together.

Pingback: Is it a Software Evaluation or a Proof of Concept? | the vendor chronicles

Pingback: The Importance of Vendor Risk Assessments | the vendor chronicles