1 / 17

DELIVER PHASE

training manager. support engineer. operations manager. support manager. project manager. operations engineer. developer. project auditor. testing manager. test engineer. technical writer. trainer. DELIVER PHASE.

anneke
Télécharger la présentation

DELIVER PHASE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. training manager support engineer operations manager support manager project manager operations engineer developer project auditor testing manager test engineer technical writer trainer DELIVER PHASE The main goal here is to deploy the application, including the appropriate documentation, to the user community. TESTin the large RELEASE packaged applicationdocumentationmodels and source codemanagement documentsrequirement alloc. matrix tested applicationdocumentationmodelsrequirement alloc. matrix REWORK ASSESS potential roles during this phase:

  2. The goal here is to ensure that the application works on its entirety. This includes user testing in which the application is specifically tested by members of user community. TEST IN THE LARGE ACCEPTTESTPLAN FUNCTIONTEST INSTALLATIONTEST packaged applicationmaster testquality assurance planprevious test results tested applicationtest results STRESSTEST OPERATIONSTEST ALPHA/BETATEST USERACCEPTANCETEST PERFORMMETRICS RECORDDEFECTS

  3. Test in the large entrance conditions checklist • The application has been packaged for delivery • The master test/QA plan in available • Previous test results are available • Team members are trained

  4. Test in the large to be performed checklist • The master test/QA plan was accepted • Defects have been recorded • All particular tests were performed • Artifacts that are potentially reusable by this project team have been identified and used • Decisions, both made and forgone, have been documented in group memory • Metrics have been collected

  5. Test in the large exit conditions checklist • The application has passed testing • Test results were documented

  6. The focus of this process is to fix the critical defects discovered by the “test in the large” process to ensure the successful deployment of the application. It is like a miniature version of the “construct” process. REWORK PRIORITIZEDEFECTS REMODEL REPROGRAM tested application tested results, documents models, source coderequirement alloc. matrix organizational priorities reworked applicationmodels, source codedocumentation requirement alloc. matrix UPDATEDOCUMENTA-TION TESTIN THESMALL PERFORMMETRICS

  7. Rework entrance conditions checklist • The test results are available • The organization priorities are known • The current version of software is able to be reworked • Team members are trained

  8. Rework to be performed checklist • Defects have been prioritized • The models have been reworked • The requirement allocation matrix has been reworked • The support documentation has been reworked • The user documentation has been reworked • The operations documentation has been reworked • The source code has been reworked • The application was tested in the small (system tests) • Reusable artifacts were used • Risk assessment document was updated • Decisions, both made and forgone, have been documented in group memory • Metrics have been collected

  9. Rework exit conditions checklist • The selected and prioritized defects have been reworked • The construct phase deliverables (code, doc, models) are consistent • The application has been repackaged for testing

  10. The goal of this process is to deploy the application and its corresponding documentation successfully to the user community (end users and also operations department staff that will help the users work with the application effectively). RELEASE ACCEPT TRAINING AND RELEASEPLANS ACCEPT USERSUPPORT ANDOPERATIONSDOCUMENTS PACKAGEAPPLICATION FINALIZECONVERSIONOF LEGACY DATA DEPLOY THE OPERATIONPROCESS TRAINOPERATIONSSTAFF release procedures training plans application package operations and support documentation released application procedures documentation DEPLOY THESUPPORTPROCESS TRAINSUPPORTSTAFF ANNONCEACTUALRELEASETO USERS TRAINUSERS DEPLOY THEAPPLICATION PERFORMMETRICS

  11. Release entrance conditions checklist • The application has been packaged for release • Organization release procedures are available • The training plan for user, operations and support communities are available • The documentation is available to be deployed • Team members are trained

  12. Release to be performed checklist • The training and release plans have been accepted • The user, support and operations documentation has been accepted • The legacy data has been converted • The product baseline and version description has been finalized • The release notes have been finalized • The installation procedures have been finalized • The operation staff has been trained • The support staff has been trained • The release was announced • The user community was trained • The application was deployed to user community • Risk management document was updated • Decisions, both made and forgone, have been documented in group memory • Metrics have been collected

  13. Release exit conditions checklist • The user, support, and operations communities have been trained • The application has been deployed • The application and its documentation has been accepted • The support environment has been installed

  14. This process has two goals: a) for the project team, to learn from its experiences developing the applicationb) to provide an opportunity to evaluate the members of the project team to support their personal growth ASSESS REVIEWPROJECTDELIVERA-BLES DEVELOPPROJECTASSESSMENT ASSESSTEAMMEMBERPERFORMANCE DEVELOPLEARNINGHISTORY project deliverables project metrics group knowledge base learning history project and staff assessment process improvement plan ANALYZEMETRICS DEVELOPSTAFFASSESSMENT ASSESSUSERINVOLVEMENT DEVELOPSOFTWAREPROCESSIMPROV. PLAN

  15. Assess entrance conditions checklist • Management support exists • Project members and key user representatives are available • Project deliverables, including the group memory and collected metrics are available • Team members are trained

  16. Assess to be performed checklist • Project deliverables were reviewed • Metrics collected during the project were presented and analyzed • The performance of individual team members was assessed • The involvement of user community was assessed • The involvement of support community was assessed • The involvement of operations community was assessed • The project assessment was documented • The learning history was developed • The software process improvement plan was developed • Risk assessment document has been updated • Decisions, both made and forgone, have been documented in group memory • Metrics have been collected

  17. Assess exit conditions checklist • All staff assessments are complete • The project assessment has been presented to senior management • The software process improvement plan has been accepted

More Related