219
23.7.1. Best Practices
● Prove that processes are followed and software meets requirements through QA audits.
● Write user documentation so the team can run the system in the absence of the lead
trader.
● All changes to code must be proved with a new and complete round of unit, integration,
system, and user acceptance tests.
● Use probationary trading to uncover any remaining flaws.
● Regress performance metrics against past results. Differences must be researched
and their causes documented for discussion at the Gate 3 meeting.23.7. SUMMARY