Removed extraneous characters
diff --git a/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_product_documentation.xmi b/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_product_documentation.xmi index f1b93f7..9441983 100644 --- a/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_product_documentation.xmi +++ b/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_product_documentation.xmi
@@ -18,13 +18,13 @@ </p></mainDescription> <sections xmi:id="_-zf1suB8EeC1y_NExchKwQ" name="Identify features of current release" guid="_-zf1suB8EeC1y_NExchKwQ"> <sectionDescription><p>
 - %EOL% Every release will contain a set of features that were developed during the preceding feature development sprint
 - or%EOL% iterations. This list should drive the table of contents of the product documentation. It also is possible that
 - some%EOL% nonfunctional requirements should be documented as well.%EOL%
 -</p>%EOL%
 + Every release will contain a set of features that were developed during the preceding feature development sprint or
 + iterations. This list should drive the table of contents of the product documentation. It also is possible that some
 + nonfunctional requirements should be documented as well.
 +</p>
 <p>
 - %EOL% While the product documentation will not be used directly as user documentation, it will become the basis for the
 - user%EOL% documentation. That foundation of information is why this step is important.%EOL%
 + While the product documentation will not be used directly as user documentation, it will become the basis for the user
 + documentation. That foundation of information is why this step is important.
 </p></sectionDescription> </sections> <sections xmi:id="_-zf1seB8EeC1y_NExchKwQ" name="Document each feature" guid="_-zf1seB8EeC1y_NExchKwQ">
diff --git a/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_support_documentation.xmi b/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_support_documentation.xmi index 23035dd..2c66e96 100644 --- a/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_support_documentation.xmi +++ b/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_support_documentation.xmi
@@ -75,14 +75,14 @@ </ul></sectionDescription> </sections> <sections xmi:id="_-zfOqeB8EeC1y_NExchKwQ" name="Write support documentation" guid="_-zfOqeB8EeC1y_NExchKwQ"> - <sectionDescription>Based on the previous steps, write the support documentation. One way to do this is to assign sections of the
 -document%EOL%(determined in the step "Determine Support Documentation Contents" above) to development team members as
 -sprint/iteration%EOL%tasks in the release sprint/iteration.</sectionDescription> + <sectionDescription>Based on the previous steps, write the support documentation. One way to do this is to assign sections of the document
 +(determined in the step "Determine Support Documentation Contents" above) to development team members as sprint/iteration
 +tasks in the release sprint/iteration.</sectionDescription> </sections> <sections xmi:id="_-zfOrOB8EeC1y_NExchKwQ" name="Perform quality review" guid="_-zfOrOB8EeC1y_NExchKwQ"> - <sectionDescription>As the support documentation is integrated, plan and conduct a quality review during the release sprint/iteration to
 -ensure%EOL%that the documentation is of sufficient quantity and quality. Update and improve the support documentation based
 -on the%EOL%results of the quality review.</sectionDescription> + <sectionDescription>As the support documentation is integrated, plan and conduct a quality review during the release sprint/iteration to ensure
 +that the documentation is of sufficient quantity and quality. Update and improve the support documentation based on the
 +results of the quality review.</sectionDescription> </sections> <sections xmi:id="_-zfOqOB8EeC1y_NExchKwQ" name="Deliver support documentation" guid="_-zfOqOB8EeC1y_NExchKwQ"> <sectionDescription>At the end of a release, deliver the completed support documentation to the deployment manager. Ensure that the program has
