| <?xml version="1.0" encoding="UTF-8"?> |
| <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,
 |
| 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
 |
| 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.
 |
| </p>
 |
| <p>
 |
| 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> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-h5qFmsSg2p-6LPnB_IUogA" name="01_02_create_update_user_documenation,_VpC9UPd3EeCFmpfCmMPILg" guid="-h5qFmsSg2p-6LPnB_IUogA"> |
| <refinedDescription><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
 |
| is used as the basis for training materials - if the documentation is of poor quality, the training materials might not
 |
| 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
 |
| expectations because they will not be able operate the application effectively.
 |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-gdsRvq0kijdAY9bJ0FONYg" name="01_03_create_update_support_documenation,_VpC9Ufd3EeCFmpfCmMPILg" guid="-gdsRvq0kijdAY9bJ0FONYg"> |
| <refinedDescription><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
 |
| 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 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></refinedDescription> |
| </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
 |
| is produced by the team during a Sprint/Iteration in support of delivered features.
 |
| </p>
 |
| <p>
 |
| Because they often are skilled at creating and maintaining technical documentation, Technical Writers help to ensure
 |
| consistency and conformance to corporate standards.
 |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-A9zavwG_ylHmUBtjwrhbpQ" name="product_owner,_VpIc5Pd3EeCFmpfCmMPILg" guid="-A9zavwG_ylHmUBtjwrhbpQ"> |
| <keyConsiderations>The Product Owner's commitment is essential to ensure the project success. By defining the product vision, they provide
 |
| direction to the team. By externally promoting each Sprint/Iteration result, the Product Owner brings recognition and motivation
 |
| 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,
 |
| 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>
 |
| <ul>
 |
| <li>
 |
| <strong>Functionality:</strong> Identifies each product requirement as a Product Backlog Item and supplies
 |
| details for those requirements when they are needed by the team, including specifying the acceptance tests for
 |
| each requirement
 |
| </li>
 |
| <li>
 |
| <strong>Priority:</strong> Defines the order in which those backlog items will be developed, according to the value
 |
| that they bring to Customers and users, which provides the team with a Product Backlog ready for Sprint/Iteration
 |
| planning
 |
| </li>
 |
| <li>
 |
| <strong>Goal:</strong> Defines the release goals and makes decisions concerning release planning
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| The Product Owner has the following responsibilities:
 |
| </p>
 |
| <ul class="noindent">
 |
| <li>
 |
| Define the features of the product
 |
| </li>
 |
| <li>
 |
| Decide on release date and content
 |
| </li>
 |
| <li>
 |
| Responsible for the profitability of the product (ROI)
 |
| </li>
 |
| <li>
 |
| Prioritize features according to market value
 |
| </li>
 |
| <li>
 |
| Adjust features and priorities as needed
 |
| </li>
 |
| <li>
 |
| Accept or reject work results
 |
| </li>
 |
| </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.
 |
| </p>
 |
| <p>
 |
| The Product Owner is one person, not a committee. Committees may exist that advise or influence this person but team
 |
| members who want to change an item's priority must first convince the Product Owner. In this way, organizational
 |
| methods for setting priorities and requirements are influenced over time by this role.
 |
| </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
 |
| 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 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
 |
| 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.
 |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-_kmWRdAS15z9HHQOi2bRUw" name="product_documentation,_VpJD8Pd3EeCFmpfCmMPILg" guid="-_kmWRdAS15z9HHQOi2bRUw"> |
| <refinedDescription><p>
 |
| 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
 |
| product operates and how it meets stated business goals and needs.
 |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-pyRevWV0HtFS5y1wBPcCjw" name="user_documentation,_VpJD8vd3EeCFmpfCmMPILg" guid="-pyRevWV0HtFS5y1wBPcCjw"> |
| <refinedDescription><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, work instructions, operational procedures, etc.
 |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-48XjWeRRpF2qfA3kioGYSA" name="support_documentation,_VpJD9Pd3EeCFmpfCmMPILg" guid="-48XjWeRRpF2qfA3kioGYSA"> |
| <refinedDescription><p>
 |
| Support documentation usually is developed for the three common tiers of a support organization. Tier 1 typically is
 |
| the Help Desk where users call when they have a problem with a particular system. Tier 1 support personnel
 |
| normally answer basic questions and, if necessary, log a ticket and escalate it to the appropriate Level 2 support
 |
| desk.
 |
| </p>
 |
| <p>
 |
| Tier 2 support personnel may deal with more complex questions or issues regarding an application and might need to
 |
| do some research on the characteristics of the system to provide an answer. If that person cannot resolve the
 |
| issue, the ticket is escalated to Tier 3 support personnel who have a deeper understanding of the application's
 |
| code and the technology support the system's architecture.
 |
| </p>
 |
| <p>
 |
| To properly convey the necessary information to each support tier, the application's code base should be well commented
 |
| and logically organized. This approach will facilitate the development of the support documentation.
 |
| </p>
 |
| <p>
 |
| Support documentation typically includes:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| User manuals with work instructions, process descriptions, and procedures
 |
| </li>
 |
| <li>
 |
| Communications, training, and knowledge transfer deliverables
 |
| </li>
 |
| <li>
 |
| Support and operations manuals
 |
| </li>
 |
| <li>
 |
| Service information, including Help Desk scripts
 |
| </li>
 |
| </ul></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:ProcessDescription xmi:id="-yeqVyv9laglLKJHLoavEgA" name="prepare_product_documentation,_NTPI8fd3EeCFmpfCmMPILg" guid="-yeqVyv9laglLKJHLoavEgA"/> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-LQefSmUJtkoZkQhMtmQpfg" name="develop_training_materials,_ofI9sJlWEeGlkdGl1HQlDA" guid="-LQefSmUJtkoZkQhMtmQpfg"> |
| <refinedDescription><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
 |
| 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.
 |
| </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.
 |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-TEGuv2rdghGx-gULZxUyJQ" name="course_developer,_ofSHoJlWEeGlkdGl1HQlDA" guid="-TEGuv2rdghGx-gULZxUyJQ"> |
| <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> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-81zxeCXkSnPW-ndmULZWlQ" name="training_materials,_ofSHoplWEeGlkdGl1HQlDA" guid="-81zxeCXkSnPW-ndmULZWlQ"> |
| <refinedDescription><p>
 |
| Training materials that can be used to train end users and production support personnel might consist of:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Presentation slides
 |
| </li>
 |
| <li>
 |
| Handouts
 |
| </li>
 |
| <li>
 |
| Job aids
 |
| </li>
 |
| <li>
 |
| Tutorials
 |
| </li>
 |
| <li>
 |
| On-line demos
 |
| </li>
 |
| <li>
 |
| Video vignettes
 |
| </li>
 |
| <li>
 |
| Lab exercises
 |
| </li>
 |
| <li>
 |
| Quizzes
 |
| </li>
 |
| <li>
 |
| Workshop materials, etc.
 |
| </li>
 |
| </ul></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| </xmi:XMI> |
