Set the Timelines for the POC and Ensure That the Implementation Activities Are Done Within the Scope of the POC

 <  Day Day Up  >  

Martin and his team had decided to let the vendors have 5 days to set up their infrastructure and get 10 POC members deployed. Once the POC was deployed, the members would then run the solution for 2 weeks. The vendors ' solutions would run in parallel on different members ' machines in each represented technology group .

Jason looked at the calendar and sighed. The deadline for digital certificates was quickly approaching. If he was to make his deadline, he would need to limit the POC. Jason had previously selected a vendor and asked the vendor to install a team in 2 days. Subsequent to that, the POC would last 10 days.


The Methodology

When deciding how long to run a POC, there is a general feeling that longer is better. The timeframe needs to be long enough to validate the technology, but not so long as to have the POC stagnate. Generally, 30 “45 days is long enough to know if the technology being proposed will meet the success criteria of the project. By keeping it short, the following benefits can be seen:

  • Keeps the POC focused ” By keeping the POC limited in its timeframe, the POC team must focus on the goals and success criteria. Letting the POC run on will tend to encourage experimentation. The members of the pilot become bored with what has been accomplished and may start trying things that are not yet ready to use. If this causes failures, the failures may be incorrectly interpreted by others outside the project as failures of the POC.

  • Builds on momentum ” If the POC is successful, there will be excitement and momentum created. This in turn will create energy and drive, which can then be leveraged to kick-start the pilot phase of the project.

If the POC is failing, keeping it short allows the failure to be completed quickly and then used as a learning tool. Since there will not be the frustration felt from using a product that does not meet the company's needs, additional vendor products can be brought in for evaluation.

 <  Day Day Up  >  


Biometrics for Network Security
Biometrics for Network Security (Prentice Hall Series in Computer Networking and Distributed)
ISBN: 0131015494
EAN: 2147483647
Year: 2003
Pages: 123
Authors: Paul Reid

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net