diff --git a/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_training_materials.xmi b/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_training_materials.xmi index 26407d2..bb10bab 100644 --- a/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_training_materials.xmi +++ b/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_training_materials.xmi
@@ -15,57 +15,35 @@ </p></mainDescription> <sections xmi:id="_-zennOB8EeC1y_NExchKwQ" name="Determine scope of training materials" guid="_-zennOB8EeC1y_NExchKwQ"> <sectionDescription><p>
 - %EOL% Consult the program manager and deployment manager to determine the extent of training materials required for
 - this%EOL% release. Depending on the contents of the release, more or fewer training materials might be needed to
 - support both end%EOL% users and IT operations support personnel.%EOL%
 -</p>%EOL%
 + Consult the program manager and deployment manager to determine the extent of training materials required for this
 + release. Depending on the contents of the release, more or fewer training materials might be needed to support both end
 + users and IT operations support personnel.
 +</p>
 <p>
 - %EOL% Training materials generally consist of a combination of:%EOL%
 -</p>%EOL%
 + Training materials generally consist of a combination of:
 +</p>
 <ul>
 - <li style="list-style: none">
 - %EOL%
 + <li>
 + Presentation slides
 </li>
 <li>
 - %EOL% Presentation slides%EOL%
 - </li>
 - <li style="list-style: none">
 - %EOL%
 + Handouts
 </li>
 <li>
 - %EOL% Handouts%EOL%
 - </li>
 - <li style="list-style: none">
 - %EOL%
 + Training aids
 </li>
 <li>
 - %EOL% Training aids%EOL%
 - </li>
 - <li style="list-style: none">
 - %EOL%
 + Hands-on labs and/or exercises
 </li>
 <li>
 - %EOL% Hands-on labs and/or exercises%EOL%
 - </li>
 - <li style="list-style: none">
 - %EOL%
 + Quizzes or tests
 </li>
 <li>
 - %EOL% Quizzes or tests%EOL%
 + Practical application workshops
 </li>
 - <li style="list-style: none">
 - %EOL%
 - </li>
 - <li>
 - %EOL% Practical application workshops%EOL%
 - </li>
 - <li style="list-style: none">
 - %EOL%
 - </li>
 -</ul>%EOL%
 +</ul>
 <p>
 - %EOL% Training materials often are grouped into modules, each with a set of learning objectives and competency
 - assessments.%EOL%
 + Training materials often are grouped into modules, each with a set of learning objectives and competency assessments.
 </p></sectionDescription> </sections> <sections xmi:id="_-zenm-B8EeC1y_NExchKwQ" name="Develop user training materials" guid="_-zenm-B8EeC1y_NExchKwQ"> @@ -82,26 +60,25 @@ </sections> <sections xmi:id="_-zenmuB8EeC1y_NExchKwQ" name="Develop support training materials" guid="_-zenmuB8EeC1y_NExchKwQ"> <sectionDescription><p>
 - %EOL% In many cases, IT support personnel are experienced enough to require minimal training on a product release.
 - However,%EOL% where the product is new to the support organization, or the support personnel themselves are
 - inexperienced or%EOL% unfamiliar with a particular technology, support training becomes very important to the success
 - of the product rollout.%EOL%
 -</p>%EOL%
 + In many cases, IT support personnel are experienced enough to require minimal training on a product release. However,
 + where the product is new to the support organization, or the support personnel themselves are inexperienced or
 + unfamiliar with a particular technology, support training becomes very important to the success of the product rollout.
 +</p>
 <p>
 - %EOL% Using the support documentation as a guideline, identify the parts of the product on which IT support personnel
 - will%EOL% need to be trained. Identify training modules and document learning objectives for each module, then leverage
 - as much%EOL% of the support documentation content as you can to create your training materials.%EOL%
 + Using the support documentation as a guideline, identify the parts of the product on which IT support personnel will
 + need to be trained. Identify training modules and document learning objectives for each module, then leverage as much
 + of the support documentation content as you can to create your training materials.
 </p></sectionDescription> </sections> <sections xmi:id="_-zenn-B8EeC1y_NExchKwQ" name="Perform quality review" guid="_-zenn-B8EeC1y_NExchKwQ"> - <sectionDescription>As user and support training materials are developed, plan and conduct a quality review during the release
 -sprint/iteration%EOL%to ensure that the materials are of sufficient quantity and quality. Update and improve the training
 -materials based on the%EOL%results of the quality review.</sectionDescription> + <sectionDescription>As user and support training materials are developed, plan and conduct a quality review during the release sprint/iteration
 +to ensure that the materials are of sufficient quantity and quality. Update and improve the training materials based on the
 +results of the quality review.</sectionDescription> </sections> <sections xmi:id="_-zennuB8EeC1y_NExchKwQ" name="Perform dry run" guid="_-zennuB8EeC1y_NExchKwQ"> - <sectionDescription>Before formally delivering the user or support training, plan a sprint/iteration task in which representatives of both
 -the%EOL%user and support communities are invited to participate in a dry run of the training materials. Use the feedback
 -obtained%EOL%from these sessions to improve the training materials during the release sprint/iteration.</sectionDescription> + <sectionDescription>Before formally delivering the user or support training, plan a sprint/iteration task in which representatives of both the
 +user and support communities are invited to participate in a dry run of the training materials. Use the feedback obtained
 +from these sessions to improve the training materials during the release sprint/iteration.</sectionDescription> </sections> <sections xmi:id="_-zenneB8EeC1y_NExchKwQ" name="Deliver training materials" guid="_-zenneB8EeC1y_NExchKwQ"> <sectionDescription>When the final user and support training materials are complete, deliver them to the deployment manager for integration
