CRP(Confrence Room Pilot)

CRP (Confrence Room Pilot) 会议室模拟。模拟运行及用户化。在基本掌握软件功能的基础上，选择代表产品，将各种必要的数据录入系统，带着企业日常工作中经常遇到的问题，组织项目小组进行实战性模拟，提出解决方案。模拟可集中在机房进行，也称之为会议室模拟（conference room pilot）。

Concept from Wiki

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. 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. The term is most commonly used in the context of 'out of the box' (OOTB) or 'commercial off-the-shelf' software (COTS).

CRP and UAT

Conference room pilot is kind of a software acceptance testing. It is kind of UAT. But UAT will do a functional testing and see if the solution is suitable as per the business requirements. However, conference room pilot tests the software to check whether its suitable for the business or not.

Although a conference room pilot shares some features of user acceptance testing (UAT), it should not be considered a testing process – it validates design or solution fit for purpose at a higher level than functional testing.

Shared features of CRP and UAT include:

• End-to-end business processes are used as a "business input" for both
• Functionality demonstrations
• Non-functional validation(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.

CRP-1: Discrete transactional activities
CRP-2: Proposed business processes (No RICE – custom Reports, Interfaces, Conversions, Enhancements / Extensions)
CRP-3: End to end business scenarios. Processes with converted data and some RICE components
UAT: Test 100% of functionality and end-to-end integration testing including all RICE components