PREO adheres to a strict change control process for all changes to the database, code, and page layouts.
Change requests are documented as "User Stories" and assigned a reference number.
User Stories are assigned to developers and worked on in 2 week cycles called "Sprints".
Completed User Stories are submitted to XBS Change Control through the change control site here: Change Control Site
Documentation of each User Story with proof of testing is provided on the request
The Change Control is approved by a local admin, a local manager and then is reviewed during a Teams meeting by Change Control Board.
During this meeting, the local admin will review the documentation and review the proposed changes.
If accepted, the Change Control is provided an effective date.
On the effective date, the new version of the application is pushed into production to complete the change control process.