diff --git a/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_user_documentation.xmi b/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_user_documentation.xmi index 40b2fd0..cd6b720 100644 --- a/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_user_documentation.xmi +++ b/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_user_documentation.xmi
@@ -12,52 +12,31 @@ </p></mainDescription> <sections xmi:id="_-zfOo-B8EeC1y_NExchKwQ" name="Determine user documentation contents" guid="_-zfOo-B8EeC1y_NExchKwQ"> <sectionDescription><p>
 - %EOL% User documentation often consists of a wide variety of content such as:%EOL%
 -</p>%EOL%
 + User documentation often consists of a wide variety of content such as:
 +</p>
 <ul>
 - <li style="list-style: none">
 - %EOL%
 + <li>
 + User manuals (electronic or paper-based)
 </li>
 <li>
 - %EOL% User manuals (electronic or paper-based)%EOL%
 - </li>
 - <li style="list-style: none">
 - %EOL%
 + Tutorials
 </li>
 <li>
 - %EOL% Tutorials%EOL%
 - </li>
 - <li style="list-style: none">
 - %EOL%
 + Frequently asked questions (FAQs)
 </li>
 <li>
 - %EOL% Frequently asked questions (FAQs)%EOL%
 - </li>
 - <li style="list-style: none">
 - %EOL%
 + On-line Help Files
 </li>
 <li>
 - %EOL% On-line Help Files%EOL%
 - </li>
 - <li style="list-style: none">
 - %EOL%
 + Installation and configuration instructions
 </li>
 <li>
 - %EOL% Installation and configuration instructions%EOL%
 + Operational procedures (or job aids)
 </li>
 - <li style="list-style: none">
 - %EOL%
 - </li>
 - <li>
 - %EOL% Operational procedures (or job aids)%EOL%
 - </li>
 - <li style="list-style: none">
 - %EOL%
 - </li>
 -</ul>%EOL%
 +</ul>
 <p>
 - %EOL% For your product and for this release, determine which of these types of user documentation your team will
 - develop and%EOL% deliver.%EOL%
 + For your product and for this release, determine which of these types of user documentation your team will develop and
 + deliver.
 </p></sectionDescription> </sections> <sections xmi:id="_-zfOpeB8EeC1y_NExchKwQ" name="Leverage product documentation" guid="_-zfOpeB8EeC1y_NExchKwQ">
diff --git a/epf_prac_151/practice.gen.production_release.base/tasks/develop_backout_plan.xmi b/epf_prac_151/practice.gen.production_release.base/tasks/develop_backout_plan.xmi index 7f65817..603ba6f 100644 --- a/epf_prac_151/practice.gen.production_release.base/tasks/develop_backout_plan.xmi +++ b/epf_prac_151/practice.gen.production_release.base/tasks/develop_backout_plan.xmi
@@ -5,13 +5,13 @@ The&nbsp;Development team should provide the production support organization with a specific plan and decision criteria
 made available to them to avoid or minimize service interruptions.</mainDescription> <sections xmi:id="_IAIu9eB-EeC1y_NExchKwQ" name="Determine if backout plan exists" guid="_IAIu9eB-EeC1y_NExchKwQ"> - <sectionDescription>Determine whether the development team has a backout plan already written for a previous release. If so, part of that
 -plan%EOL%might be reusable. If this release is the development team%sq%s first, another development team with a similar
 -feature set%EOL%might have a plan that can be used as a starting point.</sectionDescription> + <sectionDescription>Determine whether the development team has a backout plan already written for a previous release. If so, part of that plan
 +might be reusable. If this release is the development team's first, another development team with a similar feature set
 +might have a plan that can be used as a starting point.</sectionDescription> </sections> <sections xmi:id="_IAIu8-B-EeC1y_NExchKwQ" name="Develop the backout plan (if applicable)" guid="_IAIu8-B-EeC1y_NExchKwQ"> - <sectionDescription>If a backout plan does not exist, or one cannot be found to be used as a starting point, answer the questions documented
 -in%EOL%the <a class="elementLinkWithType"
 + <sectionDescription>If a backout plan does not exist, or one cannot be found to be used as a starting point, answer the questions documented in
 +the <a class="elementLinkWithType"
 href="./../../practice.gen.production_release.base/workproducts/backout_plan_DC0D7247.html"
 guid="_IAHg2eB-EeC1y_NExchKwQ">Artifact: Backout Plan</a> to start and develop a backout plan.</sectionDescription> </sections>
