Conference Room Pilot (CRP) is a term used in software procurement and software acceptance testing. A CRP may be used during the selection and implementation of a software application in an organisation or company.
The purpose of the Conference Room Pilot is to validate a software application against the business processes of end-users of the software, by allowing end-users to use the software to carry out typical or key business processes using the new software. The term is most commonly used in the context of ‘out of the box’ (OOTB) or ‘commercial off-the-shelf’ software (COTS).

A commercial advantage of a Conference Room Pilot is that it may allow the customer to prove that the new software will do the job (meets business requirements and expectations) before committing to buying the software, thus avoiding buying an inappropriate application.

A Conference Room Pilot shares some features of User Acceptance Testing (UAT). Shared features are:
Test scripts for end-to-end business processes are used
Functionality tests
Non-functional tests (e.g. performance testing)

Differences between a Conference Room Pilot and a formal UAT:
It is attempting to identify how well the application meets business needs, and identify gaps, whilst still in the design phase of the project
There is an expectation that changes will be required before acceptance of the solution
The software is ‘on trial’ and may be rejected completely in favour of another solution.

Citations:

http://www.ensync-corp.com/consulting/conference_room_pilot.cfm?section=consulting

http://www.glovia.com/html/services/methodology/

http://www-archive.ui-integrate.uillinois.edu/news_art_crp.asp

http://www.bourkeconsulting.com/documents/POCCRPBCAWebsite020903.pdf

http://www.smthacker.co.uk/conference_room_pilot.htm

标准实施方法论(AIM)，项目实施中项目计划及组织结构（Project Plan & Organization）会议室阶段（Conference Room Pilot）、业务模拟阶段（Business Pilot）、系统启动（System Startup）、实施后回顾（Post Implementation）的五大阶段