Managing Administrator Work

Before the release cycle begins, the administrator sets up a master record for the release. Then the administrator defines an access list of employees who are associated with the release. Then the administrator designates the employees on the access list for project teams that are associated with various stages of the release. The administrator also sets up Lists of Values (LOVs) for fields with drop-down lists in the Release Manager views. Finally, the administrator sets up activity templates. Users can use these templates to associate lists of specific activities with certain stages of the release process.

During release work, the administrator might have to perform certain maintenance tasks to make sure Release Manager continues to run smoothly for users. After Engineering completes product builds, the administrator adds product prototype records. Quality Assurance records tests for these records. When product parameters change in the course of development, the administrator might have to add new Area-Subarea combinations to add to the LOVs for Release Manager. When a new release cycle begins, the release administrator determines the need for new and revised test plans and test strategies.