diff --git a/epf_prac_151/practice.gen.production_release.base/tasks/execute_backout_plan.xmi b/epf_prac_151/practice.gen.production_release.base/tasks/execute_backout_plan.xmi index 919bafa..edc342a 100644 --- a/epf_prac_151/practice.gen.production_release.base/tasks/execute_backout_plan.xmi +++ b/epf_prac_151/practice.gen.production_release.base/tasks/execute_backout_plan.xmi
@@ -8,26 +8,24 @@ executing the backout plan.</mainDescription> <sections xmi:id="_IAD2c-B-EeC1y_NExchKwQ" name="Identify release problem(s)" guid="_IAD2c-B-EeC1y_NExchKwQ"> <sectionDescription><p>
 - %EOL% In the event that the release to production experiences problems, either during or after deployment, the backout
 - plan%EOL% should be invoked. However, the deployment engineer (or development team) must understand where the release
 - went wrong%EOL% so that the code can be fixed before the next release attempt. This is a critical step, but it should
 - be done quickly%EOL% so that the problematic release can be reversed before significant damage is done to the
 - production environment.%EOL%
 -</p>%EOL%
 + In the event that the release to production experiences problems, either during or after deployment, the backout plan
 + should be invoked. However, the deployment engineer (or development team) must understand where the release went wrong
 + so that the code can be fixed before the next release attempt. This is a critical step, but it should be done quickly
 + so that the problematic release can be reversed before significant damage is done to the production environment.
 +</p>
 <p>
 - %EOL% Log the issues as critical defects as soon as possible and assign those defects to the appropriate team members
 - for%EOL% resolution.%EOL%
 + Log the issues as critical defects as soon as possible and assign those defects to the appropriate team members for
 + resolution.
 </p></sectionDescription> </sections> <sections xmi:id="_IAD2cOB-EeC1y_NExchKwQ" name="Backout the release" guid="_IAD2cOB-EeC1y_NExchKwQ"> - <sectionDescription>Following the instructions in the backout plan, reverse the deployment. However, be aware that the backout
 -plan%EOL%instructions are a guide and should not always be taken literally. This interpretation is due to the fact that not
 -every%EOL%problematic condition can be documented in advance and because each real-world situation might be slightly
 -different.</sectionDescription> + <sectionDescription>Following the instructions in the backout plan, reverse the deployment. However, be aware that the backout plan
 +instructions are a guide and should not always be taken literally. This interpretation is due to the fact that not every
 +problematic condition can be documented in advance and because each real-world situation might be slightly different.</sectionDescription> </sections> <sections xmi:id="_IAD2cuB-EeC1y_NExchKwQ" name="Determine if the backout was successful" guid="_IAD2cuB-EeC1y_NExchKwQ"> - <sectionDescription>Ascertain whether the reversal was successful. If not, key members of the release team, development team, or program
 -level%EOL%agile system team might need to be engaged to find and fix the problem(s).</sectionDescription> + <sectionDescription>Ascertain whether the reversal was successful. If not, key members of the release team, development team, or program level
 +agile system team might need to be engaged to find and fix the problem(s).</sectionDescription> </sections> <sections xmi:id="_IAD2ceB-EeC1y_NExchKwQ" name="Communicate the backout" guid="_IAD2ceB-EeC1y_NExchKwQ"> <sectionDescription>Ensure that all interested parties are aware of the failed release. Because releases often take place at odd hours to
diff --git a/epf_prac_151/practice.gen.production_release.base/tasks/execute_deployment_plan.xmi b/epf_prac_151/practice.gen.production_release.base/tasks/execute_deployment_plan.xmi index 1f6479c..4b07341 100644 --- a/epf_prac_151/practice.gen.production_release.base/tasks/execute_deployment_plan.xmi +++ b/epf_prac_151/practice.gen.production_release.base/tasks/execute_deployment_plan.xmi
@@ -12,9 +12,8 @@ plan's contents.
 </p></mainDescription> <sections xmi:id="_IAD2deB-EeC1y_NExchKwQ" name="Review deployment plan" guid="_IAD2deB-EeC1y_NExchKwQ"> - <sectionDescription>Review the contents of the deployment plan to ensure that the production environment has all the dependent
 -components%EOL%installed and that the system is in the correct state. Also ensure that the release window is ready to be
 -achieved.</sectionDescription> + <sectionDescription>Review the contents of the deployment plan to ensure that the production environment has all the dependent components
 +installed and that the system is in the correct state. Also ensure that the release window is ready to be achieved.</sectionDescription> </sections> <sections xmi:id="_IAD2duB-EeC1y_NExchKwQ" name="Release code" guid="_IAD2duB-EeC1y_NExchKwQ"> <sectionDescription><p>
