Research Article

Orchestrating End-User Perspectives in the Software Release Process: An Integrated Release Management Framework

Table 2

Proposed Customer Release Manager Activities and Process Group Mappings.

Release ActivityProject Management Process
InitiatingPlanningExecutingMonitoring and ControllingClosing

Release PolicyDetermine optimal policy for the organization with appropriate stakeholdersDevelop the release policy and add to procurement documentationNegotiate policy with vendor at software procurement time. Enforce changesEnsure policy is followed by vendor and document changes if necessaryDocument and archive lessons learned

Release Planning Integrate lessons learned from prior releases. Review prioritized request for changes (RFC). Identify impacted end-users and address end-user enhancements needsPlan release’s scope (RFC, enhancements), schedule, potential costs, UAT (use cases, quality control testing), resource roles, communication strategy, risks, hardware/software procurement needs, roll-out strategy, training, distribution, and installation strategy. Re-plan based on changesCoordinate plans with the vendor’s release manager. Communicate plans with release stakeholders. Procure hardware or software. Enforce changesDocument changes based on vendor’s release manager’s feedback. Track and document any changesDocument and archive lessons learned

Design and Develop the SoftwareReview the release scope, schedule, end-user resources plans, and integrate lessons learned on UAT cases from prior releasesPlan required use cases for the RFCs and enhancements with end-users and vendor release manager. Re-plan if there are new changesDirect and manage the documentation effort of end-users. Coordinate progress and distribution of use cases with vendor’s release manager. Enforce changesVerify all use cases have been completed and delivered. Track and document any changesDocument and archive lessons learned

Build and Configure the ReleaseIntegrate lessons learned on build and configuration from prior releasesRe-plan if there are changesAddress potential issues associated with the compilation and configuration with vendor release manager (version, access permissions, and security). Enforce changesTrack and document any changesDocument and archive lessons learned

Fit-for-Purpose TestingIntegrate lessons learned on fit-for-purpose testing from prior releasesPlan the testing of a pilot. Re-plan if there are changesDirect and manage the pilot testing. Enforce changesDocument and communicate issues and potential changes with end-users and vendor release managerDocument and archive lessons learned

Release AcceptanceIntegrate lessons learned on release acceptance from prior releases. Review release plansRe-plan if there are changesDirect and mange the deployment of release into test environment, the acceptance testing and communications of issues with vendor release manager, and the deployment of fixes to issues. Adjust release plans based on progress. Enforce changesDocument and track reported issues, changes, and report on progress with stakeholdersDocument and archive lessons learned

Roll-out PlanningIntegrate lessons learned on roll-out from prior releases. Identify stakeholders involved in the roll-out (e.g. IT, key end-users, vendor resources)Prepare distribution and installation time table checklist including back out procedures, production testing, each roll-out activity, and each participant’s role and responsibility. Re-plan if there are changesCoordinate roll-out plan with vendor release manager. Enforce changesTrack and document any changesDocument and archive lessons learned

Communication, Preparation, and TrainingIntegrate lessons learned from prior releases. Identify stakeholders who will perform the trainingReview release plan for training, levels of support after the release installation. Re-plan if there are changesDocument any procedures, and communicate with end-users and vendor release manager to address any improvements. Direct and manage training. Make final decision on go/no go for release with vendor release manager and stakeholders. Manage trial runs for the installation. Enforce changesTrack and document any changesDocument and archive lessons learned

Distribution and InstallationIntegrate lessons learned on distribution and installation from prior releasesRe-plan if there are changesDirect and manage the roll-out. Ensure backups are completed. Direct production testing and make decision of go-live versus stopping the release. Enforce changesTrack progress, document issues, and communicate with stakeholdersDocument and archive lessons learned