INTERNET APPLICATION DEVELOPMENT
MID MARKET ERP DEVELOPMENT
In a Conference Room Pilot, our project managers deploy a testing version of a completed or near completed automation accessible by CodePartners’ and our client’s team members. A Conference Room Pilot (or “CRP”), provides a platform for final application testing and for client company training. It’s a great opportunity to play with the system and try to “break” it. We encourage our clients to try every use case discovered in the Requirements Analysis phase, and we often find that additional requirements may come to light in the CRP process. These may or may not necessitate a change order, but our combined hope is that the end product emerges fully featured and fully tested. As such, the CRP may include several iterations separated by updates to the code.
As mentioned previously, the CRP also serves as an excellent client training opportunity. We know that the best way to learn new technology is often with hands-on access. Accordingly, the CRP gives unrestricted access without any fear of making a mistake. We sometimes formally deliver these training opportunities in a classroom or webinar setting, or we’ll be more informal by providing a basic introduction to the system and oversight along the way. We encourage our client’s personnel to make notes on their experiences during the Conference Room Pilot, to document improvements to the code or process as they are discovered.
A successful Conference Room Pilot ends when everyone agrees that the automation is complete and the end users know how to use it. The only thing left in the process is to deploy the finished product in a production environment.
Next time, I’ll write about “going live” with a new automation as well as the crucial support and maintenance functions that CodePartners provides after project completion.