diff --git a/epf_prac_151/practice.gen.production_release.base/tasks/package_the_release.xmi b/epf_prac_151/practice.gen.production_release.base/tasks/package_the_release.xmi index 71564c1..6f256f7 100644 --- a/epf_prac_151/practice.gen.production_release.base/tasks/package_the_release.xmi +++ b/epf_prac_151/practice.gen.production_release.base/tasks/package_the_release.xmi
@@ -38,10 +38,10 @@ </li>
 </ul></mainDescription> <sections xmi:id="_IAEdheB-EeC1y_NExchKwQ" name="Assemble components" guid="_IAEdheB-EeC1y_NExchKwQ"> - <sectionDescription>Question all the developers on the development team to determine which components are ready for packaging. Only
 -package%EOL%those components that were completed and accepted during the previous feature development sprint/iterations.
 -Components%EOL%that were not finished or not accepted should not be bundled, unless the customer has granted an exception
 -or they are%EOL%infrastructure-related components.</sectionDescription> + <sectionDescription>Question all the developers on the development team to determine which components are ready for packaging. Only package
 +those components that were completed and accepted during the previous feature development sprint/iterations. Components
 +that were not finished or not accepted should not be bundled, unless the customer has granted an exception or they are
 +infrastructure-related components.</sectionDescription> </sections> <sections xmi:id="_IAEdguB-EeC1y_NExchKwQ" name="Test the release" guid="_IAEdguB-EeC1y_NExchKwQ"> <sectionDescription>After the components have been packaged and built, that executable should be installed and run in a test environment that
 @@ -53,8 +53,8 @@ package can be reconstructed at a later date, if needed. This tag is known as the release "baseline."</sectionDescription> </sections> <sections xmi:id="_IAEdg-B-EeC1y_NExchKwQ" name="Package release documentation" guid="_IAEdg-B-EeC1y_NExchKwQ"> - <sectionDescription>Gather all the product, user, and support documentation developed earlier in the production release sprint/iteration
 -and%EOL%add it to the release package.</sectionDescription> + <sectionDescription>Gather all the product, user, and support documentation developed earlier in the production release sprint/iteration and
 +add it to the release package.</sectionDescription> </sections> <sections xmi:id="_IAEdgeB-EeC1y_NExchKwQ" name="Deliver release package" guid="_IAEdgeB-EeC1y_NExchKwQ"> <sectionDescription>When the entire release package, including documentation, is ready, deliver it to the deployment manager and the release
diff --git a/epf_prac_151/practice.gen.production_release.base/tasks/plan_deployment.xmi b/epf_prac_151/practice.gen.production_release.base/tasks/plan_deployment.xmi index 611a2ed..6de4a02 100644 --- a/epf_prac_151/practice.gen.production_release.base/tasks/plan_deployment.xmi +++ b/epf_prac_151/practice.gen.production_release.base/tasks/plan_deployment.xmi
@@ -7,13 +7,13 @@ by the deployment engineer before and during the deployment to production of a particular release package.
 </p></mainDescription> <sections xmi:id="_IAJ9E-B-EeC1y_NExchKwQ" name="Determine if deployment plan exists" guid="_IAJ9E-B-EeC1y_NExchKwQ"> - <sectionDescription>Determine whether the development team has a deployment plan already written for a previous release. If so, part of
 -that%EOL%plan might be reusable. If this is the development team%sq%s first release, another development team with a
 -similar feature%EOL%set might have a plan that can be used as a starting point.</sectionDescription> + <sectionDescription>Determine whether the development team has a deployment plan already written for a previous release. If so, part of that
 +plan might be reusable. If this is the development team's first release, another development team with a similar feature
 +set might have a plan that can be used as a starting point.</sectionDescription> </sections> <sections xmi:id="_IAJ9EuB-EeC1y_NExchKwQ" name="Develop the deployment plan (if applicable)" guid="_IAJ9EuB-EeC1y_NExchKwQ"> - <sectionDescription>If a deployment plan does not exist, or one cannot be found to be used as a starting point, use the recommended
 -format%EOL%documented in the <a class="elementLinkWithType"
 + <sectionDescription>If a deployment plan does not exist, or one cannot be found to be used as a starting point, use the recommended format
 +documented in the <a class="elementLinkWithType"
 href="./../../practice.gen.production_release.base/workproducts/deployment_plan_121938C3.html"
 guid="_IAJ9FeB-EeC1y_NExchKwQ">Artifact: Deployment Plan</a> and refer to the <a class="elementLinkWithType"
 href="./../../practice.gen.production_release.base/guidances/checklists/deployment_plan_C4767691.html"
