Shell Method™ Software Engineering Process Repository
The PER acts as the primary point of contact and principal approver for the end-user community. In essence, the PER acts as the focal point for the end user community. On large projects, multiple PERs may exist, each dedicated to representing the end user community for one or more components or subsystems. In this case, a lead PER is assigned to coordinate activities with the lead PDR.
The PER works directly with the Primary Developer Representative to identify subject matter experts, coordinate meetings, conduct reviews, and track identified issues, consolidating and coordinating the responses of all end-users into a cohesive set of communications.
The PER is required to have a high-level understanding of the SDLC for this project, as well as specific knowledge of the deliverables and end-user review criteria for applicable deliverable classes. This is accomplished via:
Receiving the Lifecycle Overview presentation from the PDR, generally during the informal iteration process of the project planning stage.
Reviewing the documents available on the Shell Method example project Web site.
Reading the SDLC and Software Quality Assurance Plan (SQAP) documents.
The PER is considered to be qualified after receiving the Lifecycle Overview presentation and confirming their completion of the reading requirements with the PDR. An email confirmation of completion serves as objective evidence of qualification for the PER.