*** empty log message ***
diff --git a/epf_prac_151/core.default.cat_def.base/disciplines/project_management_discipline.xmi b/epf_prac_151/core.default.cat_def.base/disciplines/project_management_discipline.xmi
index 0a12939..5e70ec0 100644
--- a/epf_prac_151/core.default.cat_def.base/disciplines/project_management_discipline.xmi
+++ b/epf_prac_151/core.default.cat_def.base/disciplines/project_management_discipline.xmi
@@ -29,7 +29,7 @@
</p>
<ul>
<li>
- Stakeholders trust in the team's ability to successfully deliver value and understand the capabilities and
+ stakeholders trust in the team's ability to successfully deliver value and understand the capabilities and
tradeoffs of the technical platform
</li>
<li>
diff --git a/epf_prac_151/core.default.role_def.base/plugin.xmi b/epf_prac_151/core.default.role_def.base/plugin.xmi
index 618f195..2c27def 100644
--- a/epf_prac_151/core.default.role_def.base/plugin.xmi
+++ b/epf_prac_151/core.default.role_def.base/plugin.xmi
@@ -68,7 +68,7 @@
<contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_0YDosMlgEdmt3adZL5Dmdw" name="developer" guid="_0YDosMlgEdmt3adZL5Dmdw" presentationName="Developer" briefDescription="The Developer is responsible for developing a part of the system, including designing it to fit into the architecture, possibly prototyping the user interface, and then implementing, unit-testing, and integrating the components that are part of the solution.">
<presentation xmi:id="_NqL7MqeqEdmKDbQuyzCoqQ" href="uma://_NqL7MqeqEdmKDbQuyzCoqQ#_NqL7MqeqEdmKDbQuyzCoqQ"/>
</contentElements>
- <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_0a0o0MlgEdmt3adZL5Dmdw" name="project_manager" guid="_0a0o0MlgEdmt3adZL5Dmdw" presentationName="Project Manager" briefDescription="The Project Manager leads the planning of the project, coordinates interactions with the Stakeholders, and keeps the project team focused on meeting the project objectives.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_0a0o0MlgEdmt3adZL5Dmdw" name="project_manager" guid="_0a0o0MlgEdmt3adZL5Dmdw" presentationName="Project Manager" briefDescription="The Project Manager leads the planning of the project, coordinates interactions with the stakeholders, and keeps the project team focused on meeting the project objectives.">
<presentation xmi:id="_Fdq-8KX4EdmvhNXG0Oc2uA" href="uma://_Fdq-8KX4EdmvhNXG0Oc2uA#_Fdq-8KX4EdmvhNXG0Oc2uA"/>
</contentElements>
<contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_dTa6gMAYEdqX-s4mWhkyqQ" name="stakeholder" guid="_dTa6gMAYEdqX-s4mWhkyqQ" presentationName="Stakeholder" briefDescription="This role represents interest groups whose needs must be satisfied by the project. It is a role that may be played by anyone who is (or potentially will be) materially affected by the outcome of the project."/>
@@ -116,7 +116,7 @@
<methodElementProperty xmi:id="_Qv2ZsJldEeGlkdGl1HQlDA" name="me_edited" value="true"/>
<presentation xmi:id="-C6ZZTqQccgTUpiCA8BWeKg" href="uma://-C6ZZTqQccgTUpiCA8BWeKg#-C6ZZTqQccgTUpiCA8BWeKg"/>
</contentElements>
- <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_-zf1teB8EeC1y_NExchKwQ" name="technical_writer" guid="_-zf1teB8EeC1y_NExchKwQ" presentationName="Technical Writer" briefDescription="A Technical Writer often helps a Development Team complete the documentation needed for the Product Owner, End Users, and support personnel to understand and to be able to use the delivered features.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_-zf1teB8EeC1y_NExchKwQ" name="technical_writer" guid="_-zf1teB8EeC1y_NExchKwQ" presentationName="Technical Writer" briefDescription="A Technical Writer often helps a development team member complete the documentation needed for the Product Owner, End Users, and support personnel to understand and to be able to use the delivered features.">
<methodElementProperty xmi:id="_Z4RWwJldEeGlkdGl1HQlDA" name="me_edited" value="true"/>
<presentation xmi:id="-OW9Mlf5qrIMlT-E_1TEn2A" href="uma://-OW9Mlf5qrIMlT-E_1TEn2A#-OW9Mlf5qrIMlT-E_1TEn2A"/>
</contentElements>
@@ -134,7 +134,7 @@
<methodElementProperty xmi:id="_Z4kRsJldEeGlkdGl1HQlDA" name="me_edited" value="true"/>
<presentation xmi:id="-hFifDXUlUkM6ZN3q-aXyDA" href="uma://-hFifDXUlUkM6ZN3q-aXyDA#-hFifDXUlUkM6ZN3q-aXyDA"/>
</contentElements>
- <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_-a85MeCEEeC1y_NExchKwQ" name="product_owner" guid="_-a85MeCEEeC1y_NExchKwQ" presentationName="Product Owner" briefDescription="The Product Owner represents the End User's needs and defines the "work" in the project. This team member typically is co-located with a Development Team.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_-a85MeCEEeC1y_NExchKwQ" name="product_owner" guid="_-a85MeCEEeC1y_NExchKwQ" presentationName="Product Owner" briefDescription="The Product Owner represents the End User's needs and defines the "work" in the project. This team member typically is co-located with a development team.">
<presentation xmi:id="-Mcx6tqWLjhR3Dd12ad3EsQ" href="uma://-Mcx6tqWLjhR3Dd12ad3EsQ#-Mcx6tqWLjhR3Dd12ad3EsQ"/>
</contentElements>
</childPackages>
diff --git a/epf_prac_151/core.default.role_def.base/roles/deployment_manager.xmi b/epf_prac_151/core.default.role_def.base/roles/deployment_manager.xmi
index dedb215..1abc0a6 100644
--- a/epf_prac_151/core.default.role_def.base/roles/deployment_manager.xmi
+++ b/epf_prac_151/core.default.role_def.base/roles/deployment_manager.xmi
@@ -14,10 +14,10 @@
Manage a support team that performs most of the day-to-day work
</li>
<li>
- Assist the Program Manager and the Development Teams in planning each release
+ Assist the Program Manager and the development team members in planning each release
</li>
<li>
- Ensure that the organization's release controls are documented and well understood by Development Teams and Program
+ Ensure that the organization's release controls are documented and well understood by development Teams and Program
Support Teams
</li>
<li>
@@ -29,7 +29,7 @@
</li>
<li>
Coordinate with the Marketing Department and the program to ensure that sanctioned communications to all
- Stakeholders have been properly prepared and reviewed
+ stakeholders have been properly prepared and reviewed
</li>
<li>
Ensure the product has been correctly and completely integrated across the&nbsp;program
@@ -42,10 +42,10 @@
Work with the Marketing Department or IT Operations to deploy the product successfully
</li>
<li>
- Release the pre-planned communications about the product to all Stakeholders
+ Release the pre-planned communications about the product to all stakeholders
</li>
<li>
- Conduct a release retrospective with all the Development Teams that participated in the program to improve the
+ Conduct a release retrospective with all the development team members that participated in the program to improve the
release process and increase program productivity and product quality
</li>
</ul></mainDescription>
diff --git a/epf_prac_151/core.default.role_def.base/roles/product_owner.xmi b/epf_prac_151/core.default.role_def.base/roles/product_owner.xmi
index d6144cd..d018284 100644
--- a/epf_prac_151/core.default.role_def.base/roles/product_owner.xmi
+++ b/epf_prac_151/core.default.role_def.base/roles/product_owner.xmi
@@ -2,7 +2,7 @@
<org.eclipse.epf.uma:RoleDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-Mcx6tqWLjhR3Dd12ad3EsQ" name="product_owner,_ob1d4EuUEeCsWoZ6ZH16Zg" guid="-Mcx6tqWLjhR3Dd12ad3EsQ" changeDate="2011-10-13T09:55:47.374-0600" version="7.5.1">
<mainDescription><p>
This role is the one and only person responsible for managing the Product Backlog and ensuring the value of the work
- the Development Team performs. The Product Owner has the responsibility of defining what is the right product to build,
+ the development team performs. The Product Owner has the responsibility of defining what is the right product to build,
determining the order in which features will be built, and making sure that the product actually works. The Product
Owner is responsible for defining the features of the product to be developed by the team in terms of:
</p>
@@ -46,7 +46,7 @@
</ul>
<p>
This person maintains the Product Backlog and ensures that it is visible to everyone. Everyone understands what items
- have the highest priority, so everyone on the Development Team knows what will be worked on.
+ have the highest priority, so everyone on the development Team knows what will be worked on.
</p>
<p>
The Product Owner is one person, not a committee. Committees may exist that advise or influence this person but team
@@ -55,18 +55,18 @@
</p>
<p>
For the Product Owner to succeed, everyone in the organization must respect their decisions. No one is allowed to
- direct the Development Team to work from a different set of priorities. Team members are not allowed to follow the direction
+ direct the development team member to work from a different set of priorities. Team members are not allowed to follow the direction
of anyone whose direction does not coincide with the direction provided by the Product Owner. The Product Owner’s
decisions are visible in the content and prioritization of the Product Backlog. This visibility requires that the
Product Owner do their best. Visibility makes the role of Product Owner both a demanding and a rewarding experience.
</p>
<p>
- The Product Owner is responsible for the first of the three Scrum ceremonies, Sprint/Iteration Planning. The Development Team evaluates
+ The Product Owner is responsible for the first of the three Scrum ceremonies, Sprint/Iteration Planning. The development team evaluates
the prioritized Product Backlog, identifies the top priority items, and commits to completing the selected items during
a Sprint/Iteration. These items become the basis for the Sprint/Iteration Backlog.
</p>
<p>
- In return for the Development Team's commitment to completing the selected tasks, the Product Owner commits that they will
+ In return for the development team's commitment to completing the selected tasks, the Product Owner commits that they will
not introduce new requirements to the team during the Sprint/Iteration. Requirements are allowed to change but only outside the
Sprint/Iteration. After the team begins a Sprint/Iteration, it remains focused on the goals of that Sprint/Iteration. The only exception to this
rule is that a similar amount of work can be removed from a Sprint/Iteration to accommodate a new requirement.
@@ -82,7 +82,7 @@
Good knowledge of the business domain
</li>
<li>
- Demonstrate leadership and be respected by external Stakeholders (Customers and users)
+ Demonstrate leadership and be respected by external stakeholders (Customers and users)
</li>
<li>
Make decisions at the right time (not too soon, not too late)
@@ -98,8 +98,8 @@
A former Business Analyst or Project Manager is a good candidate for this role.
</p></skills>
<assignmentApproaches><p>
- Only one person can play this role for each Development Team. This person must be assigned to the project (the Product
- Owner is a member of the Development Team and should participate in the Daily Stand-up meeting). The workload
+ Only one person can play this role for each development team. This person must be assigned to the project (the Product
+ Owner is a member of the development team and should participate in the Daily Stand-up meeting). The workload
associated with this role almost requires a full-time assignment.
</p>
<p>
@@ -126,7 +126,7 @@
<ul>
<li>
The Product Owner can be a Team member, and in addition perform development work. This additional responsibility
- may affect the Product Owner’s ability to work with Stakeholders. However, the Product Owner can never be the
+ may affect the Product Owner’s ability to work with stakeholders. However, the Product Owner can never be the
ScrumMaster.
</li>
<li>
diff --git a/epf_prac_151/core.default.role_def.base/roles/technical_writer.xmi b/epf_prac_151/core.default.role_def.base/roles/technical_writer.xmi
index 8dbb0c8..95fbf45 100644
--- a/epf_prac_151/core.default.role_def.base/roles/technical_writer.xmi
+++ b/epf_prac_151/core.default.role_def.base/roles/technical_writer.xmi
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:RoleDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-OW9Mlf5qrIMlT-E_1TEn2A" name="technical_writer,_-zf1teB8EeC1y_NExchKwQ" guid="-OW9Mlf5qrIMlT-E_1TEn2A" changeDate="2011-10-13T07:00:11.197-0600" version="7.5.1">
<mainDescription><p>
- Some organizations might engage a Technical Writer to help a Development Team review and refine the documentation that
+ Some organizations might engage a Technical Writer to help a development team member review and refine the documentation that
is produced by the team during a Sprint/Iteration in support of delivered features.
</p>
<p>
@@ -27,7 +27,7 @@
</li>
<li>
Ability to adhere to corporate documentation standards. If those standards don't already exist, this role should be
- able to write those standards and communicate them to the Development Team
+ able to write those standards and communicate them to the development team
</li>
<li>
A strong understand of the domain in which the features are being developed
diff --git a/epf_prac_151/core.default.role_def.base/roles/trainer.xmi b/epf_prac_151/core.default.role_def.base/roles/trainer.xmi
index c1fd87b..a66b400 100644
--- a/epf_prac_151/core.default.role_def.base/roles/trainer.xmi
+++ b/epf_prac_151/core.default.role_def.base/roles/trainer.xmi
@@ -3,7 +3,7 @@
<mainDescription>Many organizations engage Trainers to deliver product training to various audiences. Unlike a software Developer, most
Trainers have extensive experience in delivering training materials in a fashion that is well suited to communicating
complex concepts to End Users. They bring a necessary creativity and talent that complements the implementation and testing
-skills of a Development Team.</mainDescription>
+skills of a development team.</mainDescription>
<skills><p>
A Trainer should possess the following skills:
</p>
diff --git a/epf_prac_151/core.tech.common.extend_supp/guidances/checklists/vision.xmi b/epf_prac_151/core.tech.common.extend_supp/guidances/checklists/vision.xmi
index c4bd497..9ec7b02 100644
--- a/epf_prac_151/core.tech.common.extend_supp/guidances/checklists/vision.xmi
+++ b/epf_prac_151/core.tech.common.extend_supp/guidances/checklists/vision.xmi
@@ -2,7 +2,7 @@
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="_qktWQMM0EdmSIPI87WLu3g" name="vision,_0WoFUMlgEdmt3adZL5Dmdw" guid="_qktWQMM0EdmSIPI87WLu3g" changeDate="2005-07-07T01:30:32.000-0700" version="1.0.0">
<sections xmi:id="_VwoioAeiEduWycDgioo5rg" name="The problem behind the problem has been fully explored" guid="_VwoioAeiEduWycDgioo5rg">
<sectionDescription><p>
- Make sure that you have found the root cause of the Stakeholder's problem or need. Often, Stakeholders define solutions
+ Make sure that you have found the root cause of the stakeholder's problem or need. Often, stakeholders define solutions
rather than stating the problem that they are experiencing or the pain they are experiencing. Subsequently, they may
not have identified the problem correctly or the correct solution for it.
</p>
@@ -13,8 +13,8 @@
<sections xmi:id="_dBs8gAeiEduWycDgioo5rg" name="The problem statement is correctly formulated" guid="_dBs8gAeiEduWycDgioo5rg">
<sectionDescription>Make sure that you have agreement on the problem to be solved.</sectionDescription>
</sections>
- <sections xmi:id="_jGUxYAeiEduWycDgioo5rg" name="The list of Stakeholders is complete and correct" guid="_jGUxYAeiEduWycDgioo5rg">
- <sectionDescription>Make sure you didn't miss any Stakeholders. If you did, you probably do not yet have all of the perspectives that you need
+ <sections xmi:id="_jGUxYAeiEduWycDgioo5rg" name="The list of stakeholders is complete and correct" guid="_jGUxYAeiEduWycDgioo5rg">
+ <sectionDescription>Make sure you didn't miss any stakeholders. If you did, you probably do not yet have all of the perspectives that you need
to consider.</sectionDescription>
</sections>
<sections xmi:id="_s-be8AeiEduWycDgioo5rg" name="Everyone agrees on the definition of the system boundaries" guid="_s-be8AeiEduWycDgioo5rg">
diff --git a/epf_prac_151/practice.gen.doc_trng.base/guidances/practices/documentation_and_training.xmi b/epf_prac_151/practice.gen.doc_trng.base/guidances/practices/documentation_and_training.xmi
index 49c4b6d..0018d7e 100644
--- a/epf_prac_151/practice.gen.doc_trng.base/guidances/practices/documentation_and_training.xmi
+++ b/epf_prac_151/practice.gen.doc_trng.base/guidances/practices/documentation_and_training.xmi
@@ -8,7 +8,7 @@
</p>
<p>
By playing to the strengths and availability of Technical Writers, Course Developers,&nbsp;and Trainers, a Development
- Team does not need to worry about who will write the user documents and train End Users - in this case, they can have
+ Team does not need to worry about who will write the user documents and train end users - in this case, they can have
the specialists accept those responsibilities. Also, working with these two specialists ultimately will improve the
development team's ability to articulate details of the system that they are building and provide insight into subtle
ways to better comment and document their code.
@@ -20,14 +20,14 @@
benefit from the application are not fully informed or trained.
</p>
<p>
- Although this practice is documented and adopted at the Development Team level, in some organizations it may be
+ Although this practice is documented and adopted at the development team level, in some organizations it may be
advantageous to consolidate and integrate all types of documentation and training materials at the program level and
- deliver one comprehensive package to Stakeholders, End Users, and IT operations support personnel for the entire
+ deliver one comprehensive package to stakeholders, end users, and IT operations support personnel for the entire
release across the program.
</p></mainDescription>
<problem><p>
The purpose of this practice is to harden the product before a release by documenting key aspects for use by multiple
- audiences and by providing training to End Users who will take delivery of the product when it is released.
+ audiences and by providing training to end users who will take delivery of the product when it is released.
</p></problem>
<application><p>
With this practice, basic guidance regarding <em>how</em> to develop documentation and training, and more importantly
diff --git a/epf_prac_151/practice.gen.doc_trng.base/guidances/roadmaps/how_to_adopt_doc_training.xmi b/epf_prac_151/practice.gen.doc_trng.base/guidances/roadmaps/how_to_adopt_doc_training.xmi
index 496687d..ff71623 100644
--- a/epf_prac_151/practice.gen.doc_trng.base/guidances/roadmaps/how_to_adopt_doc_training.xmi
+++ b/epf_prac_151/practice.gen.doc_trng.base/guidances/roadmaps/how_to_adopt_doc_training.xmi
@@ -4,7 +4,7 @@
Getting started
</h3>
<p>
- The goal of the Documentation and Training practice is to ensure that End Users of a product receive quality
+ The goal of the Documentation and Training practice is to ensure that end users of a product receive quality
information about the product (in comprehensive documentation) and have been adequately trained regarding how to use
the product.
</p>
@@ -15,15 +15,15 @@
<li>
<strong>Inadequate documentation:</strong> No one likes to rigorously document a product, least of all the team
members who developed it. Historically, product documentation often has been an afterthought, if given thought at
- all. In the Agile world, because the goal is to deliver high quality, working software to End Users more quickly,
- realize that part of the quality component is adequate documentation that enables End Users to use the product more
+ all. In the Agile world, because the goal is to deliver high quality, working software to end users more quickly,
+ realize that part of the quality component is adequate documentation that enables end users to use the product more
effectively.
</li>
<li>
<strong>Non-existent or inadequate training:</strong> Like documentation, training often is an afterthought. When
product budgets are reduced, training often is the first line item to be eliminated. However, in fairness to the
- End User community, proper training about how to use the product is critical to the overall success of product
- deployment in terms of enabling End Users do their jobs effectively.
+ end user community, proper training about how to use the product is critical to the overall success of product
+ deployment in terms of enabling end users do their jobs effectively.
</li>
</ul>
<h3>
diff --git a/epf_prac_151/practice.gen.doc_trng.base/plugin.xmi b/epf_prac_151/practice.gen.doc_trng.base/plugin.xmi
index 58ac358..a1396ff 100644
--- a/epf_prac_151/practice.gen.doc_trng.base/plugin.xmi
+++ b/epf_prac_151/practice.gen.doc_trng.base/plugin.xmi
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1">
+<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1">
<org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_wDcysOCFEeC1y_NExchKwQ" guid="_wDcysOCFEeC1y_NExchKwQ">
<resourceDescriptors xmi:id="_BhTfwOB9EeC1y_NExchKwQ" id="-jWMpCvzhJPOglJcxCiAYjA" uri="tasks/develop_support_documentation.xmi"/>
<resourceDescriptors xmi:id="_BiH_IOB9EeC1y_NExchKwQ" id="-xCz7FMvINdv3zLvonMDolQ" uri="tasks/deliver_support_training.xmi"/>
@@ -42,27 +42,28 @@
<methodElementProperty xmi:id="_dKj_QJifEeGlkdGl1HQlDA" name="me_edited" value="true"/>
<presentation xmi:id="-Msu85VH5rLUfl0OEAnZdIQ" href="uma://-Msu85VH5rLUfl0OEAnZdIQ#-Msu85VH5rLUfl0OEAnZdIQ"/>
</contentElements>
- <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_-zfOp-B8EeC1y_NExchKwQ" name="develop_support_documentation" guid="_-zfOp-B8EeC1y_NExchKwQ" presentationName="Develop Support Documentation" briefDescription="This type of documentation is used by production support and IT operations personnel on a regular basis to answer End Users' questions about a particular product, to troubleshoot issues, or to determine if an incident is a result of a defect or missed requirements." output="_-zfOreB8EeC1y_NExchKwQ" optionalInput="_-zf1tuB8EeC1y_NExchKwQ _-zf1tOB8EeC1y_NExchKwQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_-zfOp-B8EeC1y_NExchKwQ" name="develop_support_documentation" guid="_-zfOp-B8EeC1y_NExchKwQ" presentationName="Develop Support Documentation" briefDescription="This type of documentation is used by production support and IT operations personnel on a regular basis to answer end users' questions about a particular product, to troubleshoot issues, or to determine if an incident is a result of a defect or missed requirements." output="_-zfOreB8EeC1y_NExchKwQ" optionalInput="_-zf1tuB8EeC1y_NExchKwQ _-zf1tOB8EeC1y_NExchKwQ">
<methodElementProperty xmi:id="_fZdfwJifEeGlkdGl1HQlDA" name="me_edited" value="true"/>
<presentation xmi:id="-jWMpCvzhJPOglJcxCiAYjA" href="uma://-jWMpCvzhJPOglJcxCiAYjA#-jWMpCvzhJPOglJcxCiAYjA"/>
</contentElements>
- <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_-zfOoOB8EeC1y_NExchKwQ" name="develop_user_documentation" guid="_-zfOoOB8EeC1y_NExchKwQ" presentationName="Develop User Documentation" briefDescription="User documentation must be developed and maintained for each Release so that the product's End Users will know how to operate the system effectively." output="_-zf1tOB8EeC1y_NExchKwQ" optionalInput="_-zf1tuB8EeC1y_NExchKwQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_-zfOoOB8EeC1y_NExchKwQ" name="develop_user_documentation" guid="_-zfOoOB8EeC1y_NExchKwQ" presentationName="Develop User Documentation" briefDescription="User documentation must be developed and maintained for each Release so that the product's end users will know how to operate the system effectively." output="_-zf1tOB8EeC1y_NExchKwQ" optionalInput="_-zf1tuB8EeC1y_NExchKwQ">
<methodElementProperty xmi:id="_hko94JifEeGlkdGl1HQlDA" name="me_edited" value="true"/>
<presentation xmi:id="-bkoNpaQhWX6FBG-iOZkRPg" href="uma://-bkoNpaQhWX6FBG-iOZkRPg#-bkoNpaQhWX6FBG-iOZkRPg"/>
</contentElements>
<contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_-zf1tuB8EeC1y_NExchKwQ" name="product_documentation" guid="_-zf1tuB8EeC1y_NExchKwQ" presentationName="Product Documentation" briefDescription="Information about a specific product that has been captured in an organized format.">
+ <methodElementProperty xmi:id="_EPOVcKqaEeGLQ_Sv1UBWjg" name="me_edited" value="true"/>
<presentation xmi:id="-NHao3cbpesderphl_fDlDw" href="uma://-NHao3cbpesderphl_fDlDw#-NHao3cbpesderphl_fDlDw"/>
</contentElements>
<contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_-zfOreB8EeC1y_NExchKwQ" name="support_documentation" guid="_-zfOreB8EeC1y_NExchKwQ" presentationName="Support Documentation" briefDescription="Documents used by members of a production support team that provide information about how to service and support a specific product.">
<presentation xmi:id="--5bZB7Fly_OXGWALfR7CCA" href="uma://--5bZB7Fly_OXGWALfR7CCA#--5bZB7Fly_OXGWALfR7CCA"/>
</contentElements>
- <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_-zf1tOB8EeC1y_NExchKwQ" name="user_documentation" guid="_-zf1tOB8EeC1y_NExchKwQ" presentationName="User Documentation" briefDescription="Documents that can be utilized by the End Users of a particular system or product. This type of documentation typically is written in a way that enables system users to easily find information they need to use the product.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_-zf1tOB8EeC1y_NExchKwQ" name="user_documentation" guid="_-zf1tOB8EeC1y_NExchKwQ" presentationName="User Documentation" briefDescription="Documents that can be utilized by the end users of a particular system or product. This type of documentation typically is written in a way that enables system users to easily find information they need to use the product.">
<presentation xmi:id="-SLpYMg7H4HpPFh-tX5CqoA" href="uma://-SLpYMg7H4HpPFh-tX5CqoA#-SLpYMg7H4HpPFh-tX5CqoA"/>
</contentElements>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_-zeAgeB8EeC1y_NExchKwQ" name="training" guid="_-zeAgeB8EeC1y_NExchKwQ">
<methodElementProperty xmi:id="_lGsIUJifEeGlkdGl1HQlDA" name="me_edited" value="true"/>
- <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_-zenmeB8EeC1y_NExchKwQ" name="develop_training_materials" guid="_-zenmeB8EeC1y_NExchKwQ" presentationName="Develop Training Materials" briefDescription="This task is used to develop quality audio/visual materials that can be used to train End Users and IT production support personnel." output="_-zeAguB8EeC1y_NExchKwQ" optionalInput="_-zf1tuB8EeC1y_NExchKwQ _-zfOreB8EeC1y_NExchKwQ _-zf1tOB8EeC1y_NExchKwQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_-zenmeB8EeC1y_NExchKwQ" name="develop_training_materials" guid="_-zenmeB8EeC1y_NExchKwQ" presentationName="Develop Training Materials" briefDescription="This task is used to develop quality audio/visual materials that can be used to train end users and IT production support personnel." output="_-zeAguB8EeC1y_NExchKwQ" optionalInput="_-zf1tuB8EeC1y_NExchKwQ _-zfOreB8EeC1y_NExchKwQ _-zf1tOB8EeC1y_NExchKwQ">
<methodElementProperty xmi:id="_q_ZBEJifEeGlkdGl1HQlDA" name="me_edited" value="true"/>
<presentation xmi:id="-IfcWgUklth25pRzdNTE8LA" href="uma://-IfcWgUklth25pRzdNTE8LA#-IfcWgUklth25pRzdNTE8LA"/>
</contentElements>
@@ -70,15 +71,16 @@
<methodElementProperty xmi:id="_q__eAJifEeGlkdGl1HQlDA" name="me_edited" value="true"/>
<presentation xmi:id="-xCz7FMvINdv3zLvonMDolQ" href="uma://-xCz7FMvINdv3zLvonMDolQ#-xCz7FMvINdv3zLvonMDolQ"/>
</contentElements>
- <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_-zeAg-B8EeC1y_NExchKwQ" name="deliver_end_user_training" guid="_-zeAg-B8EeC1y_NExchKwQ" presentationName="Deliver End User Training" briefDescription="In most cases, End Users of a system require training to use the application effectively." mandatoryInput="_-zf1tOB8EeC1y_NExchKwQ _-zeAguB8EeC1y_NExchKwQ" optionalInput="_-zf1tuB8EeC1y_NExchKwQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_-zeAg-B8EeC1y_NExchKwQ" name="deliver_end_user_training" guid="_-zeAg-B8EeC1y_NExchKwQ" presentationName="Deliver end user Training" briefDescription="In most cases, end users of a system require training to use the application effectively." mandatoryInput="_-zf1tOB8EeC1y_NExchKwQ _-zeAguB8EeC1y_NExchKwQ" optionalInput="_-zf1tuB8EeC1y_NExchKwQ">
<methodElementProperty xmi:id="_rAIn8JifEeGlkdGl1HQlDA" name="me_edited" value="true"/>
<presentation xmi:id="-w4UHaO9nSn7-q_CMq-Ofog" href="uma://-w4UHaO9nSn7-q_CMq-Ofog#-w4UHaO9nSn7-q_CMq-Ofog"/>
</contentElements>
- <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_-zeAguB8EeC1y_NExchKwQ" name="training_materials" guid="_-zeAguB8EeC1y_NExchKwQ" presentationName="Training Materials" briefDescription="This work product represents all the materials needed to train End Users and production support personnel on the features and inner workings of a product for a particular Release.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_-zeAguB8EeC1y_NExchKwQ" name="training_materials" guid="_-zeAguB8EeC1y_NExchKwQ" presentationName="Training Materials" briefDescription="This work product represents all the materials needed to train end users and production support personnel on the features and inner workings of a product for a particular release.">
+ <methodElementProperty xmi:id="_K5L2kKqbEeGLQ_Sv1UBWjg" name="me_edited" value="true"/>
<presentation xmi:id="-U5rK8ue_5v305MPzxKzQUg" href="uma://-U5rK8ue_5v305MPzxKzQUg#-U5rK8ue_5v305MPzxKzQUg"/>
</contentElements>
</childPackages>
- <contentElements xsi:type="org.eclipse.epf.uma:Practice" xmi:id="_-zdZceB8EeC1y_NExchKwQ" name="documentation_and_training" guid="_-zdZceB8EeC1y_NExchKwQ" presentationName="Documentation and Training" briefDescription="This practice describes how to prepare documentation for a product release and how that documentation might be used to prepare and deliver training to End Users and support personnel.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Practice" xmi:id="_-zdZceB8EeC1y_NExchKwQ" name="documentation_and_training" guid="_-zdZceB8EeC1y_NExchKwQ" presentationName="Documentation and Training" briefDescription="This practice describes how to prepare documentation for a product release and how that documentation might be used to prepare and deliver training to end users and support personnel.">
<methodElementProperty xmi:id="_Bao3EOB9EeC1y_NExchKwQ" name="CategoryElementsSortType" value="Manual"/>
<presentation xmi:id="-cPtDc656Hgw9PuzWPtV8Iw" href="uma://-cPtDc656Hgw9PuzWPtV8Iw#-cPtDc656Hgw9PuzWPtV8Iw"/>
<contentReferences xsi:type="org.eclipse.epf.uma:Artifact" href="#_-zf1tuB8EeC1y_NExchKwQ"/>
diff --git a/epf_prac_151/practice.gen.doc_trng.base/roles/course_developer.xmi b/epf_prac_151/practice.gen.doc_trng.base/roles/course_developer.xmi
index e3391fc..f9931a1 100644
--- a/epf_prac_151/practice.gen.doc_trng.base/roles/course_developer.xmi
+++ b/epf_prac_151/practice.gen.doc_trng.base/roles/course_developer.xmi
@@ -2,8 +2,8 @@
<org.eclipse.epf.uma:RoleDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-C6ZZTqQccgTUpiCA8BWeKg" name="course_developer,_cQjSAPWkEeC0T_-ipt2c0Q" guid="-C6ZZTqQccgTUpiCA8BWeKg" changeDate="2011-10-13T08:09:19.045-0600" version="7.5.1">
<mainDescription>Many organizations engage Course Developers to develop product training&nbsp;materials for various audiences. Unlike a
software Developer, most Course Developers have extensive experience in creating training materials that are well suited to
-communicating complex concepts to End Users. They bring a necessary creativity and talent that complements the
-implementation and testing skills of a Development Team.</mainDescription>
+communicating complex concepts to end users. They bring a necessary creativity and talent that complements the
+implementation and testing skills of a development team.</mainDescription>
<skills><p>
A Course Developer should possess the following skills:
</p>
diff --git a/epf_prac_151/practice.gen.doc_trng.base/tasks/deliver_end_user_training.xmi b/epf_prac_151/practice.gen.doc_trng.base/tasks/deliver_end_user_training.xmi
index ffb89d8..fa70ebe 100644
--- a/epf_prac_151/practice.gen.doc_trng.base/tasks/deliver_end_user_training.xmi
+++ b/epf_prac_151/practice.gen.doc_trng.base/tasks/deliver_end_user_training.xmi
@@ -1,17 +1,17 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-w4UHaO9nSn7-q_CMq-Ofog" name="02_02_deliver_end_user_training,_nnueQ2zvEeCPgecPbK9bdg" guid="-w4UHaO9nSn7-q_CMq-Ofog" changeDate="2011-07-19T22:37:13.291-0700" version="7.5.1">
+<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-w4UHaO9nSn7-q_CMq-Ofog" name="02_02_deliver_end_user_training,_nnueQ2zvEeCPgecPbK9bdg" guid="-w4UHaO9nSn7-q_CMq-Ofog" changeDate="2012-05-30T13:58:23.423-0700" version="7.5.1">
<mainDescription><p>
- Often, a Trainer will deliver training to End Users; rarely will the Development Team deliver training because they are
- busy developing additional features for this or other systems. If a Trainer is not available, the Product Owner might
- have to train the End Users.
+ Often, a trainer will deliver training to end users; rarely will the development team deliver training because they are
+ busy developing additional features for this or other systems. If a trainer is not available, the product owner might
+ have to train the end users.
</p>
<p>
- End User training usually consists of presentation slides, job aids, hands-on labs and exercises, or workshops that
- integrate these methods into an environment that the End Users can understand and relate to.
+ End user training usually consists of presentation slides, job aids, hands-on labs and exercises, or workshops that
+ integrate these methods into an environment that the end users can understand and relate to.
</p></mainDescription>
- <sections xmi:id="_-zeAhOB8EeC1y_NExchKwQ" name="Validate User Training Logistics" guid="_-zeAhOB8EeC1y_NExchKwQ">
+ <sections xmi:id="_-zeAhOB8EeC1y_NExchKwQ" name="Validate user training logistics" guid="_-zeAhOB8EeC1y_NExchKwQ">
<sectionDescription><p>
- Before actually delivering the training to End Users, ensure that you have all the necessary components of the training
+ Before actually delivering the training to end users, ensure that you have all the necessary components of the training
course, including:
</p>
<ul>
@@ -40,21 +40,21 @@
audience. If possible, send a reminder notice to the attendees several days (or a week) before the delivery date.
</p></sectionDescription>
</sections>
- <sections xmi:id="_-zenkuB8EeC1y_NExchKwQ" name="Prepare for User Training Delivery" guid="_-zenkuB8EeC1y_NExchKwQ">
+ <sections xmi:id="_-zenkuB8EeC1y_NExchKwQ" name="Prepare for user training delivery" guid="_-zenkuB8EeC1y_NExchKwQ">
<sectionDescription>Review the training materials so that you are familiar with them. If you encounter any areas in which you are unsure or
-tentative about, engage experts from the Development Team or program who can help you understand the material. Then, update
+tentative about, engage experts from the development team or program who can help you understand the material. Then, update
the training materials accordingly and create instructor notes to help you remember key points as you deliver the training.
Instructor notes that you author will not only help you, but they might assist other instructors in the future who have not
-had the benefit of working with the Development Team or program.</sectionDescription>
+had the benefit of working with the development team or program.</sectionDescription>
</sections>
- <sections xmi:id="_-zenkeB8EeC1y_NExchKwQ" name="Deliver User Training and Gather Feedback" guid="_-zenkeB8EeC1y_NExchKwQ">
+ <sections xmi:id="_-zenkeB8EeC1y_NExchKwQ" name="Deliver user training and gather feedback" guid="_-zenkeB8EeC1y_NExchKwQ">
<sectionDescription>On the prescribed day(s) and time(s), deliver the training as planned. When each course is completed, solicit feedback from
the attendees on the course material, its organization and flow, the learning objectives, how well the instructor delivered
the content, and whether the course met their expectations.</sectionDescription>
</sections>
- <sections xmi:id="_-zenkOB8EeC1y_NExchKwQ" name="Provide Feedback to the Program Level" guid="_-zenkOB8EeC1y_NExchKwQ">
- <sectionDescription>Consolidate the feedback from the courses delivered and provide it to the Program Manager or their delegate for review.</sectionDescription>
+ <sections xmi:id="_-zenkOB8EeC1y_NExchKwQ" name="Provide feedback to the program level" guid="_-zenkOB8EeC1y_NExchKwQ">
+ <sectionDescription>Consolidate the feedback from the courses delivered and provide it to the program manager or their delegate for review.</sectionDescription>
</sections>
- <purpose>The purpose of this task is to ensure that End Users are properly trained to use the system to achieve the maximum business
+ <purpose>The purpose of this task is to ensure that end users are properly trained to use the system to achieve the maximum business
value.</purpose>
</org.eclipse.epf.uma:TaskDescription>
diff --git a/epf_prac_151/practice.gen.doc_trng.base/tasks/deliver_support_training.xmi b/epf_prac_151/practice.gen.doc_trng.base/tasks/deliver_support_training.xmi
index 8f8d5d8..99aba7f 100644
--- a/epf_prac_151/practice.gen.doc_trng.base/tasks/deliver_support_training.xmi
+++ b/epf_prac_151/practice.gen.doc_trng.base/tasks/deliver_support_training.xmi
@@ -1,16 +1,16 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-xCz7FMvINdv3zLvonMDolQ" name="03_deliver_support_training,_YryeIDHNEeC7j_IRiP-WPQ" guid="-xCz7FMvINdv3zLvonMDolQ" changeDate="2011-04-11T21:02:21.943-0700" version="7.5.1">
+<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-xCz7FMvINdv3zLvonMDolQ" name="03_deliver_support_training,_YryeIDHNEeC7j_IRiP-WPQ" guid="-xCz7FMvINdv3zLvonMDolQ" changeDate="2012-05-30T14:00:22.183-0700" version="7.5.1">
<mainDescription><p>
- Because a Release ultimately will have to be supported by Help Desk or other technical personnel, a set of training
- materials designed to convey key concepts to those individuals must be developed and delivered by the&nbsp;Development
- Team or by a technically oriented Trainer.
+ Because a release ultimately will have to be supported by Help Desk or other technical personnel, a set of training
+ materials designed to convey key concepts to those individuals must be developed and delivered by the&nbsp;development
+ team or by a technically oriented trainer.
</p>
<p>
Delivery of this training might include presentation slides, job aids, lab exercises, or workshops designed to provide
real-world scenarios to accelerate learning and retention. In addition, the training materials might be different for
each level (tier) of support.
</p></mainDescription>
- <sections xmi:id="_-zenmOB8EeC1y_NExchKwQ" name="Validate Support Training Logistics" guid="_-zenmOB8EeC1y_NExchKwQ">
+ <sections xmi:id="_-zenmOB8EeC1y_NExchKwQ" name="Validate support training logistics" guid="_-zenmOB8EeC1y_NExchKwQ">
<sectionDescription><p>
Before actually delivering the training to support personnel, ensure that you have all the necessary components of the
training course, including:
@@ -42,20 +42,20 @@
date.
</p></sectionDescription>
</sections>
- <sections xmi:id="_-zenl-B8EeC1y_NExchKwQ" name="Prepare for Support Training Delivery" guid="_-zenl-B8EeC1y_NExchKwQ">
+ <sections xmi:id="_-zenl-B8EeC1y_NExchKwQ" name="Prepare for support training delivery" guid="_-zenl-B8EeC1y_NExchKwQ">
<sectionDescription>Review the training materials so that you are familiar with them. If you encounter any areas where you are unsure or
-tentative, engage experts from the Development Team or program who can help you understand the material. Then, update the
+tentative, engage experts from the development team or program who can help you understand the material. Then, update the
training materials accordingly and create instructor notes to help you remember key points as you deliver the training.
Instructor notes that you write will not only help you but might assist other instructors in the future who have not had
-the benefit of working with the Development Team or program.</sectionDescription>
+the benefit of working with the development team or program.</sectionDescription>
</sections>
- <sections xmi:id="_-zenluB8EeC1y_NExchKwQ" name="Deliver Support Training and Gather Feedback" guid="_-zenluB8EeC1y_NExchKwQ">
+ <sections xmi:id="_-zenluB8EeC1y_NExchKwQ" name="deliver support training and gather feedback" guid="_-zenluB8EeC1y_NExchKwQ">
<sectionDescription>On the prescribed day(s) and time(s), deliver the training as planned. When each course is completed, solicit feedback from
the attendees about the course material, its organization and flow, the learning objectives, how well the instructor
delivered the content, and whether the course met their expectations.</sectionDescription>
</sections>
- <sections xmi:id="_-zenleB8EeC1y_NExchKwQ" name="Provide Feedback to the Program Level" guid="_-zenleB8EeC1y_NExchKwQ">
- <sectionDescription>Consolidate the feedback from the courses delivered and provide it to the Program Manager or their delegate for review.</sectionDescription>
+ <sections xmi:id="_-zenleB8EeC1y_NExchKwQ" name="Provide feedback to the program" guid="_-zenleB8EeC1y_NExchKwQ">
+ <sectionDescription>Consolidate the feedback from the courses delivered and provide it to the program manager or their delegate for review.</sectionDescription>
</sections>
<purpose>The purpose of this task is to provide personnel at all levels of support (Tiers 1, 2, and 3) with the appropriate amount
of training on the features that are being delivered as part of a specific Release.</purpose>
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 a3fe39f..191760a 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
@@ -1,49 +1,41 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-Msu85VH5rLUfl0OEAnZdIQ" name="01_create_update_product_documenation,_t15g4DHMEeC7j_IRiP-WPQ" guid="-Msu85VH5rLUfl0OEAnZdIQ" changeDate="2011-08-25T15:03:16.508-0700" version="7.5.1">
+<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-Msu85VH5rLUfl0OEAnZdIQ" name="01_create_update_product_documenation,_t15g4DHMEeC7j_IRiP-WPQ" guid="-Msu85VH5rLUfl0OEAnZdIQ" changeDate="2012-05-30T13:03:23.148-0700" version="7.5.1">
<mainDescription><p>
- Development Team Members sometimes take documentation for granted, or do not give it enough consideration. However,
- after a product is delivered, Customers who pay for the system and for support often do not have enough information to
+ Development team members sometimes take documentation for granted, or do not give it enough consideration. However,
+ after a product is delivered, customers who pay for the system and for support often do not have enough information to
effectively manage the product.
</p>
<p>
- If a Technical Writer is made available to a Development Team, that role often takes the burden off the team for
+ If a technical writer is made available to a development team, that role often takes the burden off the team for
developing the formal product documentation and for ensuring that it is in the correct format and business language. If
- a Technical Writer is not available, the Development Team and Product Owner must make every effort to create enough
- documentation to ensure that the features that have been developed for each Release are understood and can be
- communicated effectively by the paying Customer to their Stakeholders.
+ a technical writer is not available, the development team and product owner must make every effort to create enough
+ documentation to ensure that the features that have been developed for each release are understood and can be
+ communicated effectively by the paying customer to their stakeholders.
</p>
<p>
- Delivering a professionally developed product requires that a Development Team provide the Customer with accurate,
+ Delivering a professionally developed product requires that a development team provide the customer with accurate,
detailed, and comprehensive product documentation.
</p></mainDescription>
- <sections xmi:id="_-zf1suB8EeC1y_NExchKwQ" name="Identify Features of Current Release" guid="_-zf1suB8EeC1y_NExchKwQ">
- <sectionDescription><p>
- Every release will contain a set of features that were developed during the preceding Feature Development
- Sprint/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>
- 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 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%<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%</p></sectionDescription>
</sections>
- <sections xmi:id="_-zf1seB8EeC1y_NExchKwQ" name="Document Each Feature" guid="_-zf1seB8EeC1y_NExchKwQ">
+ <sections xmi:id="_-zf1seB8EeC1y_NExchKwQ" name="Document each feature" guid="_-zf1seB8EeC1y_NExchKwQ">
<sectionDescription>Write a comprehensive description of each feature and include appropriate screen shots as well as relevant information
about how the feature was developed.</sectionDescription>
</sections>
- <sections xmi:id="_-zf1s-B8EeC1y_NExchKwQ" name="Review Product Documentation with Stakeholders" guid="_-zf1s-B8EeC1y_NExchKwQ">
- <sectionDescription>Schedule a review session with key Stakeholders to ensure that the product documentation is adequate and that it contains
-the level of detail needed by the product Customer. If more detail is required, elicit one or more examples from the
-Stakeholders that show how they would like the documentation to be prepared.</sectionDescription>
+ <sections xmi:id="_-zf1s-B8EeC1y_NExchKwQ" name="Review product documentation with stakeholders" guid="_-zf1s-B8EeC1y_NExchKwQ">
+ <sectionDescription>Schedule a review session with key stakeholders to ensure that the product documentation is adequate and that it contains
+the level of detail needed by the product customer. If more detail is required, elicit one or more examples from the
+stakeholders that show how they would like the documentation to be prepared.</sectionDescription>
</sections>
- <sections xmi:id="_-zfOr-B8EeC1y_NExchKwQ" name="Update Product Documentation as Necessary" guid="_-zfOr-B8EeC1y_NExchKwQ">
+ <sections xmi:id="_-zfOr-B8EeC1y_NExchKwQ" name="Update product documentation as necessary" guid="_-zfOr-B8EeC1y_NExchKwQ">
<sectionDescription>Based on the outcome of the review session, update the product documentation so that it can receive the proper approval on
delivery.</sectionDescription>
</sections>
- <sections xmi:id="_-zf1sOB8EeC1y_NExchKwQ" name="Deliver Product Documentation" guid="_-zf1sOB8EeC1y_NExchKwQ">
- <sectionDescription>For this Release, deliver the final product documentation to the Customer and key Stakeholders. Obtain their formal
+ <sections xmi:id="_-zf1sOB8EeC1y_NExchKwQ" name="Deliver product documentation" guid="_-zf1sOB8EeC1y_NExchKwQ">
+ <sectionDescription>For this release, deliver the final product documentation to the customer and key stakeholders. Obtain their formal
approval if necessary.</sectionDescription>
</sections>
<purpose>The purpose of this task is to document enough information about the features that were developed in a particular release
-to be useful to Customers throughout the life of the product.</purpose>
+to be useful to customers throughout the life of the product.</purpose>
</org.eclipse.epf.uma:TaskDescription>
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 b15d172..f45e511 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
@@ -1,21 +1,21 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-jWMpCvzhJPOglJcxCiAYjA" name="03_create_update_support_documenation,_nGAhcDHMEeC7j_IRiP-WPQ" guid="-jWMpCvzhJPOglJcxCiAYjA" changeDate="2011-08-25T15:21:46.686-0700" version="7.5.1">
+<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-jWMpCvzhJPOglJcxCiAYjA" name="03_create_update_support_documenation,_nGAhcDHMEeC7j_IRiP-WPQ" guid="-jWMpCvzhJPOglJcxCiAYjA" changeDate="2012-05-30T13:11:48.626-0700" version="7.5.1">
<mainDescription><p>
Support documentation often is the most overlooked aspect of a documentation effort. Anyone who has had the opportunity
- to provide End User support for a particular application can appreciate how important effective, well-written support
+ to provide end user support for a particular application can appreciate how important effective, well-written support
documentation can be. This documentation very often is technical in nature and differs significantly from user or
product documentation, which normally is written for the lay person.
</p>
<p>
- The Development Team should do its best to make sure that personnel who perform an IT support role have the right
+ The development team should do its best to make sure that personnel who perform an IT support role have the right
amount and the relevant type of information necessary to support the application, whether they provide Tier 1, Tier 2,
or Tier 3 support. Support documentation often is developed based on these three different support categories. How
effectively the code base is commented and the ease with which those comments are found and understood contributes to
the quality and quantity of support documentation.
</p></mainDescription>
- <sections xmi:id="_-zfOquB8EeC1y_NExchKwQ" name="Determine Support Documentation Contents" guid="_-zfOquB8EeC1y_NExchKwQ">
+ <sections xmi:id="_-zfOquB8EeC1y_NExchKwQ" name="Determine support documentation contents" guid="_-zfOquB8EeC1y_NExchKwQ">
<sectionDescription><p>
- This step is often challenging for Development Teams because they must put themselves in the position of IT support
+ This step is often challenging for development teams because they must put themselves in the position of IT support
personnel to develop the right kind and right amount of useful content. It is advantageous to visit the support
organization and ask them what types of documentation they would want delivered to them at each Release. You might be
surprised at what they say, and it could make your documentation tasks easier if you know exactly what type of
@@ -24,12 +24,12 @@
<p>
Because every product is different, and because each program or IT support organization has unique needs, it is
impossible to list recommended contents for support documentation. However, each program should create support
- documentation standards for the Development Teams that support its program.
+ documentation standards for the development teams that support its program.
</p></sectionDescription>
</sections>
- <sections xmi:id="_-zfOq-B8EeC1y_NExchKwQ" name="Leverage Available Materials" guid="_-zfOq-B8EeC1y_NExchKwQ">
+ <sections xmi:id="_-zfOq-B8EeC1y_NExchKwQ" name="Leverage available materials" guid="_-zfOq-B8EeC1y_NExchKwQ">
<sectionDescription><p>
- Use the Development Team's Release Plan as a mechanism to define the scope of the support documentation. Source
+ Use the development team's Release Plan as a mechanism to define the scope of the support documentation. Source
materials that can contribute effectively to support documentation content include:
</p>
<ul>
@@ -74,18 +74,14 @@
</li>
</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
-(determined in the step "Determine Support Documentation Contents" above) to Development Team Members as Sprint/Iteration
-Tasks in the Release Sprint/Iteration.</sectionDescription>
+ <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>
</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
-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 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>
</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
+ <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
a plan for communicating the support documentation to the IT operations support organization in a timely manner.</sectionDescription>
</sections>
<purpose>The purpose of this task is to ensure that the personnel who are tasked with supporting the system have enough information
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 b49e8ce..84ca0fb 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
@@ -1,52 +1,22 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-IfcWgUklth25pRzdNTE8LA" name="create_update_training_materials,_yJRakDHMEeC7j_IRiP-WPQ" guid="-IfcWgUklth25pRzdNTE8LA" changeDate="2011-10-13T07:12:09.267-0700" version="7.5.1">
+<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-IfcWgUklth25pRzdNTE8LA" name="create_update_training_materials,_yJRakDHMEeC7j_IRiP-WPQ" guid="-IfcWgUklth25pRzdNTE8LA" changeDate="2012-05-30T14:02:19.664-0700" version="7.5.1">
<mainDescription><p>
- Having the correct amount and type of materials available to adequately train End Users and supporters of an
- application is necessary to promote usability and to achieve the desired business value. If a Course Developer is
+ Having the correct amount and type of materials available to adequately train end users and supporters of an
+ application is necessary to promote usability and to achieve the desired business value. If a course ceveloper is
available, they can assume most of the burden of creating the training materials, lab exercises, and workshops&nbsp;for
- delivery of&nbsp;those courses to either End Users or support personnel. If a Course Developer is not
- available,&nbsp;Development Team Members should take the time to properly develop a suite of training materials for the
- feature set developed during a Release.
+ delivery of&nbsp;those courses to either end users or support personnel. If a course developer is not
+ available,&nbsp;development team members should take the time to properly develop a suite of training materials for the
+ feature set developed during a release.
</p>
<p>
- Although different parts of training materials should be created during Feature Development Sprint/Iterations, the bulk
- of the work (and the integration of the materials) usually is reserved for the Release Sprint/Iteration that occurs
- immediately before a scheduled Release.
+ Although different parts of training materials should be created during feature development sprint/iterations, the bulk
+ of the work (and the integration of the materials) usually is reserved for the release sprint/iteration that occurs
+ immediately before a scheduled release.
</p></mainDescription>
- <sections xmi:id="_-zennOB8EeC1y_NExchKwQ" name="Determine Scope of Training Materials" guid="_-zennOB8EeC1y_NExchKwQ">
- <sectionDescription><p>
- 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>
- Training materials generally consist of a combination of:
-</p>
-<ul>
- <li>
- Presentation slides
- </li>
- <li>
- Handouts
- </li>
- <li>
- Training aids
- </li>
- <li>
- Hands-on labs and/or exercises
- </li>
- <li>
- Quizzes or tests
- </li>
- <li>
- Practical application workshops
- </li>
-</ul>
-<p>
- Training materials often are grouped into modules, each with a set of learning objectives and competency assessments.
-</p></sectionDescription>
+ <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%<p>%EOL% Training materials generally consist of a combination of:%EOL%</p>%EOL%<ul>%EOL% <li>%EOL% Presentation slides%EOL% </li>%EOL% <li>%EOL% Handouts%EOL% </li>%EOL% <li>%EOL% Training aids%EOL% </li>%EOL% <li>%EOL% Hands-on labs and/or exercises%EOL% </li>%EOL% <li>%EOL% Quizzes or tests%EOL% </li>%EOL% <li>%EOL% Practical application workshops%EOL% </li>%EOL%</ul>%EOL%<p>%EOL% Training materials often are grouped into modules, each with a set of learning objectives and competency assessments.%EOL%</p></sectionDescription>
</sections>
- <sections xmi:id="_-zenm-B8EeC1y_NExchKwQ" name="Develop User Training Materials" guid="_-zenm-B8EeC1y_NExchKwQ">
+ <sections xmi:id="_-zenm-B8EeC1y_NExchKwQ" name="Develop user training materials" guid="_-zenm-B8EeC1y_NExchKwQ">
<sectionDescription><p>
Leverage all the user documentation that has been prepared previously or is in the process of being prepared. The table
of contents of the user documentation will provide a starting point for developing a training course framework and a
@@ -58,30 +28,17 @@
training modules.
</p></sectionDescription>
</sections>
- <sections xmi:id="_-zenmuB8EeC1y_NExchKwQ" name="Develop Support Training Materials" guid="_-zenmuB8EeC1y_NExchKwQ">
- <sectionDescription><p>
- 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>
- 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 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%<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%</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
-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 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>
</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
-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 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>
</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
+ <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
with the training materials from the other teams participating in the program.</sectionDescription>
</sections>
<purpose>The purpose of this task is to enable adoption of the product and to encourage its proper use.</purpose>
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 fa1e2ac..cb170b3 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
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-bkoNpaQhWX6FBG-iOZkRPg" name="create_update_user_documenation,_gMmZoDHMEeC7j_IRiP-WPQ" guid="-bkoNpaQhWX6FBG-iOZkRPg" changeDate="2011-09-12T08:48:05.139-0700" version="7.5.1">
+<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-bkoNpaQhWX6FBG-iOZkRPg" name="create_update_user_documenation,_gMmZoDHMEeC7j_IRiP-WPQ" guid="-bkoNpaQhWX6FBG-iOZkRPg" changeDate="2011-09-12T08:48:05.139-0700" version="7.5.1">
<mainDescription><p>
User documentation might include all or parts of user manuals (electronic or paper-based), tutorials, frequently asked
questions (FAQs), on-line Help Files, installation instructions, operational procedures, etc. User documentation often
@@ -7,45 +7,19 @@
be any better.
</p>
<p>
- Without good user documentation, a system might be well developed by a Development Team but might not meet the End
+ Without good user documentation, a system might be well developed by a development team but might not meet the End
User's expectations because they will not be able operate the application effectively.
</p></mainDescription>
- <sections xmi:id="_-zfOo-B8EeC1y_NExchKwQ" name="Determine User Documentation Contents" guid="_-zfOo-B8EeC1y_NExchKwQ">
- <sectionDescription><p>
- User documentation often consists of a wide variety of content such as:
-</p>
-<ul>
- <li>
- User manuals (electronic or paper-based)
- </li>
- <li>
- Tutorials
- </li>
- <li>
- Frequently asked questions (FAQs)
- </li>
- <li>
- On-line Help Files
- </li>
- <li>
- Installation and configuration instructions
- </li>
- <li>
- Operational procedures (or job aids)
- </li>
-</ul>
-<p>
- For your product and for this Release, determine which of these types of user documentation your team will develop and
- deliver.
-</p></sectionDescription>
+ <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%<ul>%EOL% <li>%EOL% User manuals (electronic or paper-based)%EOL% </li>%EOL% <li>%EOL% Tutorials%EOL% </li>%EOL% <li>%EOL% Frequently asked questions (FAQs)%EOL% </li>%EOL% <li>%EOL% On-line Help Files%EOL% </li>%EOL% <li>%EOL% Installation and configuration instructions%EOL% </li>%EOL% <li>%EOL% Operational procedures (or job aids)%EOL% </li>%EOL%</ul>%EOL%<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%</p></sectionDescription>
</sections>
- <sections xmi:id="_-zfOpeB8EeC1y_NExchKwQ" name="Leverage Product Documentation" guid="_-zfOpeB8EeC1y_NExchKwQ">
+ <sections xmi:id="_-zfOpeB8EeC1y_NExchKwQ" name="Leverage product documentation" guid="_-zfOpeB8EeC1y_NExchKwQ">
<sectionDescription>Re-use whatever material you can from the product documentation that your team has created. If adequate time and attention
was given to product documentation, you should be able to leverage a significant amount of it to develop the user
documentation. Because only features (and possibly some nonfunctional requirements) were documented for the product, only
that amount can be leveraged. However, it often provides a nice framework for the user documentation.</sectionDescription>
</sections>
- <sections xmi:id="_-zfOpOB8EeC1y_NExchKwQ" name="Leverage Other Materials" guid="_-zfOpOB8EeC1y_NExchKwQ">
+ <sections xmi:id="_-zfOpOB8EeC1y_NExchKwQ" name="Leverage other materials" guid="_-zfOpOB8EeC1y_NExchKwQ">
<sectionDescription><p>
Other materials developed in the course of the Release might provide excellent input into the user documentation such
as:
@@ -72,22 +46,22 @@
</ul>
<p>
Each of these may contain content that you do not need to re-create. Use your imagination to find other source
- materials that can help your team document the system for End Users.
+ materials that can help your team document the system for end users.
</p></sectionDescription>
</sections>
- <sections xmi:id="_-zfOouB8EeC1y_NExchKwQ" name="Write User Documentation Content" guid="_-zfOouB8EeC1y_NExchKwQ">
+ <sections xmi:id="_-zfOouB8EeC1y_NExchKwQ" name="Write user documentation content" guid="_-zfOouB8EeC1y_NExchKwQ">
<sectionDescription>Based on the previous steps, write the user documentation. One way to do this is to assign sections of the document
-(described in the step "Determine User Documentation Contents" above) to Development Team Members as Sprint/Iteration Tasks
+(described in the step "Determine User Documentation Contents" above) to Development team members as Sprint/Iteration Tasks
in the Release Sprint/Iteration.</sectionDescription>
</sections>
- <sections xmi:id="_-zfOoeB8EeC1y_NExchKwQ" name="Perform Quality Review" guid="_-zfOoeB8EeC1y_NExchKwQ">
+ <sections xmi:id="_-zfOoeB8EeC1y_NExchKwQ" name="Perform quality review" guid="_-zfOoeB8EeC1y_NExchKwQ">
<sectionDescription>As the user 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 user documentation based on the
results of the quality review.</sectionDescription>
</sections>
- <sections xmi:id="_-zfOpuB8EeC1y_NExchKwQ" name="Deliver User Documentation" guid="_-zfOpuB8EeC1y_NExchKwQ">
- <sectionDescription>Before or at the end of a Release, deliver the completed user documentation to the Deployment Manager. Ensure that the
-program has a plan for communicating the user documentation to End Users.</sectionDescription>
+ <sections xmi:id="_-zfOpuB8EeC1y_NExchKwQ" name="Deliver user documentation" guid="_-zfOpuB8EeC1y_NExchKwQ">
+ <sectionDescription>Before or at the end of a release, deliver the completed user documentation to the deployment manager. Ensure that the
+program has a plan for communicating the user documentation to end users.</sectionDescription>
</sections>
- <purpose>The purpose of this task is to provide useful information to End Users of the product being released into production.</purpose>
+ <purpose>The purpose of this task is to provide useful information to end users of the product being released into production.</purpose>
</org.eclipse.epf.uma:TaskDescription>
diff --git a/epf_prac_151/practice.gen.doc_trng.base/workproducts/product_documentation.xmi b/epf_prac_151/practice.gen.doc_trng.base/workproducts/product_documentation.xmi
index 1d7df28..965d96b 100644
--- a/epf_prac_151/practice.gen.doc_trng.base/workproducts/product_documentation.xmi
+++ b/epf_prac_151/practice.gen.doc_trng.base/workproducts/product_documentation.xmi
@@ -1,14 +1,14 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-NHao3cbpesderphl_fDlDw" name="product_documentation,_E8QEgEVtEeC6_c5S_pc9RA" guid="-NHao3cbpesderphl_fDlDw" changeDate="2011-04-11T22:12:42.080-0600" version="7.5.1">
+<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-NHao3cbpesderphl_fDlDw" name="product_documentation,_E8QEgEVtEeC6_c5S_pc9RA" guid="-NHao3cbpesderphl_fDlDw" changeDate="2012-05-30T13:55:07.824-0700" version="7.5.1">
<mainDescription><p>
- Product documentation is created for the benefit of the marketing arm of an organization, the Program Manager, and
+ Product documentation is created for the benefit of the marketing arm of an organization, the program manager, and
those people who must assess the business value of a particular system.
</p>
<p>
- This is an often overlooked aspect of Development Team implementation. The team should consider that the customers of a
- particular Release usually are not technical themselves, but do require a detailed enough understanding of how their
+ This is an often overlooked aspect of development team implementation. The team should consider that the customers of a
+ particular release usually are not technical themselves, but do require a detailed enough understanding of how their
product operates and how it meets stated business goals and needs.
</p></mainDescription>
- <purpose>The purpose of this work product is to provide documentation about the product for a Product Owner and their constituents
+ <purpose>The purpose of this work product is to provide documentation about the product for a product owner and their constituents
to be able to manage the product during its development and after the project is completed.</purpose>
</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/epf_prac_151/practice.gen.doc_trng.base/workproducts/training_materials.xmi b/epf_prac_151/practice.gen.doc_trng.base/workproducts/training_materials.xmi
index 4bb6a13..2500324 100644
--- a/epf_prac_151/practice.gen.doc_trng.base/workproducts/training_materials.xmi
+++ b/epf_prac_151/practice.gen.doc_trng.base/workproducts/training_materials.xmi
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-U5rK8ue_5v305MPzxKzQUg" name="training_materials,_B2vaMEVvEeC6_c5S_pc9RA" guid="-U5rK8ue_5v305MPzxKzQUg" changeDate="2011-10-13T12:16:35.404-0600" version="7.5.1">
+<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-U5rK8ue_5v305MPzxKzQUg" name="training_materials,_B2vaMEVvEeC6_c5S_pc9RA" guid="-U5rK8ue_5v305MPzxKzQUg" changeDate="2012-05-30T14:04:32.231-0700" version="7.5.1">
<mainDescription><p>
Training materials that can be used to train end users and production support personnel might consist of:
</p>
@@ -33,5 +33,5 @@
</li>
</ul></mainDescription>
<purpose>The purpose of this work product is to provide direct understanding of how to use or support a set of features deployed in
-a particular Release.</purpose>
+a particular release.</purpose>
</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/epf_prac_151/practice.gen.production_release.base/guidances/checklists/deployment_plan.xmi b/epf_prac_151/practice.gen.production_release.base/guidances/checklists/deployment_plan.xmi
index 55d5c8b..5d88fca 100644
--- a/epf_prac_151/practice.gen.production_release.base/guidances/checklists/deployment_plan.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/guidances/checklists/deployment_plan.xmi
@@ -2,18 +2,18 @@
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-x6K6zdVklh4CbhxTeVvYew" name="deployment_plan,_LXE_8LlKEeCciPPzZcIJFA" guid="-x6K6zdVklh4CbhxTeVvYew" changeDate="2011-07-28T11:52:30.549-0700" version="7.5.1">
<mainDescription>By answering a set of generic questions (who, what, when, where, why, and how), deployment planning can go a long way to
make a release a satisfying experience. Some questions to be considered are indicated by the check items below:</mainDescription>
- <sections xmi:id="_IAHg0uB-EeC1y_NExchKwQ" name="Who are the End Users of the features to be released?" guid="_IAHg0uB-EeC1y_NExchKwQ">
- <sectionDescription>Do those End Users require any special training?</sectionDescription>
+ <sections xmi:id="_IAHg0uB-EeC1y_NExchKwQ" name="Who are the end users of the features to be released?" guid="_IAHg0uB-EeC1y_NExchKwQ">
+ <sectionDescription>Do those end users require any special training?</sectionDescription>
</sections>
<sections xmi:id="_IAHg1eB-EeC1y_NExchKwQ" name="What features must be deployed?" guid="_IAHg1eB-EeC1y_NExchKwQ">
- <sectionDescription>What features will make this release valuable to the End User community? What components are included in the release
+ <sectionDescription>What features will make this release valuable to the end user community? What components are included in the release
package?</sectionDescription>
</sections>
<sections xmi:id="_IAHg1OB-EeC1y_NExchKwQ" name="When do the features need to be available?" guid="_IAHg1OB-EeC1y_NExchKwQ">
<sectionDescription>When must the deployment be completed and tested?</sectionDescription>
</sections>
- <sections xmi:id="_IAG5wuB-EeC1y_NExchKwQ" name="Where are the End Users located? " guid="_IAG5wuB-EeC1y_NExchKwQ">
- <sectionDescription>Are End Users distributed or in one location, and are their infrastructure configurations the same or different? <br /></sectionDescription>
+ <sections xmi:id="_IAG5wuB-EeC1y_NExchKwQ" name="Where are the end users located? " guid="_IAG5wuB-EeC1y_NExchKwQ">
+ <sectionDescription>Are end users distributed or in one location, and are their infrastructure configurations the same or different? <br /></sectionDescription>
</sections>
<sections xmi:id="_IAHg0OB-EeC1y_NExchKwQ" name="Why is the release taking place?" guid="_IAHg0OB-EeC1y_NExchKwQ">
<sectionDescription>Is the deployment needed to resolve an issue or is it required to provide new functionality that has been requested? <br /></sectionDescription>
diff --git a/epf_prac_151/practice.gen.production_release.base/guidances/practices/production_release.xmi b/epf_prac_151/practice.gen.production_release.base/guidances/practices/production_release.xmi
index 4d368a6..af750d6 100644
--- a/epf_prac_151/practice.gen.production_release.base/guidances/practices/production_release.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/guidances/practices/production_release.xmi
@@ -18,7 +18,7 @@
</p>
<p>
Deployment involves the act of delivering the release into the production environment, verifying that the integration
- of the release package into the existing environment was successful, and notifying all relevant Stakeholders that the
+ of the release package into the existing environment was successful, and notifying all relevant stakeholders that the
features of the release are available for use.
</p>
<p>
diff --git a/epf_prac_151/practice.gen.production_release.base/guidances/roadmaps/how_to_adopt_production_release.xmi b/epf_prac_151/practice.gen.production_release.base/guidances/roadmaps/how_to_adopt_production_release.xmi
index 849d803..8e9afaf 100644
--- a/epf_prac_151/practice.gen.production_release.base/guidances/roadmaps/how_to_adopt_production_release.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/guidances/roadmaps/how_to_adopt_production_release.xmi
@@ -9,11 +9,11 @@
coordinated Release.
</p>
<p>
- If a Development Team has never practiced Production Release before, the best way to think of this special type of
+ If a development team has never practiced Production Release before, the best way to think of this special type of
Sprint/Iteration is to consider a past project in which your team spent a week of 16-hour days doing all the things
necessary to prepare for a deployment based on an arbitrary release date. Then realize that you do not have to operate
like that any more, and that a Production Release Sprint/Iteration is your opportunity to calmly deal with all the
- preparatory activities that accompany a well-managed, coordinated release while other Development Teams are doing the
+ preparatory activities that accompany a well-managed, coordinated release while other development team members are doing the
same. In short, the Production Release practice represents the way you always wished you could prepare for a release
but did not have the opportunity.
</p>
@@ -21,12 +21,12 @@
Common pitfalls
</h3>
<p>
- Because production release provides a Development Team the opportunity to "fine tune" a product and tighten up
+ Because production release provides a development team the opportunity to "fine tune" a product and tighten up
problematic areas of the code, it is good practice not to squander that Sprint/Iteration.
</p>
<ul>
<li>
- <strong>A Release Sprint/Iteration is not a time to rest:</strong> Some Development Teams think that when they get
+ <strong>A Release Sprint/Iteration is not a time to rest:</strong> Some development team members think that when they get
to Production Release they can relax and not work too hard. However, when practicing the Agile value of Sustainable
Pace, teams should <em>not need to</em> rest, and team members should maintain the tempo that they established
during previous Feature Development Sprint/Iterations.
@@ -34,7 +34,7 @@
<li>
<strong>Testing is not more important than documentation and training:</strong> While the various types of testing
that are conducted in a Release Sprint/Iteration (integration, system, UAT) are important, documentation and
- training are just as important because how well End Users can actually use the product to do their work is critical
+ training are just as important because how well end users can actually use the product to do their work is critical
to a successful delivery.
</li>
<li>
diff --git a/epf_prac_151/practice.gen.production_release.base/plugin.xmi b/epf_prac_151/practice.gen.production_release.base/plugin.xmi
index f3b8697..5d401b9 100644
--- a/epf_prac_151/practice.gen.production_release.base/plugin.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/plugin.xmi
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1">
+<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1">
<org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_mYj6YOCIEeC1y_NExchKwQ" guid="_mYj6YOCIEeC1y_NExchKwQ">
<resourceDescriptors xmi:id="_I7u0gOB-EeC1y_NExchKwQ" id="-x6K6zdVklh4CbhxTeVvYew" uri="guidances/checklists/deployment_plan.xmi"/>
<resourceDescriptors xmi:id="_I7Q6cOB-EeC1y_NExchKwQ" id="-wHkXWtQxFeicCBDHK-f7xg" uri="workproducts/release_communications.xmi"/>
@@ -49,11 +49,11 @@
<methodElementProperty xmi:id="_1jAw0JifEeGlkdGl1HQlDA" name="me_edited" value="true"/>
<presentation xmi:id="-SLY9_MQQ_ykBIaLojfgzBQ" href="uma://-SLY9_MQQ_ykBIaLojfgzBQ#-SLY9_MQQ_ykBIaLojfgzBQ"/>
</contentElements>
- <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_IAIu9uB-EeC1y_NExchKwQ" name="review_conform_to_release_controls" guid="_IAIu9uB-EeC1y_NExchKwQ" presentationName="Review and Conform to Release Controls" briefDescription="Release controls normally are specified by the Deployment Manager. These controls document the requirements to which all releases must conform before being placed into the production environment." mandatoryInput="_IAJWA-B-EeC1y_NExchKwQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_IAIu9uB-EeC1y_NExchKwQ" name="review_conform_to_release_controls" guid="_IAIu9uB-EeC1y_NExchKwQ" presentationName="Review and Conform to Release Controls" briefDescription="Release controls normally are specified by the deployment manager. These controls document the requirements to which all releases must conform before being placed into the production environment." mandatoryInput="_IAJWA-B-EeC1y_NExchKwQ">
<methodElementProperty xmi:id="_1ikE4JifEeGlkdGl1HQlDA" name="me_edited" value="true"/>
<presentation xmi:id="-zT8t7LcbcrgIhYd_XUi6DA" href="uma://-zT8t7LcbcrgIhYd_XUi6DA#-zT8t7LcbcrgIhYd_XUi6DA"/>
</contentElements>
- <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_IAJ9EeB-EeC1y_NExchKwQ" name="plan_deployment" guid="_IAJ9EeB-EeC1y_NExchKwQ" presentationName="Plan Deployment" briefDescription="If a Deployment Plan for the project already exists, update it to reflect the nature of this release. If this document does not exist, develop a Deployment Plan to indicate how this release will be rolled out to the production environment." checklists="_IAG5weB-EeC1y_NExchKwQ" output="_IAJ9FeB-EeC1y_NExchKwQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_IAJ9EeB-EeC1y_NExchKwQ" name="plan_deployment" guid="_IAJ9EeB-EeC1y_NExchKwQ" presentationName="Plan Deployment" briefDescription="If a deployment plan for the project already exists, update it to reflect the nature of this release. If this document does not exist, develop a deployment plan to indicate how this release will be rolled out to the production environment." checklists="_IAG5weB-EeC1y_NExchKwQ" output="_IAJ9FeB-EeC1y_NExchKwQ">
<methodElementProperty xmi:id="_1lZWcJifEeGlkdGl1HQlDA" name="me_edited" value="true"/>
<presentation xmi:id="-QqCVewwu8buOCXKRukpf5g" href="uma://-QqCVewwu8buOCXKRukpf5g#-QqCVewwu8buOCXKRukpf5g"/>
</contentElements>
@@ -65,28 +65,34 @@
<methodElementProperty xmi:id="_1kDSoJifEeGlkdGl1HQlDA" name="me_edited" value="true"/>
<presentation xmi:id="-Z_sfrl6NWP_8GKlFeHrrgg" href="uma://-Z_sfrl6NWP_8GKlFeHrrgg#-Z_sfrl6NWP_8GKlFeHrrgg"/>
</contentElements>
- <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_IAJWA-B-EeC1y_NExchKwQ" name="release_controls" guid="_IAJWA-B-EeC1y_NExchKwQ" presentationName="Release Controls" briefDescription="Release controls normally are established by IT management and enforced by the Deployment Manager.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_IAJWA-B-EeC1y_NExchKwQ" name="release_controls" guid="_IAJWA-B-EeC1y_NExchKwQ" presentationName="Release Controls" briefDescription="Release controls normally are established by IT management and enforced by the deployment manager.">
+ <methodElementProperty xmi:id="_daFekKqeEeGLQ_Sv1UBWjg" name="me_edited" value="true"/>
<presentation xmi:id="-s-_ZWqfnqO34JF-_nDPk3Q" href="uma://-s-_ZWqfnqO34JF-_nDPk3Q#-s-_ZWqfnqO34JF-_nDPk3Q"/>
</contentElements>
- <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_IAJ9EOB-EeC1y_NExchKwQ" name="infrastructure" guid="_IAJ9EOB-EeC1y_NExchKwQ" presentationName="Infrastructure" briefDescription="In reference to a Release Sprint, infrastructure refers to all the hardware, software, and network facilities necessary to support a deployed release.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_IAJ9EOB-EeC1y_NExchKwQ" name="infrastructure" guid="_IAJ9EOB-EeC1y_NExchKwQ" presentationName="Infrastructure" briefDescription="In reference to a release sprint, infrastructure refers to all the hardware, software, and network facilities necessary to support a deployed release.">
+ <methodElementProperty xmi:id="_dXyYgKqeEeGLQ_Sv1UBWjg" name="me_edited" value="true"/>
<presentation xmi:id="-I1cGb0If2i9wNcOXbEU6XA" href="uma://-I1cGb0If2i9wNcOXbEU6XA#-I1cGb0If2i9wNcOXbEU6XA"/>
</contentElements>
- <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_IAJ9FeB-EeC1y_NExchKwQ" name="deployment_plan" guid="_IAJ9FeB-EeC1y_NExchKwQ" presentationName="Deployment Plan" briefDescription="A Deployment Plan is used to document all the information needed by Deployment Engineers to deploy a release successfully." checklists="_IAG5weB-EeC1y_NExchKwQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_IAJ9FeB-EeC1y_NExchKwQ" name="deployment_plan" guid="_IAJ9FeB-EeC1y_NExchKwQ" presentationName="Deployment Plan" briefDescription="A deployment plan is used to document all the information needed by deployment engineers to deploy a release successfully." checklists="_IAG5weB-EeC1y_NExchKwQ">
+ <methodElementProperty xmi:id="_dWmFsKqeEeGLQ_Sv1UBWjg" name="me_edited" value="true"/>
<presentation xmi:id="-4Fv0TSuJBCRxarK5ssyLGw" href="uma://-4Fv0TSuJBCRxarK5ssyLGw#-4Fv0TSuJBCRxarK5ssyLGw"/>
</contentElements>
- <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_IAHg2eB-EeC1y_NExchKwQ" name="backout_plan" guid="_IAHg2eB-EeC1y_NExchKwQ" presentationName="Backout Plan" briefDescription="A Backout Plan defines the criteria and procedures to be followed if a release into production needs to be rolled back.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_IAHg2eB-EeC1y_NExchKwQ" name="backout_plan" guid="_IAHg2eB-EeC1y_NExchKwQ" presentationName="Backout Plan" briefDescription="A backout plan defines the criteria and procedures to be followed if a release into production needs to be rolled back.">
+ <methodElementProperty xmi:id="_dV6wQKqeEeGLQ_Sv1UBWjg" name="me_edited" value="true"/>
<presentation xmi:id="-O9dNph5o0Au5C2deOUG8Bg" href="uma://-O9dNph5o0Au5C2deOUG8Bg#-O9dNph5o0Au5C2deOUG8Bg"/>
</contentElements>
<contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_IAIH4OB-EeC1y_NExchKwQ" name="release_communications" guid="_IAIH4OB-EeC1y_NExchKwQ" presentationName="Release Communications" briefDescription="This artifact provides information to concerned parties that a product (or subset) has been placed into production.">
+ <methodElementProperty xmi:id="_dZzxwKqeEeGLQ_Sv1UBWjg" name="me_edited" value="true"/>
<presentation xmi:id="-wHkXWtQxFeicCBDHK-f7xg" href="uma://-wHkXWtQxFeicCBDHK-f7xg#-wHkXWtQxFeicCBDHK-f7xg"/>
</contentElements>
- <contentElements xsi:type="org.eclipse.epf.uma:Deliverable" xmi:id="_EopWMPddEeCG79QDqBlPXg" name="release" guid="_EopWMPddEeCG79QDqBlPXg" presentationName="Release" briefDescription="	
A Release is the transition of an increment of potentially shippable product from the development group into routine use by Customers based on a successful placement of a Release Sprint's output into the production environment.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Deliverable" xmi:id="_EopWMPddEeCG79QDqBlPXg" name="release" guid="_EopWMPddEeCG79QDqBlPXg" presentationName="Release" briefDescription="A release is the transition of an increment of potentially shippable product from the development group into routine use by customers based on a successful placement of a release sprint's output into the production environment.">
+ <methodElementProperty xmi:id="_dYXAQKqeEeGLQ_Sv1UBWjg" name="me_edited" value="true"/>
<presentation xmi:id="-Lo_rjBFuf6JDjdUw5nJjYw" href="uma://-Lo_rjBFuf6JDjdUw5nJjYw#-Lo_rjBFuf6JDjdUw5nJjYw"/>
</contentElements>
</childPackages>
<childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_IADPYuB-EeC1y_NExchKwQ" name="deployment" guid="_IADPYuB-EeC1y_NExchKwQ" presentationName="Deployment">
<methodElementProperty xmi:id="_CRWrsJigEeGlkdGl1HQlDA" name="me_edited" value="true"/>
- <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_IAD2dOB-EeC1y_NExchKwQ" name="execute_deployment_plan" guid="_IAD2dOB-EeC1y_NExchKwQ" presentationName="Execute Deployment Plan" briefDescription="The Deployment Plan has all the unique instructions necessary to roll out a release." checklists="_IAG5weB-EeC1y_NExchKwQ" mandatoryInput="_IAJ9FeB-EeC1y_NExchKwQ _IAJ9EOB-EeC1y_NExchKwQ _EopWMPddEeCG79QDqBlPXg" optionalInput="_IAJWA-B-EeC1y_NExchKwQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_IAD2dOB-EeC1y_NExchKwQ" name="execute_deployment_plan" guid="_IAD2dOB-EeC1y_NExchKwQ" presentationName="Execute Deployment Plan" briefDescription="The deployment plan has all the unique instructions necessary to roll out a release." checklists="_IAG5weB-EeC1y_NExchKwQ" mandatoryInput="_IAJ9FeB-EeC1y_NExchKwQ _IAJ9EOB-EeC1y_NExchKwQ _EopWMPddEeCG79QDqBlPXg" optionalInput="_IAJWA-B-EeC1y_NExchKwQ">
<methodElementProperty xmi:id="_CU7kIJigEeGlkdGl1HQlDA" name="me_edited" value="true"/>
<presentation xmi:id="-PPEUOk6Gija0ckrWlDdCxA" href="uma://-PPEUOk6Gija0ckrWlDdCxA#-PPEUOk6Gija0ckrWlDdCxA"/>
</contentElements>
@@ -98,7 +104,7 @@
<methodElementProperty xmi:id="_CYXSoJigEeGlkdGl1HQlDA" name="me_edited" value="true"/>
<presentation xmi:id="-chKviPT1F1yq5Y_KL9ET9g" href="uma://-chKviPT1F1yq5Y_KL9ET9g#-chKviPT1F1yq5Y_KL9ET9g"/>
</contentElements>
- <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_IAEdhuB-EeC1y_NExchKwQ" name="deliver_release_communications" guid="_IAEdhuB-EeC1y_NExchKwQ" presentationName="Deliver Release Communications" briefDescription="After a product release has been declared a success and is available for use, all relevant Stakeholders should receive a communique stating that fact." mandatoryInput="_IAIH4OB-EeC1y_NExchKwQ" optionalInput="_EopWMPddEeCG79QDqBlPXg">
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_IAEdhuB-EeC1y_NExchKwQ" name="deliver_release_communications" guid="_IAEdhuB-EeC1y_NExchKwQ" presentationName="Deliver Release Communications" briefDescription="After a product release has been declared a success and is available for use, all relevant stakeholders should receive a communique stating that fact." mandatoryInput="_IAIH4OB-EeC1y_NExchKwQ" optionalInput="_EopWMPddEeCG79QDqBlPXg">
<methodElementProperty xmi:id="_CaTMUJigEeGlkdGl1HQlDA" name="me_edited" value="true"/>
<presentation xmi:id="-HIQR9GY0lX3xDuTpeslNtg" href="uma://-HIQR9GY0lX3xDuTpeslNtg#-HIQR9GY0lX3xDuTpeslNtg"/>
</contentElements>
diff --git a/epf_prac_151/practice.gen.production_release.base/tasks/deliver_release_communications.xmi b/epf_prac_151/practice.gen.production_release.base/tasks/deliver_release_communications.xmi
index f4b8b70..6677459 100644
--- a/epf_prac_151/practice.gen.production_release.base/tasks/deliver_release_communications.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/tasks/deliver_release_communications.xmi
@@ -1,23 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-HIQR9GY0lX3xDuTpeslNtg" name="02_05_execute_release_communications,_FCKYcmzvEeCPgecPbK9bdg" guid="-HIQR9GY0lX3xDuTpeslNtg" changeDate="2011-09-13T22:09:17.171-0700" version="7.5.1">
+<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-HIQR9GY0lX3xDuTpeslNtg" name="02_05_execute_release_communications,_FCKYcmzvEeCPgecPbK9bdg" guid="-HIQR9GY0lX3xDuTpeslNtg" changeDate="2012-05-30T14:06:20.399-0700" version="7.5.1">
<mainDescription><p>
- This task represents the distribution of communiques that were prepared beforehand as part of the Release
- Communications artifact. Although the Development Team is responsible for preparing the communications, the
- responsibility for sending the communiques normally is assigned to the Deployment Engineer, if that is the
+ This task represents the distribution of communiques that were prepared beforehand as part of the release
+ communications artifact. Although the development team is responsible for preparing the communications, the
+ responsibility for sending the communiques normally is assigned to the deployment engineer, if that is the
organizational protocol.
</p></mainDescription>
- <sections xmi:id="_IAFEkeB-EeC1y_NExchKwQ" name="Validate the Communiques" guid="_IAFEkeB-EeC1y_NExchKwQ">
- <sectionDescription>Ensure that the communiques designated for this release are correct, complete, and reflect all the Stakeholder groups that
+ <sections xmi:id="_IAFEkeB-EeC1y_NExchKwQ" name="Validate the communiques" guid="_IAFEkeB-EeC1y_NExchKwQ">
+ <sectionDescription>Ensure that the communiques designated for this release are correct, complete, and reflect all the stakeholder groups that
must be informed.</sectionDescription>
</sections>
- <sections xmi:id="_IAFEkOB-EeC1y_NExchKwQ" name="Send Release Communications" guid="_IAFEkOB-EeC1y_NExchKwQ">
+ <sections xmi:id="_IAFEkOB-EeC1y_NExchKwQ" name="Send release communications" guid="_IAFEkOB-EeC1y_NExchKwQ">
<sectionDescription>Using a pre-planned script, send the communiques in the manner designated in the <a class="elementLinkWithType"
href="./../../practice.gen.production_release.base/workproducts/release_communications_7698226F.html"
guid="_IAIH4OB-EeC1y_NExchKwQ">Artifact: Release Communications</a>. Most of the time, the preferred communication
mechanism will be by email, but other methods could include beeper notification, telephone calls, a posting to an internal
release website, live or pre-recorded presentations by senior management, etc.</sectionDescription>
</sections>
- <sections xmi:id="_IAEdh-B-EeC1y_NExchKwQ" name="Validate Communications were Received" guid="_IAEdh-B-EeC1y_NExchKwQ">
+ <sections xmi:id="_IAEdh-B-EeC1y_NExchKwQ" name="Validate communications were received" guid="_IAEdh-B-EeC1y_NExchKwQ">
<sectionDescription>If the communiques were sent by email, it may be prudent to request a receipt of delivery to ensure that the notices were
received by the intended audience.</sectionDescription>
</sections>
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 0d3eca4..18581cb 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
@@ -1,24 +1,19 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-Z_sfrl6NWP_8GKlFeHrrgg" name="04_create_update_backout_plan,_2F7n8DHNEeC7j_IRiP-WPQ" guid="-Z_sfrl6NWP_8GKlFeHrrgg" changeDate="2011-07-28T12:18:22.207-0700" version="7.5.1">
+<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-Z_sfrl6NWP_8GKlFeHrrgg" name="04_create_update_backout_plan,_2F7n8DHNEeC7j_IRiP-WPQ" guid="-Z_sfrl6NWP_8GKlFeHrrgg" changeDate="2011-07-28T12:18:22.207-0700" version="7.5.1">
<mainDescription>A rollback might be needed for a variety of reasons, including corruption of the production code base, inoperable
-components, an unplanned undesirable effect of the release on other production systems, an unhappy Customer, etc.
-The&nbsp;Development Team should provide the production support organization with a specific plan and decision criteria
+components, an unplanned undesirable effect of the release on other production systems, an unhappy customer, etc.
+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
-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 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>
</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
-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 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" 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>
- <sections xmi:id="_IAIu9OB-EeC1y_NExchKwQ" name="Update the Backout Plan (if applicable)" guid="_IAIu9OB-EeC1y_NExchKwQ">
- <sectionDescription>If a Backout Plan does exist that can be used as a baseline, review that plan and update, add, or delete information as
+ <sections xmi:id="_IAIu9OB-EeC1y_NExchKwQ" name="Update the backout plan (if applicable)" guid="_IAIu9OB-EeC1y_NExchKwQ">
+ <sectionDescription>If a backout plan does exist that can be used as a baseline, review that plan and update, add, or delete information as
necessary. When the plan is completed, it should reflect entirely the contents of the upcoming deployment only, not a
-release in the past or one in the future. In other words, the Backout Plan should be specific only to this release.</sectionDescription>
+release in the past or one in the future. In other words, the backout plan should be specific only to this release.</sectionDescription>
</sections>
<purpose>The purpose of this task is to develop the criteria, procedures, and responsibilities associated with rolling back a
specific release into the production environment to prevent or minimize interruptions to other products or services.</purpose>
diff --git a/epf_prac_151/practice.gen.production_release.base/tasks/develop_release_communications.xmi b/epf_prac_151/practice.gen.production_release.base/tasks/develop_release_communications.xmi
index 03d6676..0f04aad 100644
--- a/epf_prac_151/practice.gen.production_release.base/tasks/develop_release_communications.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/tasks/develop_release_communications.xmi
@@ -1,50 +1,50 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-FWdvN43s5ux00S-GVpDH-w" name="05_develop_release_communications,_g-LLEDHNEeC7j_IRiP-WPQ" guid="-FWdvN43s5ux00S-GVpDH-w" changeDate="2011-07-28T12:31:26.269-0700" version="7.5.1">
+<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-FWdvN43s5ux00S-GVpDH-w" name="05_develop_release_communications,_g-LLEDHNEeC7j_IRiP-WPQ" guid="-FWdvN43s5ux00S-GVpDH-w" changeDate="2011-07-28T12:31:26.269-0700" version="7.5.1">
<mainDescription><p>
- When a release is pushed to production, all the Stakeholders of that product should be notified that the event has
- happened and what the release means to each of the Stakeholders. Often, the output of this task does not need to be
+ When a release is pushed to production, all the stakeholders of that product should be notified that the event has
+ happened and what the release means to each of the stakeholders. Often, the output of this task does not need to be
created from scratch; for products that plan multiple releases, just updating the communique details for each release
- might be enough. However, if any of the Stakeholder groups change, or there is a significant difference in the product
+ might be enough. However, if any of the stakeholder groups change, or there is a significant difference in the product
distribution, more significant content might need to be developed.
</p>
<p>
- In any case, communicating effectively to the End User community is important. A Development Team can develop high
- quality software, but if messaging to the Stakeholders is conducted poorly or not at all, the End User experience might
+ In any case, communicating effectively to the end user community is important. A development team can develop high
+ quality software, but if messaging to the stakeholders is conducted poorly or not at all, the end user experience might
be degraded. By simply answering the questions "who, what, when, where, why, and how" in a format appropriate for each
- Stakeholder group, a product release can become a more satisfying experience for all those involved.
+ stakeholder group, a product release can become a more satisfying experience for all those involved.
</p></mainDescription>
- <sections xmi:id="_IAJWBuB-EeC1y_NExchKwQ" name="Identify Stakeholders for this Release" guid="_IAJWBuB-EeC1y_NExchKwQ">
- <sectionDescription>The Development Team should know exactly which Stakeholder groups will benefit from the upcoming release. First, identify
-the Stakeholders for this release. Next, determine how each Stakeholder group is expected to benefit from the release based
+ <sections xmi:id="_IAJWBuB-EeC1y_NExchKwQ" name="Identify stakeholders for this release" guid="_IAJWBuB-EeC1y_NExchKwQ">
+ <sectionDescription>The development team should know exactly which stakeholder groups will benefit from the upcoming release. First, identify
+the stakeholders for this release. Next, determine how each stakeholder group is expected to benefit from the release based
on the components that will be delivered to production.</sectionDescription>
</sections>
- <sections xmi:id="_IAJWBeB-EeC1y_NExchKwQ" name="Draft Communique for each Stakeholder Group" guid="_IAJWBeB-EeC1y_NExchKwQ">
+ <sections xmi:id="_IAJWBeB-EeC1y_NExchKwQ" name="Draft communique for each stakeholder group" guid="_IAJWBeB-EeC1y_NExchKwQ">
<sectionDescription><p>
- For each Stakeholder group, document the following:
+ For each stakeholder group, document the following:
</p>
<ul>
<li>
- The features that will be deployed to production that those Stakeholders are expected to benefit from
+ The features that will be deployed to production that those stakeholders are expected to benefit from
</li>
<li>
- The business value that Stakeholder group will obtain from the feature set being released
+ The business value that stakeholder group will obtain from the feature set being released
</li>
<li>
- How, when, and where that Stakeholder group will be able to access the new functionality and what special
+ How, when, and where that stakeholder group will be able to access the new functionality and what special
credentials or permissions are required
</li>
<li>
- Any additional constraints or information that the Stakeholder group should be aware of, such as availability
+ Any additional constraints or information that the stakeholder group should be aware of, such as availability
restrictions, geographical restrictions, server limitations, regulatory requirements, etc.
</li>
</ul></sectionDescription>
</sections>
- <sections xmi:id="_IAJWB-B-EeC1y_NExchKwQ" name="Provide Commiques to Deployment Manager" guid="_IAJWB-B-EeC1y_NExchKwQ">
- <sectionDescription>After drafting the communiques for each Stakeholder group, the Development Team should provide those drafts to the
-Deployment Manager. Typically, release communications are consolidated and released at the program level. The Deployment
-Manager and Deployment Engineers normally are responsible for ensuring that all release communications are consistent and
-concise. The Deployment Manager will determine the appropriate time to communicate information about the upcoming release
-to the appropriate Stakeholders.</sectionDescription>
+ <sections xmi:id="_IAJWB-B-EeC1y_NExchKwQ" name="Provide commiques to deployment manager" guid="_IAJWB-B-EeC1y_NExchKwQ">
+ <sectionDescription>After drafting the communiques for each stakeholder group, the development team should provide those drafts to the
+deployment manager. Typically, release communications are consolidated and released at the program level. The deployment
+manager and deployment engineers normally are responsible for ensuring that all release communications are consistent and
+concise. The deployment manager will determine the appropriate time to communicate information about the upcoming release
+to the appropriate stakeholders.</sectionDescription>
</sections>
<purpose>The purpose of this task is to create the content and criteria to identify who is notified and to describe how they are
notified after a release is deployed successfully to the production environment.</purpose>
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 9abfaea..1b1589b 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
@@ -1,36 +1,24 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-mHGd7nm4EywKy0UPe9dZhg" name="02_04_execute_backout_plan,_FCK_gGzvEeCPgecPbK9bdg" guid="-mHGd7nm4EywKy0UPe9dZhg" changeDate="2011-07-28T16:11:20.087-0700" version="7.5.1">
- <mainDescription>Assuming a Backout Plan is available for this release, the Deployment Engineer (or Development Team) will follow the
+<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-mHGd7nm4EywKy0UPe9dZhg" name="02_04_execute_backout_plan,_FCK_gGzvEeCPgecPbK9bdg" guid="-mHGd7nm4EywKy0UPe9dZhg" changeDate="2012-05-30T14:08:13.096-0700" version="7.5.1">
+ <mainDescription>Assuming a backout plan is available for this release, the deployment engineer (or development team) will follow the
instructions for reversing the installation of the product into production, if there is a problem. While the plan might
have been written with good intentions, sometimes key procedures are missing or have not been thought out. The team backing
-out the release should be aware that blindly following the Backout Plan might not be the best approach. It is best to
+out the release should be aware that blindly following the backout plan might not be the best approach. It is best to
consider the unique circumstances within which the deployment has failed and rely on common sense and experience when
-executing the Backout Plan.</mainDescription>
- <sections xmi:id="_IAD2c-B-EeC1y_NExchKwQ" name="Identify Release Problem(s)" guid="_IAD2c-B-EeC1y_NExchKwQ">
- <sectionDescription><p>
- 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>
- Log the issues as critical defects as soon as possible and assign those defects to the appropriate team members for
- resolution.
-</p></sectionDescription>
+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%<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%</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
-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 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>
</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
-Agile System Team might need to be engaged to find and fix the problem(s).</sectionDescription>
+ <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>
</sections>
- <sections xmi:id="_IAD2ceB-EeC1y_NExchKwQ" name="Communicate the Backout" guid="_IAD2ceB-EeC1y_NExchKwQ">
+ <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
-minimize End User impact, use beeper-based notifications judiciously. In most cases, an email to key Stakeholders (such as
-the Product Owner and Program Manager) might suffice. Following up with a phone call also might be warranted.</sectionDescription>
+minimize end user impact, use beeper-based notifications judiciously. In most cases, an email to key stakeholders (such as
+the product owner and program manager) might suffice. Following up with a phone call also might be warranted.</sectionDescription>
</sections>
<purpose>The purpose of this task is to remove a specific release quickly and seamlessly from the production environment because the
release has caused problems or because it has been determined by the stakeholder community as unfit for service.</purpose>
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 a02f227..fec1c8d 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
@@ -1,21 +1,20 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-PPEUOk6Gija0ckrWlDdCxA" name="02_02_execute_deployment_plan,_FCK_gWzvEeCPgecPbK9bdg" guid="-PPEUOk6Gija0ckrWlDdCxA" changeDate="2011-09-13T22:05:32.383-0700" version="7.5.1">
+<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-PPEUOk6Gija0ckrWlDdCxA" name="02_02_execute_deployment_plan,_FCK_gWzvEeCPgecPbK9bdg" guid="-PPEUOk6Gija0ckrWlDdCxA" changeDate="2012-05-30T14:11:35.736-0700" version="7.5.1">
<mainDescription><p>
This task is straightforward: follow the procedures in the Deployment Plan for the rollout of a specific product
- release. If the Deployment Plan does not exist or it is poorly constructed, this task might be much more difficult.
+ release. If the deployment plan does not exist or it is poorly constructed, this task might be much more difficult.
</p>
<p>
- The main point here is that to achieve a high probability of success, the Development Team should have previously
+ The main point here is that to achieve a high probability of success, the development team should have previously
developed a detailed plan that organizes and articulates all the unique instructions for deploying that particular
- release. Because an experienced Deployment Engineer normally executes this task, they might be able to overcome any
- missing deployment procedures or content. However, that is not an excuse for a Development Team to not develop the
+ release. Because an experienced deployment engineer normally executes this task, they might be able to overcome any
+ missing deployment procedures or content. However, that is not an excuse for a development team to not develop the
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
-installed and that the system is in the correct state. Also ensure that the release window is ready to be achieved.</sectionDescription>
+ <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>
</sections>
- <sections xmi:id="_IAD2duB-EeC1y_NExchKwQ" name="Release Code" guid="_IAD2duB-EeC1y_NExchKwQ">
+ <sections xmi:id="_IAD2duB-EeC1y_NExchKwQ" name="Release code" guid="_IAD2duB-EeC1y_NExchKwQ">
<sectionDescription><p>
When the preliminary review has been completed and the release window has started, deploy the release package into
production. Depending on the release script and the size of the package, this installation might take anywhere from a
diff --git a/epf_prac_151/practice.gen.production_release.base/tasks/install_validate_infrastructure.xmi b/epf_prac_151/practice.gen.production_release.base/tasks/install_validate_infrastructure.xmi
index 01d04d9..2711b3a 100644
--- a/epf_prac_151/practice.gen.production_release.base/tasks/install_validate_infrastructure.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/tasks/install_validate_infrastructure.xmi
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-SLY9_MQQ_ykBIaLojfgzBQ" name="02_install_validate_infrastructure,_FVOHgDHMEeC7j_IRiP-WPQ" guid="-SLY9_MQQ_ykBIaLojfgzBQ" changeDate="2011-09-13T22:12:43.813-0700" version="7.5.1">
+<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-SLY9_MQQ_ykBIaLojfgzBQ" name="02_install_validate_infrastructure,_FVOHgDHMEeC7j_IRiP-WPQ" guid="-SLY9_MQQ_ykBIaLojfgzBQ" changeDate="2011-09-13T22:12:43.813-0700" version="7.5.1">
<mainDescription><p>
A release package cannot be deployed to production if the environmental infrastructure within which the release will be
run is not sufficiently built or tested. Whether the release is deployed as a "push" (where the application is deployed
@@ -44,28 +44,28 @@
</ul>
</li>
</ul></mainDescription>
- <sections xmi:id="_IAIH4-B-EeC1y_NExchKwQ" name="Identify Infrastructure Needs" guid="_IAIH4-B-EeC1y_NExchKwQ">
+ <sections xmi:id="_IAIH4-B-EeC1y_NExchKwQ" name="Identify infrastructure needs" guid="_IAIH4-B-EeC1y_NExchKwQ">
<sectionDescription>Identify and describe all the components of the infrastructure that are needed to support the upcoming release. These
requirements should be based completely on the feature set that is about to be deployed, not on intended future needs.</sectionDescription>
</sections>
- <sections xmi:id="_IAIu8eB-EeC1y_NExchKwQ" name="Procure Components" guid="_IAIu8eB-EeC1y_NExchKwQ">
+ <sections xmi:id="_IAIu8eB-EeC1y_NExchKwQ" name="Procure components" guid="_IAIu8eB-EeC1y_NExchKwQ">
<sectionDescription>Determine how long it will reasonably take to procure the needed components and to engage the appropriate division in the
organization to place the order. Be sure to work with the procurement agency to track the order and to identify any issues
-with that order. Ultimately, the Development Team, not the procurement agency, is responsible for ensuring that the correct
+with that order. Ultimately, the development team, not the procurement agency, is responsible for ensuring that the correct
infrastructure components are in place.</sectionDescription>
</sections>
- <sections xmi:id="_IAIH5OB-EeC1y_NExchKwQ" name="Schedule Components for Installation" guid="_IAIH5OB-EeC1y_NExchKwQ">
+ <sections xmi:id="_IAIH5OB-EeC1y_NExchKwQ" name="Schedule components for installation" guid="_IAIH5OB-EeC1y_NExchKwQ">
<sectionDescription>After the procured components arrive, schedule to have them installed by the IT operations group(s) that control the
-production environment. The Development Team should be developing tests to confirm the correct installation at this time.</sectionDescription>
+production environment. The development team should be developing tests to confirm the correct installation at this time.</sectionDescription>
</sections>
- <sections xmi:id="_IAIH4uB-EeC1y_NExchKwQ" name="Install and Test Components" guid="_IAIH4uB-EeC1y_NExchKwQ">
+ <sections xmi:id="_IAIH4uB-EeC1y_NExchKwQ" name="Install and test components" guid="_IAIH4uB-EeC1y_NExchKwQ">
<sectionDescription>When the components have been installed, be prepared to run the validation tests developed in the previous step. These
tests should not only verify the individual components' readiness, but also should validate their integration with each
other and with legacy components.</sectionDescription>
</sections>
- <sections xmi:id="_IAIu8OB-EeC1y_NExchKwQ" name="Validate Other Component Aspects" guid="_IAIu8OB-EeC1y_NExchKwQ">
+ <sections xmi:id="_IAIu8OB-EeC1y_NExchKwQ" name="Validate other component aspects" guid="_IAIu8OB-EeC1y_NExchKwQ">
<sectionDescription><p>
- As the validation testing is underway, the Development Team also should consider how the newly installed components
+ As the validation testing is underway, the development team also should consider how the newly installed components
impact overall system security, whether or not database connectivity and security have been compromised, and what
impact they have on the configuration management database that contains an inventory of CIs.
</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 f4ecec2..a99aa4e 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
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-fBwPDexzVTCxcEM5H1ljeQ" name="02_01_package_the_release,_DQowcWzvEeCPgecPbK9bdg" guid="-fBwPDexzVTCxcEM5H1ljeQ" changeDate="2011-09-13T22:14:24.290-0700" version="7.5.1">
+<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-fBwPDexzVTCxcEM5H1ljeQ" name="02_01_package_the_release,_DQowcWzvEeCPgecPbK9bdg" guid="-fBwPDexzVTCxcEM5H1ljeQ" changeDate="2012-05-30T14:12:33.929-0700" version="7.5.1">
<mainDescription><p>
The key activities normally used to package a release:
</p>
@@ -37,30 +37,26 @@
</ul>
</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
-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 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>
</sections>
- <sections xmi:id="_IAEdguB-EeC1y_NExchKwQ" name="Test the Release" guid="_IAEdguB-EeC1y_NExchKwQ">
+ <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
mimics the production environment. A "staging" environment usually is maintained for this purpose. Testing typically
includes a "smoke test" in which key features are exercised to highlight any unplanned behavior.</sectionDescription>
</sections>
- <sections xmi:id="_IAEdhOB-EeC1y_NExchKwQ" name="Tag Source Code Repository" guid="_IAEdhOB-EeC1y_NExchKwQ">
+ <sections xmi:id="_IAEdhOB-EeC1y_NExchKwQ" name="Tag source code repository" guid="_IAEdhOB-EeC1y_NExchKwQ">
<sectionDescription>In the team's configuration management (CM) tool, tag all the components that went into the release package so that the
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
-add it to the release package.</sectionDescription>
+ <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>
</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
-Team in a timely manner. Be prepared to answer questions from the Deployment Engineer, especially questions about
+ <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
+team in a timely manner. Be prepared to answer questions from the deployment engineer, especially questions about
conformity to release controls.</sectionDescription>
</sections>
<purpose>The purpose of this task is to render a complete, deployable package capable of being released into the production
-environment by the Deployment Engineer.</purpose>
+environment by the deployment engineer.</purpose>
</org.eclipse.epf.uma:TaskDescription>
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 4b09aa5..05b5e6e 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
@@ -1,29 +1,22 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-QqCVewwu8buOCXKRukpf5g" name="03_create_update_deployment_plan,_FR0_0DHNEeC7j_IRiP-WPQ" guid="-QqCVewwu8buOCXKRukpf5g" changeDate="2011-07-28T11:53:55.365-0700" version="7.5.1">
+<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-QqCVewwu8buOCXKRukpf5g" name="03_create_update_deployment_plan,_FR0_0DHNEeC7j_IRiP-WPQ" guid="-QqCVewwu8buOCXKRukpf5g" changeDate="2012-05-30T14:20:09.505-0700" version="7.5.1">
<mainDescription><p>
- Because a Deployment Engineer is responsible for accepting the results of one or more Development Teams and deploying
- those integrated releases into the production environment, it is important for all parties to agree on the details of a
- particular release. The Deployment Plan documents, in one place, all the information that will be consumed by the
- Deployment Engineer before and during the deployment to production of a particular release package.
+ Because a deployment engineer is responsible for accepting the results of one or more development team members and
+ deploying those integrated releases into the production environment, it is important for all parties to agree on the
+ details of a particular release. The deployment plan documents, in one place, all the information that will be consumed
+ 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
-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 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>
</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
-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"
-guid="_IAG5weB-EeC1y_NExchKwQ">Checklist: Deployment Plan</a> to start and develop a Deployment Plan.</sectionDescription>
+ <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" 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" guid="_IAG5weB-EeC1y_NExchKwQ">Checklist: Deployment Plan</a> to start and develop a deployment plan.</sectionDescription>
</sections>
- <sections xmi:id="_IAJ9FOB-EeC1y_NExchKwQ" name="Update the Deployment Plan (if applicable)" guid="_IAJ9FOB-EeC1y_NExchKwQ">
- <sectionDescription>If a Deployment Plan does exist that can be used as a baseline, review that plan and update, add, or delete information as
+ <sections xmi:id="_IAJ9FOB-EeC1y_NExchKwQ" name="Update the deployment plan (if applicable)" guid="_IAJ9FOB-EeC1y_NExchKwQ">
+ <sectionDescription>If a deployment plan does exist that can be used as a baseline, review that plan and update, add, or delete information as
necessary. When the plan is done, it should reflect entirely the contents of the upcoming deployment only, not a release in
-the past or one in the future. In other words, the Deployment Plan should be specific only to this release.</sectionDescription>
+the past or one in the future. In other words, the deployment plan should be specific only to this release.</sectionDescription>
</sections>
<purpose>The purpose of this task is to ensure that the various aspects of deploying a release to production are considered and
-understood between the Development Team and the Deployment Engineer.</purpose>
+understood between the development team and the deployment engineer.</purpose>
</org.eclipse.epf.uma:TaskDescription>
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 4da1d2e..f540021 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
@@ -1,11 +1,11 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-zT8t7LcbcrgIhYd_XUi6DA" name="01_review_conform_to_release_controls,_PwLDcDHMEeC7j_IRiP-WPQ" guid="-zT8t7LcbcrgIhYd_XUi6DA" changeDate="2011-09-13T22:16:21.716-0700" version="7.5.1">
+<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-zT8t7LcbcrgIhYd_XUi6DA" name="01_review_conform_to_release_controls,_PwLDcDHMEeC7j_IRiP-WPQ" guid="-zT8t7LcbcrgIhYd_XUi6DA" changeDate="2012-05-30T14:22:34.002-0700" version="7.5.1">
<mainDescription><p>
Release controls describe the minimum number of requirements that a software package must adhere to before being
- released into production. This is especially important if a Development Team is new or emerging, because they might not
- be aware of the great responsibilities a Deployment Manager has. In fact, a Deployment Manager is responsible to senior
+ released into production. This is especially important if a development team is new or emerging, because they might not
+ be aware of the great responsibilities a deployment manager has. In fact, a deployment manager is responsible to senior
management for ensuring that nothing is placed into production that does not conform to the rigid controls designed to
- protect the IT organization's ability to successfully deliver IT services to internal and external Customers.
+ protect the IT organization's ability to successfully deliver IT services to internal and external customers.
</p>
<p>
Release controls typically consist of:
@@ -33,16 +33,13 @@
Ready for transfer to operations and support staff
</li>
</ul></mainDescription>
- <sections xmi:id="_IAJWAuB-EeC1y_NExchKwQ" name="Locate Release Controls" guid="_IAJWAuB-EeC1y_NExchKwQ">
- <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 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>
</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
-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 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>
</sections>
- <sections xmi:id="_IAJWAOB-EeC1y_NExchKwQ" name="Ensure the Team Release Conforms to the Controls" guid="_IAJWAOB-EeC1y_NExchKwQ">
+ <sections xmi:id="_IAJWAOB-EeC1y_NExchKwQ" name="Ensure the team release conforms to the controls" guid="_IAJWAOB-EeC1y_NExchKwQ">
<sectionDescription><p>
Coordinated releases at the program level are very formal processes. They are formal for a very good reason - namely,
the company's production environment could be corrupted and serious business ramifications could result, including:
@@ -52,7 +49,7 @@
Lost revenue
</li>
<li>
- Customer dissatisfaction
+ customer dissatisfaction
</li>
<li>
Fines resulting from legal noncompliance
@@ -62,21 +59,21 @@
</li>
</ul>
<p>
- All Development Teams that contribute to a release are expected to adhere to all the controls defined at the program
- level. Non-compliance could result in multiple impacts:
+ All development team members that contribute to a release are expected to adhere to all the controls defined at the
+ program level. Non-compliance could result in multiple impacts:
</p>
<ul>
<li>
- The entire release being abandoned, which could lead to Customer or End User dissatisfaction
+ The entire release being abandoned, which could lead to customer or end user dissatisfaction
</li>
<li>
The results of multiple feature development Sprint/Iterations not being included in the release
</li>
<li>
- Embarrassment on the part of the Development Team that did not comply
+ Embarrassment on the part of the development team member that did not comply
</li>
<li>
- Loss of funding for that Development Team
+ Loss of funding for that development team
</li>
</ul></sectionDescription>
</sections>
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 102bd44..8e11f0a 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
@@ -1,22 +1,21 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-chKviPT1F1yq5Y_KL9ET9g" name="02_03_verify_successful_deployment,_FCK_gmzvEeCPgecPbK9bdg" guid="-chKviPT1F1yq5Y_KL9ET9g" changeDate="2011-09-13T22:19:16.596-0700" version="7.5.1">
+<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-chKviPT1F1yq5Y_KL9ET9g" name="02_03_verify_successful_deployment,_FCK_gmzvEeCPgecPbK9bdg" guid="-chKviPT1F1yq5Y_KL9ET9g" changeDate="2012-05-30T14:15:13.081-0700" version="7.5.1">
<mainDescription><p>
- Using the success criteria documented either in the Deployment Plan or in the Backout Plan, the Deployment Engineer, in
- collaboration with the Development Team, will determine whether the rollout can be declared a success or not.
+ Using the success criteria documented either in the deployment plan or in the backout plan, the deployment engineer, in
+ collaboration with the development team, will determine whether the rollout can be declared a success or not.
</p>
<p>
If the deployment is successful, the previously prepared release communiques should be delivered. If the deployment is
- unsuccessful, then the Backout Plan should be invoked.
+ unsuccessful, then the backout plan should be invoked.
</p></mainDescription>
- <sections xmi:id="_IAFEleB-EeC1y_NExchKwQ" name="Test Production Release" guid="_IAFEleB-EeC1y_NExchKwQ">
+ <sections xmi:id="_IAFEleB-EeC1y_NExchKwQ" name="Test production release" guid="_IAFEleB-EeC1y_NExchKwQ">
<sectionDescription>In this step, automated smoke tests should be run to determine whether key components were deployed successfully. These
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
-tests should be executed by Development Team Members or Stakeholders recruited specifically for this purpose.</sectionDescription>
+ <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>
</sections>
- <sections xmi:id="_IAFElOB-EeC1y_NExchKwQ" name="Determine if Release Should be Reversed" guid="_IAFElOB-EeC1y_NExchKwQ">
+ <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
the problem(s) associated with the release can be fixed easily, and if they are not detrimental to the production
environment, an emergency bug fix (EBF) might be the answer. In that case, the release is not backed out; rather, an EBF is
diff --git a/epf_prac_151/practice.gen.production_release.base/workproducts/backout_plan.xmi b/epf_prac_151/practice.gen.production_release.base/workproducts/backout_plan.xmi
index 75f5062..5703777 100644
--- a/epf_prac_151/practice.gen.production_release.base/workproducts/backout_plan.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/workproducts/backout_plan.xmi
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-O9dNph5o0Au5C2deOUG8Bg" name="backout_plan,_mfw0wGPoEeCXEsUUiTbOuQ" guid="-O9dNph5o0Au5C2deOUG8Bg" changeDate="2011-08-23T20:00:32.261-0600" version="7.5.1">
+<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-O9dNph5o0Au5C2deOUG8Bg" name="backout_plan,_mfw0wGPoEeCXEsUUiTbOuQ" guid="-O9dNph5o0Au5C2deOUG8Bg" changeDate="2012-05-30T14:24:40.931-0700" version="7.5.1">
<mainDescription><p>
- While someone on the Development Team normally authors a draft version of the Backout Plan, the Deployment Engineer is
- ultimately responsible for its contents and existence. A Backout Plan typically answers the following questions:
+ While someone on the development team normally authors a draft version of the Backout Plan, the Deployment Engineer is
+ ultimately responsible for its contents and existence. A backout plan typically answers the following questions:
</p>
<ul>
<li>
@@ -34,6 +34,6 @@
Has the Backout Plan been successfully tested?
</li>
</ul></mainDescription>
- <purpose>The purpose of this work product is for the Development Team to provide, in one document, all the information needed by the
+ <purpose>The purpose of this work product is for the development team to provide, in one document, all the information needed by the
production support organization to determine if a rollback is needed, who will authorize it, how it will be performed, etc.</purpose>
</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/epf_prac_151/practice.gen.production_release.base/workproducts/deployment_plan.xmi b/epf_prac_151/practice.gen.production_release.base/workproducts/deployment_plan.xmi
index aa7a606..0103f54 100644
--- a/epf_prac_151/practice.gen.production_release.base/workproducts/deployment_plan.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/workproducts/deployment_plan.xmi
@@ -1,14 +1,14 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-4Fv0TSuJBCRxarK5ssyLGw" name="deployment_plan,_j0qgcGPoEeCXEsUUiTbOuQ" guid="-4Fv0TSuJBCRxarK5ssyLGw" changeDate="2011-10-15T12:01:51.928-0600" version="7.5.1">
+<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-4Fv0TSuJBCRxarK5ssyLGw" name="deployment_plan,_j0qgcGPoEeCXEsUUiTbOuQ" guid="-4Fv0TSuJBCRxarK5ssyLGw" changeDate="2012-05-30T14:25:00.538-0700" version="7.5.1">
<mainDescription><p>
- The Deployment Plan should contain the unique instructions for deploying a particular version of a product. By "unique
- instructions" we mean those things that are not part of a Deployment Engineer's normal procedures. Rather, they often
- are specific procedures and timing constraints that a Deployment Engineer should be aware of as they are rolling out a
+ The deployment plan should contain the unique instructions for deploying a particular version of a product. By "unique
+ instructions" we mean those things that are not part of a deployment engineer's normal procedures. Rather, they often
+ are specific procedures and timing constraints that a deployment engineer should be aware of as they are rolling out a
particular release.
</p>
<p>
- While&nbsp;a draft version of the&nbsp;Deployment Plan is typically developed by a Development Team, the Deployment
- Engineer is responsible for its contents and existence.&nbsp;A Deployment Plan&nbsp;normally consists of the following
+ While&nbsp;a draft version of the&nbsp;deployment plan is typically developed by a development team, the deployment
+ engineer is responsible for its contents and existence.&nbsp;A deployment plan&nbsp;normally consists of the following
sections:
</p>
<ul>
@@ -22,13 +22,13 @@
The risks or issues associated with the release based on a risk assessment
</li>
<li>
- The customer organization, Stakeholders, and End User community that will be impacted by the release
+ The customer organization, stakeholders, and end user community that will be impacted by the release
</li>
<li>
The person or persons who have the authority to approve the release as "ready for production"
</li>
<li>
- The Development Team members responsible for delivering the release package to the Deployment Manager, along with
+ The development team members responsible for delivering the release package to the Deployment Manager, along with
contact information
</li>
<li>
@@ -40,6 +40,6 @@
successful so it can report success
</li>
</ul></mainDescription>
- <purpose>The purpose of this work product is to capture, in one document, the unique information that will be consumed by Deployment
-Engineers before and during the deployment to production of a particular release package.</purpose>
+ <purpose>The purpose of this work product is to capture, in one document, the unique information that will be consumed by deployment
+engineers before and during the deployment to production of a particular release package.</purpose>
</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/epf_prac_151/practice.gen.production_release.base/workproducts/release.xmi b/epf_prac_151/practice.gen.production_release.base/workproducts/release.xmi
index 4139d79..d76f4c9 100644
--- a/epf_prac_151/practice.gen.production_release.base/workproducts/release.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/workproducts/release.xmi
@@ -1,12 +1,12 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:DeliverableDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-Lo_rjBFuf6JDjdUw5nJjYw" name="new_deliverable,_EopWMPddEeCG79QDqBlPXg" guid="-Lo_rjBFuf6JDjdUw5nJjYw" version="7.5.1">
+<org.eclipse.epf.uma:DeliverableDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-Lo_rjBFuf6JDjdUw5nJjYw" name="new_deliverable,_EopWMPddEeCG79QDqBlPXg" guid="-Lo_rjBFuf6JDjdUw5nJjYw" changeDate="2012-05-30T14:26:25.810-0700" version="7.5.1">
<mainDescription><p>
- A Release consists of integrated, compiled code that runs cleanly, independently, and in its entirety. This is an
- important rule because in order to be released or even "potentially shippable," a Release increment must be able to
+ A release consists of integrated, compiled code that runs cleanly, independently, and in its entirety. This is an
+ important rule because in order to be released or even "potentially shippable," a release increment must be able to
stand on its own, otherwise it is not shippable. Releases&nbsp;can be created at either the program or team level.
</p>
<p>
- There are three potential uses for a Release:
+ There are three potential uses for a release:
</p>
<ul>
<li>
@@ -15,40 +15,40 @@
beginning of a new product lifecycle.
</li>
<li>
- <strong>It is used by Beta Customers and the Program Manager:</strong> It allows End Users to test it in a Beta
+ <strong>It is used by beta customers and the program manager:</strong> It allows end users to test it in a Beta
test environment, which provides immediate feedback and reduces risks associated with user interface ergonomics.
- Customer feedback will influence the Program Backlog for later consideration.
+ customer feedback will influence the program backlog for later consideration.
</li>
<li>
- <strong>It is deployed or shipped and used by End Users:</strong> This result provides immediate value to the End
- Users.
+ <strong>It is deployed or shipped and used by end users:</strong> This result provides immediate value to the end
+ users.
</li>
</ul>
<p>
- In many organizations, a program Release typically is timeboxed to 2 to 3 months of development effort and 2 to 4 weeks
- of hardening which results in a scheduled release approximately every 90 days. Releases for individual Development
- Teams usually occur more often than those for programs, but there are no hard and fast rules regarding how often
+ In many organizations, a program release typically is timeboxed to 2 to 3 months of development effort and 2 to 4 weeks
+ of hardening which results in a scheduled release approximately every 90 days. Releases for individual development
+ teams usually occur more often than those for programs, but there are no hard and fast rules regarding how often
releases should be scheduled. The only requirement is that working software should be delivered "frequently" by both
- Development Teams and programs. Although the example timeframe described above is arbitrary, empirical evidence
+ development teams and programs. Although the example timeframe described above is arbitrary, empirical evidence
suggests it is about right for most companies and fits nicely into quarterly planning cycles.
</p>
<p>
- Each Release has a set of release objectives and a projected delivery date; it also has a planned number of
- Sprint/Iterations. For example, a brief description of a release might be: "The goal of Release 2 is to provide B2B
- scheduling capability for the Ordering and Logistics Department. The Release is targeted for June 31 and will consist
- of five 2-week Feature Development Sprint/Iterations and&nbsp;one 2-week Release Sprint/Iteration."
+ Each release has a set of release objectives and a projected delivery date; it also has a planned number of
+ sprint/iterations. For example, a brief description of a release might be: "The goal of Release 2 is to provide B2B
+ scheduling capability for the Ordering and Logistics Department. The release is targeted for June 31 and will consist
+ of five 2-week feature development sprint/iterations and&nbsp;one 2-week release sprint/iteration."
</p></mainDescription>
<purpose><p>
The purpose of this work product is to:
</p>
<ul>
<li>
- At the team level, bring closure to a Sprint/Iteration or series of Sprint/Iterations by delivering working, tested
- software that can be potentially used by the End User community for whom the system was (or is being) developed
+ At the team level, bring closure to a sprint/iteration or series of sprint/iterations by delivering working, tested
+ software that can be potentially used by the end user community for whom the system was (or is being) developed
</li>
<li>
- At the program level, deliver an integrated, value-added product increment to Customers that was developed in
- parallel by multiple, coordinated, and synchronized Development Teams
+ At the program level, deliver an integrated, value-added product increment to customers that was developed in
+ parallel by multiple, coordinated, and synchronized development team members
</li>
</ul></purpose>
</org.eclipse.epf.uma:DeliverableDescription>
diff --git a/epf_prac_151/practice.gen.production_release.base/workproducts/release_communications.xmi b/epf_prac_151/practice.gen.production_release.base/workproducts/release_communications.xmi
index 5cd1da8..6ebef8c 100644
--- a/epf_prac_151/practice.gen.production_release.base/workproducts/release_communications.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/workproducts/release_communications.xmi
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-wHkXWtQxFeicCBDHK-f7xg" name="release_communications,_pQGOYGPoEeCXEsUUiTbOuQ" guid="-wHkXWtQxFeicCBDHK-f7xg" changeDate="2011-08-23T20:04:58.598-0600" version="7.5.1">
+<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-wHkXWtQxFeicCBDHK-f7xg" name="release_communications,_pQGOYGPoEeCXEsUUiTbOuQ" guid="-wHkXWtQxFeicCBDHK-f7xg" changeDate="2012-05-30T14:28:28.971-0700" version="7.5.1">
<mainDescription><p>
- Sometimes, depending on the product user base, separate communiques might need to be prepared for each Stakeholder
+ Sometimes, depending on the product user base, separate communiques might need to be prepared for each stakeholder
group. In that case, this artifact should specify the different groups to which communications are directed, the method
of communication (e.g., email, text or pager message, bulletin, newsletter, phone message, etc.). All communiques
should be prepared in advance so that it is a matter of disseminating information when the release to production has
@@ -13,30 +13,30 @@
communiques.
</p>
<p>
- While there is no prescribed format for the Release Communications artifact, each communique should indicate the
+ While there is no prescribed format for the release communications artifact, each communique should indicate the
preferred delivery mechanisms (e.g., beeper notification, telephone calls, a posting to an internal release website,
live or pre-recorded presentations by senior management, etc.) and generally answer the following questions:
</p>
<ul>
<li>
- Who are the parties (Stakeholders) that are interested in knowing that a release to production has taken place?
+ Who are the parties (stakeholders) that are interested in knowing that a release to production has taken place?
</li>
<li>
What specifically (features, functions, components) has been placed into production?
</li>
<li>
- Why is this release valuable to Stakeholders and what business purpose does it serve?
+ Why is this release valuable to stakeholders and what business purpose does it serve?
</li>
<li>
Where is the product available (on which platforms, geographical locations, business units, etc.)?
</li>
<li>
- How can the Stakeholders access the system and under what circumstances?
+ How can the stakeholders access the system and under what circumstances?
</li>
<li>
When was the product released (or when will it be released if the release date is in the future)?
</li>
</ul></mainDescription>
- <purpose>The purpose of this work product is to inform all the various Stakeholders that a release to production has taken place and
+ <purpose>The purpose of this work product is to inform all the various stakeholders that a release to production has taken place and
the implemented features are now generally available.</purpose>
</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/epf_prac_151/practice.mgmt.iterative_dev.base/guidances/concepts/micro_increments.xmi b/epf_prac_151/practice.mgmt.iterative_dev.base/guidances/concepts/micro_increments.xmi
index 5bd5a21..0b481c0 100644
--- a/epf_prac_151/practice.mgmt.iterative_dev.base/guidances/concepts/micro_increments.xmi
+++ b/epf_prac_151/practice.mgmt.iterative_dev.base/guidances/concepts/micro_increments.xmi
@@ -14,9 +14,9 @@
</p>
<ul>
<li>
- <b>Identify Stakeholders<em>.</em></b> Defining a shared vision is a task that can drag on for weeks, so to ensure
+ <b>Identify stakeholders<em>.</em></b> Defining a shared vision is a task that can drag on for weeks, so to ensure
that you make and track daily progress, divide the task into small and well-defined micro-increments. Describing
- and getting buy-in on which Stakeholders to put into a Vision document is a meaningful result, and may take a few
+ and getting buy-in on which stakeholders to put into a Vision document is a meaningful result, and may take a few
hours or at most a few days, and thus represents a suitable micro-increment.
</li>
<li>
diff --git a/epf_prac_151/practice.mgmt.iterative_dev.base/guidances/guidelines/iteration_assessment.xmi b/epf_prac_151/practice.mgmt.iterative_dev.base/guidances/guidelines/iteration_assessment.xmi
index a988d44..3fcd4a1 100644
--- a/epf_prac_151/practice.mgmt.iterative_dev.base/guidances/guidelines/iteration_assessment.xmi
+++ b/epf_prac_151/practice.mgmt.iterative_dev.base/guidances/guidelines/iteration_assessment.xmi
@@ -48,7 +48,7 @@
</li>
</ul>
<p>
- Stakeholders and the team may also agree that there is sufficient functionality in the system to provide immediate
+ stakeholders and the team may also agree that there is sufficient functionality in the system to provide immediate
business value, and they may decide to put the solution into production. In that case, discuss what deployment-related
work items should be added to the <a class="elementLink"
href="./../../../core.mgmt.slot.base/workproducts/project_work_slot_F12BAC46.html"
diff --git a/epf_prac_151/practice.mgmt.iterative_dev.base/guidances/guidelines/prioritizing_work_items.xmi b/epf_prac_151/practice.mgmt.iterative_dev.base/guidances/guidelines/prioritizing_work_items.xmi
index 0bd49c7..4077f5e 100644
--- a/epf_prac_151/practice.mgmt.iterative_dev.base/guidances/guidelines/prioritizing_work_items.xmi
+++ b/epf_prac_151/practice.mgmt.iterative_dev.base/guidances/guidelines/prioritizing_work_items.xmi
@@ -37,7 +37,7 @@
of the paying stakeholders.
</li>
<li>
- Stakeholders&nbsp;that pay for the application have the final say on what capabilities to prioritize.
+ stakeholders&nbsp;that pay for the application have the final say on what capabilities to prioritize.
</li>
</ul>
<h3>
diff --git a/epf_prac_151/practice.mgmt.project_process_tailoring.base/guidances/examples/development_case_project.xmi b/epf_prac_151/practice.mgmt.project_process_tailoring.base/guidances/examples/development_case_project.xmi
index 3a05fb2..89fb5dc 100644
--- a/epf_prac_151/practice.mgmt.project_process_tailoring.base/guidances/examples/development_case_project.xmi
+++ b/epf_prac_151/practice.mgmt.project_process_tailoring.base/guidances/examples/development_case_project.xmi
@@ -55,7 +55,7 @@
<li style="LIST-STYLE-TYPE: none">
<ul type="circle">
<li>
- Stakeholder consensus achieved
+ stakeholder consensus achieved
</li>
</ul>
</li>
diff --git a/epf_prac_151/practice.mgmt.project_process_tailoring.base/guidances/templates/development_case.xmi b/epf_prac_151/practice.mgmt.project_process_tailoring.base/guidances/templates/development_case.xmi
index b4db163..e577182 100644
--- a/epf_prac_151/practice.mgmt.project_process_tailoring.base/guidances/templates/development_case.xmi
+++ b/epf_prac_151/practice.mgmt.project_process_tailoring.base/guidances/templates/development_case.xmi
@@ -338,7 +338,7 @@
<li>
<div>
<em><font color="#0000ff">To describe any changes in the set of roles; for example, it is common to refine the
- role Stakeholder into more than one role.</font></em>
+ role stakeholder into more than one role.</font></em>
</div>
</li>
<li>
@@ -359,7 +359,7 @@
<li>
<div>
<em><font color="#0000ff">Role: Identify the roles used on your project. For example, it is common to refine
- the role Stakeholder into more than one role. You might need to add new roles or clarify how each role is used
+ the role stakeholder into more than one role. You might need to add new roles or clarify how each role is used
in the organization by providing role names commonly used in your organization</font></em>
</div>
</li>
diff --git a/epf_prac_151/practice.mgmt.release_planning.base/guidances/guidelines/staffing_project.xmi b/epf_prac_151/practice.mgmt.release_planning.base/guidances/guidelines/staffing_project.xmi
index 351b3c5..9e02786 100644
--- a/epf_prac_151/practice.mgmt.release_planning.base/guidances/guidelines/staffing_project.xmi
+++ b/epf_prac_151/practice.mgmt.release_planning.base/guidances/guidelines/staffing_project.xmi
@@ -26,7 +26,7 @@
understanding of the software development process and the business domain offers.
</li>
<li>
- Include stakeholders. Stakeholders, including business stakeholders (such as end users) and technical stakeholders
+ Include stakeholders. stakeholders, including business stakeholders (such as end users) and technical stakeholders
(such as operations staff), can add significant value to your team. Instead of just interviewing them to gain
information from them, or asking them to review your work, why not include them as active participants on the team?
</li>
diff --git a/epf_prac_151/practice.tech.abrd.base/disciplines/rule_governance.xmi b/epf_prac_151/practice.tech.abrd.base/disciplines/rule_governance.xmi
index c959bbb..beb4f21 100644
--- a/epf_prac_151/practice.tech.abrd.base/disciplines/rule_governance.xmi
+++ b/epf_prac_151/practice.tech.abrd.base/disciplines/rule_governance.xmi
@@ -4,7 +4,7 @@
<p style="MARGIN: 0in 0in 0pt" class="MsoNormal">
<span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">Developing or customizing the governance
processes is an incremental activity. As the processes are deployed across departments, there are always tension
- between IT and Business teams. The idea is to start simple, and involve IT and Business Stakeholders in the process
+ between IT and Business teams. The idea is to start simple, and involve IT and Business stakeholders in the process
design. After first implementation it is possible to fine tune the processes.</span>
</p><br style="MARGIN: 3pt 0cm" class="MsoNormal" />
<br />
diff --git a/epf_prac_151/practice.tech.concurrent_testing.base/tasks/create_test_cases.xmi b/epf_prac_151/practice.tech.concurrent_testing.base/tasks/create_test_cases.xmi
index 6b999de..35db301 100644
--- a/epf_prac_151/practice.tech.concurrent_testing.base/tasks/create_test_cases.xmi
+++ b/epf_prac_151/practice.tech.concurrent_testing.base/tasks/create_test_cases.xmi
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="_NrVKsKeqEdmKDbQuyzCoqQ" name="create_test_cases,_0iwc0clgEdmt3adZL5Dmdw" guid="_NrVKsKeqEdmKDbQuyzCoqQ" changeDate="2007-02-07T03:38:57.000-0800" version="1.0.0">
<keyConsiderations><p>
- Develop test cases in parallel with requirements so that Analysts and Stakeholders can agree with the specific
+ Develop test cases in parallel with requirements so that Analysts and stakeholders can agree with the specific
conditions of satisfaction for each requirement. The test cases act as acceptance criteria by expanding on the intent
of the system&nbsp;through actual scenarios of use.&nbsp;This allows team members to measure progress in terms of
passing test cases.&nbsp;
@@ -56,7 +56,7 @@
</p>
<p>
Ask the participants to agree that if <em>these test cases pass</em>, they will consider these requirements
- implemented.&nbsp; Elicit additional test ideas from Analysts and Stakeholders to ensure you understand the expected
+ implemented.&nbsp; Elicit additional test ideas from Analysts and stakeholders to ensure you understand the expected
behavior of the scenario.
</p>
<p>
diff --git a/epf_prac_151/practice.tech.evolutionary_design.base/tasks/design_solution.xmi b/epf_prac_151/practice.tech.evolutionary_design.base/tasks/design_solution.xmi
index 980e419..c0c3629 100644
--- a/epf_prac_151/practice.tech.evolutionary_design.base/tasks/design_solution.xmi
+++ b/epf_prac_151/practice.tech.evolutionary_design.base/tasks/design_solution.xmi
@@ -57,7 +57,7 @@
guid="_i3vkoLS-EduDY8LNbMCDBA">[Technical Specification]</a>&nbsp;to understand the scope of the design task and the
expectations on the <a class="elementLink"
href="./../../practice.tech.evolutionary_design.base/workproducts/design_D677D182.html"
- guid="_0WuL8slgEdmt3adZL5Dmdw">Design</a>. Work with the Stakeholder and Analyst to clarify ambiguous or missing
+ guid="_0WuL8slgEdmt3adZL5Dmdw">Design</a>. Work with the stakeholder and Analyst to clarify ambiguous or missing
information.
</p>
<p>
diff --git a/epf_prac_151/practice.tech.shared_vision.base/guidances/roadmaps/how_to_adopt.xmi b/epf_prac_151/practice.tech.shared_vision.base/guidances/roadmaps/how_to_adopt.xmi
index 87e8b91..4c024d6 100644
--- a/epf_prac_151/practice.tech.shared_vision.base/guidances/roadmaps/how_to_adopt.xmi
+++ b/epf_prac_151/practice.tech.shared_vision.base/guidances/roadmaps/how_to_adopt.xmi
@@ -27,7 +27,7 @@
<ul>
<li>
Requirements practices: the vision is one of the outcomes of stakeholder requests elicitation. It is also the
- primary input for developing more fine-grained technical requirements. Stakeholders and the development team use
+ primary input for developing more fine-grained technical requirements. stakeholders and the development team use
the vision to provide the context and high-level objectives for the detailed technical requirements.
</li>
<li>
diff --git a/epf_prac_151/practice.tech.shared_vision.base/tasks/develop_technical_vision.xmi b/epf_prac_151/practice.tech.shared_vision.base/tasks/develop_technical_vision.xmi
index 0f3d188..efa1d7e 100644
--- a/epf_prac_151/practice.tech.shared_vision.base/tasks/develop_technical_vision.xmi
+++ b/epf_prac_151/practice.tech.shared_vision.base/tasks/develop_technical_vision.xmi
@@ -3,7 +3,7 @@
<keyConsiderations><p>
Use-case modeling&nbsp;is one technique that can prove useful in defining the system boundaries and system behavior.
</p></keyConsiderations>
- <sections xmi:id="_ceK-UED2EdyoefaQkqWN_Q" name="Identify Stakeholders" guid="_ceK-UED2EdyoefaQkqWN_Q">
+ <sections xmi:id="_ceK-UED2EdyoefaQkqWN_Q" name="Identify stakeholders" guid="_ceK-UED2EdyoefaQkqWN_Q">
<sectionDescription>Identify the stakeholders: decision-makers, customers, potential users, partners, domain experts, industry analysts and
other interested parties. Briefly describe what stakeholders do and what their responsibilities are with regard to the
system being developed.</sectionDescription>
@@ -56,7 +56,7 @@
business and technical terms.&nbsp; Work with stakeholders to continually expand and refine the glossary throughout the
project lifecycle.</sectionDescription>
</sections>
- <purpose>The solution is proposed for a problem that everybody agrees on. Stakeholders collaborate with the development team to
+ <purpose>The solution is proposed for a problem that everybody agrees on. stakeholders collaborate with the development team to
express and document their problems, needs, and potential features for the system to be, so the project team can better
understand what has to be done.</purpose>
</org.eclipse.epf.uma:TaskDescription>
diff --git a/epf_prac_151/practice.tech.use_case_driven_dev.base/guidances/guidelines/use_case_model.xmi b/epf_prac_151/practice.tech.use_case_driven_dev.base/guidances/guidelines/use_case_model.xmi
index 1da4cf7..3c1fe3a 100644
--- a/epf_prac_151/practice.tech.use_case_driven_dev.base/guidances/guidelines/use_case_model.xmi
+++ b/epf_prac_151/practice.tech.use_case_driven_dev.base/guidances/guidelines/use_case_model.xmi
@@ -45,7 +45,7 @@
</p>
<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
<h5>
- Identify Stakeholders
+ Identify stakeholders
</h5>
<p>
Begin by listing all the external stakeholders for the system.&nbsp; These individuals will be the source of the
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/construction_phase_iteration/content.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/construction_phase_iteration/content.xmi
index 503b141..0e6f526 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/construction_phase_iteration/content.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/construction_phase_iteration/content.xmi
@@ -149,7 +149,7 @@
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-nIF2UE5rqiDXuJIzOZcQuA" name="create_test_cases,_AVhA0tOOEdyqlogshP8l4g" guid="-nIF2UE5rqiDXuJIzOZcQuA">
<keyConsiderations><p>
- Develop test cases in parallel with requirements so that Analysts and Stakeholders can agree with the specific
+ Develop test cases in parallel with requirements so that Analysts and stakeholders can agree with the specific
conditions of satisfaction for each requirement. The test cases act as acceptance criteria by expanding on the intent
of the system&nbsp;through actual scenarios of use.&nbsp;This allows team members to measure progress in terms of
passing test cases.&nbsp;
@@ -222,7 +222,7 @@
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-mx51ATVqsnhmw5TcEQIYYw" name="plan_deployment,_DZttwJlXEeGlkdGl1HQlDA" guid="-mx51ATVqsnhmw5TcEQIYYw">
<refinedDescription><p>
- Because a Deployment Engineer is responsible for accepting the results of one or more Development Teams and deploying those
+ Because a Deployment Engineer is responsible for accepting the results of one or more development team members and deploying those
integrated releases into the production environment, it is important for all parties to agree on the details of a
particular release. The Deployment Plan documents, in one place, all the information that will be consumed by the
Deployment Engineer before and during the deployment to production of a particular release package.
@@ -246,7 +246,7 @@
particular release.
</p>
<p>
- While&nbsp;a draft version of the&nbsp;Deployment Plan is typically developed by a Development Team, the Deployment
+ While&nbsp;a draft version of the&nbsp;Deployment Plan is typically developed by a development team, the Deployment
Engineer is responsible for its contents and existence.&nbsp;A Deployment Plan&nbsp;normally consists of the following
sections:
</p>
@@ -261,13 +261,13 @@
The risks or issues associated with the release based on a risk assessment
</li>
<li>
- The customer organization, Stakeholders, and End User community that will be impacted by the release
+ The customer organization, stakeholders, and End User community that will be impacted by the release
</li>
<li>
The person or persons who have the authority to approve the release as "ready for production"
</li>
<li>
- The Development Team members responsible for delivering the release package to the Deployment Manager, along with
+ The development team members responsible for delivering the release package to the Deployment Manager, along with
contact information
</li>
<li>
@@ -282,7 +282,7 @@
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-FcJEVCc4jEBKZPGYLseZkQ" name="backout_plan,_DaTjoplXEeGlkdGl1HQlDA" guid="-FcJEVCc4jEBKZPGYLseZkQ">
<refinedDescription><p>
- While someone on the Development Team normally authors a draft version of the Backout Plan, the Deployment Engineer is
+ While someone on the development team normally authors a draft version of the Backout Plan, the Deployment Engineer is
ultimately responsible for its contents and existence. A Backout Plan typically answers the following questions:
</p>
<ul>
@@ -318,7 +318,7 @@
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-M8RcfIWzEdq2ZYUeLZoX4Q" name="release_communications,_DaTjpZlXEeGlkdGl1HQlDA" guid="-M8RcfIWzEdq2ZYUeLZoX4Q">
<refinedDescription><p>
- Sometimes, depending on the product user base, separate communiques might need to be prepared for each Stakeholder
+ Sometimes, depending on the product user base, separate communiques might need to be prepared for each stakeholder
group. In that case, this artifact should specify the different groups to which communications are directed, the method
of communication (e.g., email, text or pager message, bulletin, newsletter, phone message, etc.). All communiques
should be prepared in advance so that it is a matter of disseminating information when the release to production has
@@ -342,13 +342,13 @@
What specifically (features, functions, components) has been placed into production?
</li>
<li>
- Why is this release valuable to Stakeholders and what business purpose does it serve?
+ Why is this release valuable to stakeholders and what business purpose does it serve?
</li>
<li>
Where is the product available (on which platforms, geographical locations, business units, etc.)?
</li>
<li>
- How can the Stakeholders access the system and under what circumstances?
+ How can the stakeholders access the system and under what circumstances?
</li>
<li>
When was the product released (or when will it be released if the release date is in the future)?
@@ -385,7 +385,7 @@
of hardening which results in a scheduled release approximately every 90 days. Releases for individual Development
Teams usually occur more often than those for programs, but there are no hard and fast rules regarding how often
releases should be scheduled. The only requirement is that working software should be delivered "frequently" by both
- Development Teams and programs. Although the example timeframe described above is arbitrary, empirical evidence
+ development teams and programs. Although the example timeframe described above is arbitrary, empirical evidence
suggests it is about right for most companies and fits nicely into quarterly planning cycles.
</p>
<p>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/deploy_release_to_production/model.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/deploy_release_to_production/model.xmi
index 7b8c6f3..d470a75 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/deploy_release_to_production/model.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/deploy_release_to_production/model.xmi
@@ -59,7 +59,7 @@
<selectedSteps href="uma://-mHGd7nm4EywKy0UPe9dZhg#_IAD2cuB-EeC1y_NExchKwQ"/>
<selectedSteps href="uma://-mHGd7nm4EywKy0UPe9dZhg#_IAD2ceB-EeC1y_NExchKwQ"/>
</processElements>
- <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_y7a0JZiLEeGOvpP1fVrVNA" name="deliver_release_communications" guid="_y7a0JZiLEeGOvpP1fVrVNA" presentationName="Deliver Release Communications" briefDescription="After a product release has been declared a success and is available for use, all relevant Stakeholders should receive a communique stating that fact." isPlanned="true" superActivities="_y7a0GZiLEeGOvpP1fVrVNA" mandatoryInput="_y7a0H5iLEeGOvpP1fVrVNA" optionalInput="_y7a0I5iLEeGOvpP1fVrVNA">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_y7a0JZiLEeGOvpP1fVrVNA" name="deliver_release_communications" guid="_y7a0JZiLEeGOvpP1fVrVNA" presentationName="Deliver Release Communications" briefDescription="After a product release has been declared a success and is available for use, all relevant stakeholders should receive a communique stating that fact." isPlanned="true" superActivities="_y7a0GZiLEeGOvpP1fVrVNA" mandatoryInput="_y7a0H5iLEeGOvpP1fVrVNA" optionalInput="_y7a0I5iLEeGOvpP1fVrVNA">
<methodElementProperty xmi:id="_FP30hZoPEeGnJt_Qpwdfdg" name="me_references" value="<?xml version="1.0" encoding="UTF-8"?><me_references udtList=""/>"/>
<presentation xmi:id="-yQw-_bdY-Wc4UaWalfL27Q" href="uma://-zxy4hzFT2yBzt2lUjCwnqA#-yQw-_bdY-Wc4UaWalfL27Q"/>
<Task href="uma://_mYfo8OCIEeC1y_NExchKwQ#_IAEdhuB-EeC1y_NExchKwQ"/>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/elaboration_phase_iteration/content.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/elaboration_phase_iteration/content.xmi
index b6846ce..eeea08e 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/elaboration_phase_iteration/content.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/elaboration_phase_iteration/content.xmi
@@ -68,7 +68,7 @@
</org.eclipse.epf.uma:ProcessDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-n6Q-ulwXte8wbHfbdgJuXQ" name="plan_deployment,_oaBE0JigEeGlkdGl1HQlDA" guid="-n6Q-ulwXte8wbHfbdgJuXQ">
<refinedDescription><p>
- Because a Deployment Engineer is responsible for accepting the results of one or more Development Teams and deploying those
+ Because a Deployment Engineer is responsible for accepting the results of one or more development team members and deploying those
integrated releases into the production environment, it is important for all parties to agree on the details of a
particular release. The Deployment Plan documents, in one place, all the information that will be consumed by the
Deployment Engineer before and during the deployment to production of a particular release package.
@@ -92,7 +92,7 @@
particular release.
</p>
<p>
- While&nbsp;a draft version of the&nbsp;Deployment Plan is typically developed by a Development Team, the Deployment
+ While&nbsp;a draft version of the&nbsp;Deployment Plan is typically developed by a development team, the Deployment
Engineer is responsible for its contents and existence.&nbsp;A Deployment Plan&nbsp;normally consists of the following
sections:
</p>
@@ -107,13 +107,13 @@
The risks or issues associated with the release based on a risk assessment
</li>
<li>
- The customer organization, Stakeholders, and End User community that will be impacted by the release
+ The customer organization, stakeholders, and End User community that will be impacted by the release
</li>
<li>
The person or persons who have the authority to approve the release as "ready for production"
</li>
<li>
- The Development Team members responsible for delivering the release package to the Deployment Manager, along with
+ The development team members responsible for delivering the release package to the Deployment Manager, along with
contact information
</li>
<li>
@@ -128,7 +128,7 @@
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-r0AuJYtQwfZHI7WFZFRAVg" name="backout_plan,_oanhw5igEeGlkdGl1HQlDA" guid="-r0AuJYtQwfZHI7WFZFRAVg">
<refinedDescription><p>
- While someone on the Development Team normally authors a draft version of the Backout Plan, the Deployment Engineer is
+ While someone on the development team normally authors a draft version of the Backout Plan, the Deployment Engineer is
ultimately responsible for its contents and existence. A Backout Plan typically answers the following questions:
</p>
<ul>
@@ -164,7 +164,7 @@
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-dklyw-kN1blOVTzIdtlryg" name="release_communications,_oanhxpigEeGlkdGl1HQlDA" guid="-dklyw-kN1blOVTzIdtlryg">
<refinedDescription><p>
- Sometimes, depending on the product user base, separate communiques might need to be prepared for each Stakeholder
+ Sometimes, depending on the product user base, separate communiques might need to be prepared for each stakeholder
group. In that case, this artifact should specify the different groups to which communications are directed, the method
of communication (e.g., email, text or pager message, bulletin, newsletter, phone message, etc.). All communiques
should be prepared in advance so that it is a matter of disseminating information when the release to production has
@@ -188,13 +188,13 @@
What specifically (features, functions, components) has been placed into production?
</li>
<li>
- Why is this release valuable to Stakeholders and what business purpose does it serve?
+ Why is this release valuable to stakeholders and what business purpose does it serve?
</li>
<li>
Where is the product available (on which platforms, geographical locations, business units, etc.)?
</li>
<li>
- How can the Stakeholders access the system and under what circumstances?
+ How can the stakeholders access the system and under what circumstances?
</li>
<li>
When was the product released (or when will it be released if the release date is in the future)?
@@ -231,7 +231,7 @@
of hardening which results in a scheduled release approximately every 90 days. Releases for individual Development
Teams usually occur more often than those for programs, but there are no hard and fast rules regarding how often
releases should be scheduled. The only requirement is that working software should be delivered "frequently" by both
- Development Teams and programs. Although the example timeframe described above is arbitrary, empirical evidence
+ development teams and programs. Although the example timeframe described above is arbitrary, empirical evidence
suggests it is about right for most companies and fits nicely into quarterly planning cycles.
</p>
<p>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/identify_and_refine_requirements/content.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/identify_and_refine_requirements/content.xmi
index 42464bd..8bf002c 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/identify_and_refine_requirements/content.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/identify_and_refine_requirements/content.xmi
@@ -109,7 +109,7 @@
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-Afh79qcpEs6i404AABE0rA" name="create_test_cases,_HDOWUNOLEdyqlogshP8l4g" guid="-Afh79qcpEs6i404AABE0rA">
<keyConsiderations><p>
- Develop test cases in parallel with requirements so that Analysts and Stakeholders can agree with the specific
+ Develop test cases in parallel with requirements so that Analysts and stakeholders can agree with the specific
conditions of satisfaction for each requirement. The test cases act as acceptance criteria by expanding on the intent
of the system&nbsp;through actual scenarios of use.&nbsp;This allows team members to measure progress in terms of
passing test cases.&nbsp;
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/prep_doc_trng/content.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/prep_doc_trng/content.xmi
index f80ae05..3ca97af 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/prep_doc_trng/content.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/prep_doc_trng/content.xmi
@@ -2,19 +2,19 @@
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1">
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-fz8LKMHNt9wb0sZo4mO04w" name="01_01_create_update_product_documenation,_VpCWQPd3EeCFmpfCmMPILg" guid="-fz8LKMHNt9wb0sZo4mO04w">
<refinedDescription><p>
- Development Team Members sometimes take documentation for granted, or do not give it enough consideration. However,
+ Development team members sometimes take documentation for granted, or do not give it enough consideration. However,
after a product is delivered, Customers who pay for the system and for support often do not have enough information to
effectively manage the product.
</p>
<p>
- If a Technical Writer is made available to a Development Team, that role often takes the burden off the team for
+ If a Technical Writer is made available to a development team, that role often takes the burden off the team for
developing the formal product documentation and for ensuring that it is in the correct format and business language. If
- a Technical Writer is not available, the Development Team and Product Owner must make every effort to create enough
+ a Technical Writer is not available, the development team and Product Owner must make every effort to create enough
documentation to ensure that the features that have been developed for each Release are understood and can be
- communicated effectively by the paying Customer to their Stakeholders.
+ communicated effectively by the paying Customer to their stakeholders.
</p>
<p>
- Delivering a professionally developed product requires that a Development Team provide the Customer with accurate,
+ Delivering a professionally developed product requires that a development team provide the Customer with accurate,
detailed, and comprehensive product documentation.
</p></refinedDescription>
</org.eclipse.epf.uma:DescriptorDescription>
@@ -26,7 +26,7 @@
be any better.
</p>
<p>
- Without good user documentation, a system might be well developed by a Development Team but might not meet the End User's
+ Without good user documentation, a system might be well developed by a development team but might not meet the End User's
expectations because they will not be able operate the application effectively.
</p></refinedDescription>
</org.eclipse.epf.uma:DescriptorDescription>
@@ -38,7 +38,7 @@
product documentation, which normally is written for the lay person.
</p>
<p>
- The Development Team should do its best to make sure that personnel who perform an IT support role have the right amount and
+ The development team should do its best to make sure that personnel who perform an IT support role have the right amount and
the relevant type of information necessary to support the application, whether they provide Tier 1, Tier 2, or Tier 3
support. Support documentation often is developed based on these three different support categories. How
effectively the code base is commented and the ease with which those comments are found and understood contributes to
@@ -47,7 +47,7 @@
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-qS1z2DJT2_jfCUcou-xFYw" name="technical_writer,_VpIc4Pd3EeCFmpfCmMPILg" guid="-qS1z2DJT2_jfCUcou-xFYw">
<refinedDescription><p>
- Some organizations might engage a Technical Writer to help a Development Team review and refine the documentation that
+ Some organizations might engage a Technical Writer to help a development team review and refine the documentation that
is produced by the team during a Sprint/Iteration in support of delivered features.
</p>
<p>
@@ -61,7 +61,7 @@
to the team.</keyConsiderations>
<refinedDescription><p>
This role is the one and only person responsible for managing the Product Backlog and ensuring the value of the work
- the Development Team performs. The Product Owner has the responsibility of defining what is the right product to build,
+ the development team performs. The Product Owner has the responsibility of defining what is the right product to build,
determining the order in which features will be built, and making sure that the product actually works. The Product
Owner is responsible for defining the features of the product to be developed by the team in terms of:
</p>
@@ -105,7 +105,7 @@
</ul>
<p>
This person maintains the Product Backlog and ensures that it is visible to everyone. Everyone understands what items
- have the highest priority, so everyone on the Development Team knows what will be worked on.
+ have the highest priority, so everyone on the development team knows what will be worked on.
</p>
<p>
The Product Owner is one person, not a committee. Committees may exist that advise or influence this person but team
@@ -114,18 +114,18 @@
</p>
<p>
For the Product Owner to succeed, everyone in the organization must respect their decisions. No one is allowed to
- direct the Development Team to work from a different set of priorities. Team members are not allowed to follow the direction
+ direct the development team to work from a different set of priorities. Team members are not allowed to follow the direction
of anyone whose direction does not coincide with the direction provided by the Product Owner. The Product Owner’s
decisions are visible in the content and prioritization of the Product Backlog. This visibility requires that the
Product Owner do their best. Visibility makes the role of Product Owner both a demanding and a rewarding experience.
</p>
<p>
- The Product Owner is responsible for the first of the three Scrum ceremonies, Sprint/Iteration Planning. The Development Team evaluates
+ The Product Owner is responsible for the first of the three Scrum ceremonies, Sprint/Iteration Planning. The development team evaluates
the prioritized Product Backlog, identifies the top priority items, and commits to completing the selected items during
a Sprint/Iteration. These items become the basis for the Sprint/Iteration Backlog.
</p>
<p>
- In return for the Development Team's commitment to completing the selected tasks, the Product Owner commits that they will
+ In return for the development team's commitment to completing the selected tasks, the Product Owner commits that they will
not introduce new requirements to the team during the Sprint/Iteration. Requirements are allowed to change but only outside the
Sprint/Iteration. After the team begins a Sprint/Iteration, it remains focused on the goals of that Sprint/Iteration. The only exception to this
rule is that a similar amount of work can be removed from a Sprint/Iteration to accommodate a new requirement.
@@ -137,7 +137,7 @@
those people who must assess the business value of a particular system.
</p>
<p>
- This is an often overlooked aspect of Development Team implementation. The team should consider that the customers of a
+ This is an often overlooked aspect of development team implementation. The team should consider that the customers of a
particular Release usually are not technical themselves, but do require a detailed enough understanding of how their
product operates and how it meets stated business goals and needs.
</p></refinedDescription>
@@ -190,7 +190,7 @@
application is necessary to promote usability and to achieve the desired business value. If a Course Developer is
available, they can assume most of the burden of creating the training materials, lab exercises, and workshops&nbsp;for
delivery of&nbsp;those courses to either End Users or support personnel. If a Course Developer is not
- available,&nbsp;Development Team Members should take the time to properly develop a suite of training materials for the
+ available,&nbsp;Development team members should take the time to properly develop a suite of training materials for the
feature set developed during a Release.
</p>
<p>
@@ -203,7 +203,7 @@
<refinedDescription>Many organizations engage Trainers to deliver product training to various audiences. Unlike a software Developer, most
Trainers have extensive experience in delivering training materials in a fashion that is well suited to communicating
complex concepts to End Users. They bring a necessary creativity and talent that complements the implementation and testing
-skills of a Development Team.</refinedDescription>
+skills of a development team.</refinedDescription>
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-81zxeCXkSnPW-ndmULZWlQ" name="training_materials,_ofSHoplWEeGlkdGl1HQlDA" guid="-81zxeCXkSnPW-ndmULZWlQ">
<refinedDescription><p>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/prepare_for_release/content.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/prepare_for_release/content.xmi
index 24af339..5208fcc 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/prepare_for_release/content.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/prepare_for_release/content.xmi
@@ -49,22 +49,22 @@
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-7ZImjs9oa1GUIfRAA-aZ7A" name="01_04_create_update_backout_plan,_qWKsovd3EeCFmpfCmMPILg" guid="-7ZImjs9oa1GUIfRAA-aZ7A">
<refinedDescription>A rollback might be needed for a variety of reasons, including corruption of the production code base, inoperable
components, an unplanned undesirable effect of the release on other production systems, an unhappy Customer, etc.
-The&nbsp;Development Team should provide the production support organization with a specific plan and decision criteria
+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.</refinedDescription>
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-LyV_ZO1Np5hR4jCzxdP8lg" name="01_05_develop_release_communications,_qWKso_d3EeCFmpfCmMPILg" guid="-LyV_ZO1Np5hR4jCzxdP8lg">
<refinedDescription><p>
- When a release is pushed to production, all the Stakeholders of that product should be notified that the event has
- happened and what the release means to each of the Stakeholders. Often, the output of this task does not need to be
+ When a release is pushed to production, all the stakeholders of that product should be notified that the event has
+ happened and what the release means to each of the stakeholders. Often, the output of this task does not need to be
created from scratch; for products that plan multiple releases, just updating the communique details for each release
- might be enough. However, if any of the Stakeholder groups change, or there is a significant difference in the product
+ might be enough. However, if any of the stakeholder groups change, or there is a significant difference in the product
distribution, more significant content might need to be developed.
</p>
<p>
- In any case, communicating effectively to the End User community is important. A Development Team can develop high quality
- software, but if messaging to the Stakeholders is conducted poorly or not at all, the End User experience might be
+ In any case, communicating effectively to the End User community is important. A development team can develop high quality
+ software, but if messaging to the stakeholders is conducted poorly or not at all, the End User experience might be
degraded. By simply answering the questions "who, what, when, where, why, and how" in a format appropriate for each
- Stakeholder group, a product release can become a more satisfying experience for all those involved.
+ stakeholder group, a product release can become a more satisfying experience for all those involved.
</p></refinedDescription>
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-7MHd2XgrDNoZemDYzKTd4Q" name="deployment_engineer,_qWLTsPd3EeCFmpfCmMPILg" guid="-7MHd2XgrDNoZemDYzKTd4Q">
@@ -86,7 +86,7 @@
particular release.
</p>
<p>
- While&nbsp;a draft version of the&nbsp;Deployment Plan is typically developed by a Development Team, the Deployment
+ While&nbsp;a draft version of the&nbsp;Deployment Plan is typically developed by a development team, the Deployment
Engineer is responsible for its contents and existence.&nbsp;A Deployment Plan&nbsp;normally consists of the following
sections:
</p>
@@ -101,13 +101,13 @@
The risks or issues associated with the release based on a risk assessment
</li>
<li>
- The customer organization, Stakeholders, and End User community that will be impacted by the release
+ The customer organization, stakeholders, and End User community that will be impacted by the release
</li>
<li>
The person or persons who have the authority to approve the release as "ready for production"
</li>
<li>
- The Development Team members responsible for delivering the release package to the Deployment Manager, along with
+ The development team members responsible for delivering the release package to the Deployment Manager, along with
contact information
</li>
<li>
@@ -204,7 +204,7 @@
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-IhfK-TBRtHklzkKVrccUvw" name="backout_plan,_qWLTuvd3EeCFmpfCmMPILg" guid="-IhfK-TBRtHklzkKVrccUvw">
<refinedDescription><p>
- While someone on the Development Team normally authors a draft version of the Backout Plan, the Deployment Engineer is
+ While someone on the development team normally authors a draft version of the Backout Plan, the Deployment Engineer is
ultimately responsible for its contents and existence. A Backout Plan typically answers the following questions:
</p>
<ul>
@@ -240,7 +240,7 @@
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-grT7fq-8SP3IEHJFjdrz-A" name="release_communications,_qWLTvPd3EeCFmpfCmMPILg" guid="-grT7fq-8SP3IEHJFjdrz-A">
<refinedDescription><p>
- Sometimes, depending on the product user base, separate communiques might need to be prepared for each Stakeholder
+ Sometimes, depending on the product user base, separate communiques might need to be prepared for each stakeholder
group. In that case, this artifact should specify the different groups to which communications are directed, the method
of communication (e.g., email, text or pager message, bulletin, newsletter, phone message, etc.). All communiques
should be prepared in advance so that it is a matter of disseminating information when the release to production has
@@ -264,13 +264,13 @@
What specifically (features, functions, components) has been placed into production?
</li>
<li>
- Why is this release valuable to Stakeholders and what business purpose does it serve?
+ Why is this release valuable to stakeholders and what business purpose does it serve?
</li>
<li>
Where is the product available (on which platforms, geographical locations, business units, etc.)?
</li>
<li>
- How can the Stakeholders access the system and under what circumstances?
+ How can the stakeholders access the system and under what circumstances?
</li>
<li>
When was the product released (or when will it be released if the release date is in the future)?
@@ -307,7 +307,7 @@
of hardening which results in a scheduled release approximately every 90 days. Releases for individual Development
Teams usually occur more often than those for programs, but there are no hard and fast rules regarding how often
releases should be scheduled. The only requirement is that working software should be delivered "frequently" by both
- Development Teams and programs. Although the example timeframe described above is arbitrary, empirical evidence
+ development teams and programs. Although the example timeframe described above is arbitrary, empirical evidence
suggests it is about right for most companies and fits nicely into quarterly planning cycles.
</p>
<p>
@@ -320,7 +320,7 @@
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-TIDq6m5AxfWlAJfJCiHN7g" name="01_01_review_conform_to_release_controls,_1TCC0Pd3EeCFmpfCmMPILg" guid="-TIDq6m5AxfWlAJfJCiHN7g">
<refinedDescription><p>
Release controls describe the minimum number of requirements that a software package must adhere to before being
- released into production. This is especially important if a Development Team is new or emerging, because they might not be
+ released into production. This is especially important if a development team is new or emerging, because they might not be
aware of the great responsibilities a Deployment Manager has. In fact, a Deployment Manager is responsible to senior
management for ensuring that nothing is placed into production that does not conform to the rigid controls designed to
protect the IT organization's ability to successfully deliver IT services to internal and external Customers.
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/provide_product_training/content.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/provide_product_training/content.xmi
index 0a9fc76..2799487 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/provide_product_training/content.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/provide_product_training/content.xmi
@@ -2,7 +2,7 @@
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1">
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-S5JIDccPmUswHn8Fuoihmg" name="02_02_deliver_end_user_training,_iEP5wfd3EeCFmpfCmMPILg" guid="-S5JIDccPmUswHn8Fuoihmg">
<refinedDescription><p>
- Often, a Trainer will deliver training to End Users; rarely will the Development Team deliver training because
+ Often, a Trainer will deliver training to End Users; rarely will the development team deliver training because
they are busy developing additional features for this or other systems. If a Trainer is not available, the
Product Owner might have to train the End Users.
</p>
@@ -27,7 +27,7 @@
<refinedDescription>Many organizations engage Trainers to deliver product training to various audiences. Unlike a software Developer, most
Trainers have extensive experience in delivering training materials in a fashion that is well suited to communicating
complex concepts to End Users. They bring a necessary creativity and talent that complements the implementation and testing
-skills of a Development Team.</refinedDescription>
+skills of a development team.</refinedDescription>
</org.eclipse.epf.uma:DescriptorDescription>
<org.eclipse.epf.uma:DescriptorDescription xmi:id="-EeEevuLnY3VYk0iyk-4PNA" name="product_documentation,_iEQg1Pd3EeCFmpfCmMPILg" guid="-EeEevuLnY3VYk0iyk-4PNA">
<refinedDescription><p>
@@ -35,7 +35,7 @@
those people who must assess the business value of a particular system.
</p>
<p>
- This is an often overlooked aspect of Development Team implementation. The team should consider that the customers of a
+ This is an often overlooked aspect of development team implementation. The team should consider that the customers of a
particular Release usually are not technical themselves, but do require a detailed enough understanding of how their
product operates and how it meets stated business goals and needs.
</p></refinedDescription>
diff --git a/epf_prac_151/process.openup.base/capabilitypatterns/test_solution/content.xmi b/epf_prac_151/process.openup.base/capabilitypatterns/test_solution/content.xmi
index a5fe790..0df4026 100644
--- a/epf_prac_151/process.openup.base/capabilitypatterns/test_solution/content.xmi
+++ b/epf_prac_151/process.openup.base/capabilitypatterns/test_solution/content.xmi
@@ -15,7 +15,7 @@
items list, so that they can be prioritized as part of the work that you will do during iterations.
</p>
<p>
- Stakeholders and end-users also may also be involved in performing tests to accept the release.
+ stakeholders and end-users also may also be involved in performing tests to accept the release.
</p></mainDescription>
<purpose>Develop and run test scripts to validate that the system satisfies the requirements.</purpose>
<howtoStaff><p>
diff --git a/epf_prac_151/publish.openup.base/guidances/concepts/core_principle_balance.xmi b/epf_prac_151/publish.openup.base/guidances/concepts/core_principle_balance.xmi
index ce9a11e..b94b559 100644
--- a/epf_prac_151/publish.openup.base/guidances/concepts/core_principle_balance.xmi
+++ b/epf_prac_151/publish.openup.base/guidances/concepts/core_principle_balance.xmi
@@ -30,7 +30,7 @@
<p>
Discovering the balance point is challenging, elusive, and ongoing, because the balance point is dynamic. As the system
evolves, stakeholder needs change, new opportunities appear, risks are resolved, new risks appear, and the development
- team discovers new realities about the system. Change happens throughout the development cycle. Stakeholders and team
+ team discovers new realities about the system. Change happens throughout the development cycle. stakeholders and team
members must be prepared to re-evaluate commitments, reset expectations, and adjust plans accordingly as the system
evolves.
</p>
@@ -141,7 +141,7 @@
<p>
Manage change while maintaining agreements with the stakeholders. Modern processes always manage change,
continually adapting to changes in the environment and stakeholder needs, assessing the impact of changes, making
- trade-offs, and re-prioritizing work. Stakeholder and developer expectations must be realistic and aligned
+ trade-offs, and re-prioritizing work. stakeholder and developer expectations must be realistic and aligned
throughout the development lifecycle.
</p>
</blockquote>
diff --git a/epf_prac_151/publish.openup.base/guidances/roadmaps/openup_roadmap.xmi b/epf_prac_151/publish.openup.base/guidances/roadmaps/openup_roadmap.xmi
index f516ded..916ba27 100644
--- a/epf_prac_151/publish.openup.base/guidances/roadmaps/openup_roadmap.xmi
+++ b/epf_prac_151/publish.openup.base/guidances/roadmaps/openup_roadmap.xmi
@@ -27,7 +27,7 @@
</p>
<p>
Use cases are used to elicit and describe requirements; therefore, team members need to develop skills in writing good
- use cases. Stakeholders are responsible for reviewing and certifying that the requirements are correct. Use cases are
+ use cases. stakeholders are responsible for reviewing and certifying that the requirements are correct. Use cases are
developed collaboratively.
</p>
<p>
diff --git a/epf_prac_151/publish.openup.base/guidances/supportingmaterials/who_should_use_openup.xmi b/epf_prac_151/publish.openup.base/guidances/supportingmaterials/who_should_use_openup.xmi
index 9d833ea..9667c89 100644
--- a/epf_prac_151/publish.openup.base/guidances/supportingmaterials/who_should_use_openup.xmi
+++ b/epf_prac_151/publish.openup.base/guidances/supportingmaterials/who_should_use_openup.xmi
@@ -9,7 +9,7 @@
project team
</li>
<li>
- Stakeholders
+ stakeholders
</li>
<li>
Software process engineers
@@ -24,7 +24,7 @@
roles collaborate.
</p>
<p>
- Stakeholders will find guidance on what they may expect from the software development team, and how the software will
+ stakeholders will find guidance on what they may expect from the software development team, and how the software will
be created. OpenUP also describes the stakeholders' responsibilities, and states how they can best work with the
development team to obtain software that meets their needs.
</p>