diff --git a/epf_prac_151/practice.gen.production_release.base/tasks/review_conform_to_release_controls.xmi b/epf_prac_151/practice.gen.production_release.base/tasks/review_conform_to_release_controls.xmi index 527ec3d..1ad3b61 100644 --- a/epf_prac_151/practice.gen.production_release.base/tasks/review_conform_to_release_controls.xmi +++ b/epf_prac_151/practice.gen.production_release.base/tasks/review_conform_to_release_controls.xmi
@@ -34,13 +34,13 @@ </li>
 </ul></mainDescription> <sections xmi:id="_IAJWAuB-EeC1y_NExchKwQ" name="Locate release controls" guid="_IAJWAuB-EeC1y_NExchKwQ"> - <sectionDescription>If the program%sq%s release controls are not readily available, the development team must engage the deployment manager
 -and/or%EOL%their deployment engineers to know where to find the release controls and be able to comply with them.</sectionDescription> + <sectionDescription>If the program's release controls are not readily available, the development team must engage the deployment manager and/or
 +their deployment engineers to know where to find the release controls and be able to comply with them.</sectionDescription> </sections> <sections xmi:id="_IAJWAeB-EeC1y_NExchKwQ" name="Review release controls" guid="_IAJWAeB-EeC1y_NExchKwQ"> - <sectionDescription>The development team should thoroughly review the release controls so that it understands what is expected before a
 -release%EOL%is accepted into the production environment. If the team has any questions or issues with the controls, team
 -members should%EOL%communicate directly with the deployment manager or the deployment engineer to understand the issues.</sectionDescription> + <sectionDescription>The development team should thoroughly review the release controls so that it understands what is expected before a release
 +is accepted into the production environment. If the team has any questions or issues with the controls, team members should
 +communicate directly with the deployment manager or the deployment engineer to understand the issues.</sectionDescription> </sections> <sections xmi:id="_IAJWAOB-EeC1y_NExchKwQ" name="Ensure the team release conforms to the controls" guid="_IAJWAOB-EeC1y_NExchKwQ"> <sectionDescription><p>
diff --git a/epf_prac_151/practice.gen.production_release.base/tasks/verify_successful_deployment.xmi b/epf_prac_151/practice.gen.production_release.base/tasks/verify_successful_deployment.xmi index 1e2aa9f..e085328 100644 --- a/epf_prac_151/practice.gen.production_release.base/tasks/verify_successful_deployment.xmi +++ b/epf_prac_151/practice.gen.production_release.base/tasks/verify_successful_deployment.xmi
@@ -13,8 +13,8 @@ tests should be brief but revealing enough to quickly determine the validity of the deployment.</sectionDescription> </sections> <sections xmi:id="_IAFEk-B-EeC1y_NExchKwQ" name="Run manual tests" guid="_IAFEk-B-EeC1y_NExchKwQ"> - <sectionDescription>If the automated smoke tests are successful, run several complex manual tests to simulate key end user behavior.
 -These%EOL%tests should be executed by development team members or stakeholders recruited specifically for this purpose.</sectionDescription> + <sectionDescription>If the automated smoke tests are successful, run several complex manual tests to simulate key end user behavior. These
 +tests should be executed by development team members or stakeholders recruited specifically for this purpose.</sectionDescription> </sections> <sections xmi:id="_IAFElOB-EeC1y_NExchKwQ" name="Determine if release should be reversed" guid="_IAFElOB-EeC1y_NExchKwQ"> <sectionDescription>In some situations, problems with the release might be encountered but are not serious enough to reverse the deployment. If