Microsoft Guidelines for SCCM Proof of Concept

Question

Where can I find the Microsoft Guidelines for Microsoft Proof of Concept for SCCM 2012 R2.
Some of the point I remember are as follows:
POC should be done in Lab and not in production.
POC not to be include any specific customization.
At times customers want to include everything specific to their environment which is not possible in limited time we have for POCs (5-10 days). Where can we show them the guidelines for that? All the customizations they have may take 1-2 months to test and
deliver.
They generally say that all customizations must be provided in POC as they are paying for the project. But actually it is Microsoft paying for that. Just want to know how others deal with such situations.

Answer 1

You need to make your costumer understand that a Proof-of-Concept is exactly what it Means - It proves to the customer that this product can deliver what they need. That does not mean that you have to implement every possible feature in ConfigMgr 2012 and
configure advanced OSD TS´s etc.
Compile a long list of demos, features and functionality and let the customer choose which ones they would like to "examine" in their PoC. When you have tried this a few times you sort of know how long it takes to implement whatever they want.
And just like Gerry - I do not know of any guidance documents from Microsoft either.