CA Product Vision. Getting Started Guide

Transcription

1 CA Product Vision Getting Started Guide Spring 2012

2 This documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice. The manufacturer of this Documentation is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2012 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

3 Contact CA Technologies Contact CA Support For your convenience, CA Technologies provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA Technologies products. At you can access the following: Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads CA Support policies and guidelines Other helpful resources appropriate for your product Providing Feedback About Product Documentation If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com. If you would like to provide feedback about CA Technologies product documentation, complete our short customer survey, which is available on the CA Support website at

4

5 Contents Chapter 1: Introduction 7 About Product Vision... 7 Product Vision and CA Clarity PPM... 7 Log In to Product Vision... 8 Add a User in Salesforce.com... 8 Chapter 2: Best Practice for Getting Started 11 How to Enter Requirement Data Chapter 3: Quick Tour 13 Product Vision Menu Administration Menu Page Features Navigation Links Auto Suggest for Lookups Page Filters Create a List Page Filter Edit Filters Search for an Object List Pages Sort a List Page by Column List Page View and Edit Edit List Page Fields Configure Columns for a List Page Detail Pages Editing Rules Chapter 4: Sources and Personas 23 Sources Create a Source Edit Source Details View Source Details Personas Create a Persona Edit Persona Details Contents 5

6 View Persona Details Chapter 5: Product Setup 27 Products Create a Product Create a Product Release Edit Product Details View Product Details Releases Edit Product Release Details View Product Release Details Requirements Create a Requirement Edit Requirement Details View Requirement Details View and Manage Requirements Lists Track Requirements with Charts and Reports Features Create a Feature Edit Feature Details View Feature Details The Product Roadmap Roadmap Navigation View Details for Items in the Roadmap Chapter 6: Chatter 43 Turn Following On or Off How to View Different Types of Chatter Information View Chatter for all Items that You Follow View Chatter Activity for an Item Appendix A: Glossary 47 6 Getting Started Guide

7 Chapter 1: Introduction This section contains the following topics: About Product Vision (see page 7) Product Vision and CA Clarity PPM (see page 7) Log In to Product Vision (see page 8) Add a User in Salesforce.com (see page 8) About Product Vision Product Vision lets you manage requirements for projects, services, products, releases, and features. Using Product Vision you can trace a requirement from its original requester to its inclusion in a particular feature or release for a product. You can include detailed information about the requirement and its benefits, the source of the requirement, competing products, and ranking information. Associating these types of information with requirements can help you decide whether to include a requirement in a product release. You can also associate requirements with Agile Vision user stories, from scrum methodology, to track the history of a user story for any given sprint. You can see the requirement that is associated with the user story and the source that requested the requirement. Product Vision and CA Clarity PPM When Product Vision is integrated with CA Clarity PPM, the following tasks can be accomplished: Role hierarchies can be downloaded from CA Clarity PPM to Product Vision. A Product Vision requirement can be linked with a CA Clarity PPM task from CA Clarity PPM. An administrator, with appropriate privileges in Product Vision and CA Clarity PPM, performs these tasks. When integration is completed, and requirements and tasks are linked, users can see cost and effort information from CA Clarity PPM. The following information is available: Planned Cost Actual Cost Chapter 1: Introduction 7

8 Log In to Product Vision Planned vs Actual Cost Planned Effort Actual effort Effort Remaining Planned vs Actual Effort Note: For more information about using Product Vision with CA Clarity PPM, see the Integration Guide. Log In to Product Vision All new CA Product Vision users are given a user name and a temporary login password. As a convenience, you can set the check box to have CA Product Vision automatically populate the User Name field with your login user name. The user name and password are sent by , usually from salesforce.com. 1. Go to the following Internet URL: 2. Enter your user name and password and click Login. When you first log into CA Product Vision, you are instructed to change your password immediately. Add a User in Salesforce.com The user profiles that are available for users are part of the Salesforce license. Note: For more information about user profiles, see the Access Rights appendix in the Administration Guide. Only a system administrator can add a user in Salesforce.com. 1. Click Setup on the menu bar. 2. In the left pane, click Manage Users in the Administration Setup menu. 8 Getting Started Guide

9 Add a User in Salesforce.com 3. In the right pane, click the option to add or edit users. The user list page appears displaying the administrator users. 4. Optionally, select All Users in the View field to see all users. 5. Click Help for this Page for information about setting up a user in Salesforce.com. This link opens the Salesforce.com help. Chapter 1: Introduction 9

10

11 Chapter 2: Best Practice for Getting Started This section describes best practices for starting to use Product Vision. How to Enter Requirement Data If you are new to CA Product Vision, the following process explains the best way to get started entering your requirement data. 1. Create the sources and personas you intend to use first. Sources and personas provide knowledge about where product requirements come from and who is waiting for the fulfillment of a requirement. Having this basic information already in CA Product Vision lets you associate it with components like products and releases as they are created, providing traceability and context. You can create a source or persona with a requirement or product at any point, but having the information created and available for selection when other components are created saves extra clicks and rework. 2. Create products. One of the primary intents of CA Product Vision is to manage product requirements. You can create the products for which you want to track requirements and provide information on cost, owners, personas, customers, market segments, competing products, strengths, weaknesses, and opportunities. Setting up a product in CA Product Vision provides a history that shows the reasoning that influences the requirements chosen to be completed. 3. Create releases. A release can be associated with only one product. It is a way to organize requirements associated with a product into an effort that has a definite delivery time period. A release usually includes the fulfillment of a number of requirements or features. 4. Create features. A feature can be standalone and cover one or more releases of a product. 5. Create requirements and associate them with the necessary products, releases, or features. Chapter 2: Best Practice for Getting Started 11

12

13 Chapter 3: Quick Tour This section contains the following topics: Product Vision Menu (see page 13) Administration Menu (see page 13) Page Features (see page 14) Page Filters (see page 15) Search for an Object (see page 17) List Pages (see page 17) Detail Pages (see page 21) Editing Rules (see page 21) Product Vision Menu Use the Product Vision menu to access the pages that let you manage all aspects of requirements for products. The following menu sections appear on the Product Vision menu: Overview Use the selections in the Overview menu to view communications from other users with Chatter, and to view ideas from Idea Vision in the Inbox. Business Planning Use the selections in the Business Planning menu to set up Sources and Personas to track the origin of a requirement to its original requester. You can also access the Product Roadmap from this section. No security is available around the contents of this menu section. All Product Vision users can view and edit the contents found here. Detailed Planning Use the selections in the Detailed Planning menu section to set up products, releases, features, and requirements. Role-based security controls the access to the items found under this menu section. Administration Menu The Administration menu groups the product administration pages into the following menu sections: Organization Use the selections in the Organization menu section to set up users and roles. Chapter 3: Quick Tour 13

14 Page Features Application Use the selections in the Application menu section to set up master releases, products, and releases. You can use the links for products and releases on the Administration menu or the Detailed Planning menu section on the Product Vision menu. Configuration Use the selections in the Configuration menu to manage the following: Property Views List view publishing Custom attributes Global Configuration Status mapping Page Features The Agile Vision and Product Vision pages have a number of convenient features to help you set up and manage your products more easily. Navigation Links Users can navigate to most pages from almost every Product Vision page. On list pages showing the All Records view, the actions Edit or View appear in an Action column. Clicking Edit navigates to the edit page for the item from the list page that is being viewed. Clicking View navigates to the detail page. If you are the creator of a list page item, for example, a product or a requirement, you see both links. If you did not create the item, you do not have the right to edit it. Only the View action is visible in the Actions column. In the Hierarchy view on a list page, the names of items appear as underlined text. Clicking one of these links navigates to the respective detail page. On pages that are not main menu pages, a Back to List button on the header navigates to the previous page. 14 Getting Started Guide

15 Page Filters You can navigate to the home page, or can specify a custom home page from any page. The Home icon is next to the Search field. Hover over the icon to view options to: Go to the home page Set the current page as the home page Reset the home page to the default home page. Auto Suggest for Lookups Auto suggest displays a list of values that matches the characters entered in the text field of a lookup attribute. For example, if you type Bo in a lookup text field, the system displays a list of suggested values containing the string Bo. Select the appropriate value from the list. Adding additional letters to the string further narrows the suggestions. Page Filters List pages have a filter below the header that lets you control what you view on the page. All filters that are created for a list page appear in the Filters drop-down list for selection. The current filter in use on the list page shows in the Filters field. Note the following points about filters: When you filter, the selection criteria remain in effect for the list page. If you leave the list page and return, the list is prefiltered with the selection criteria from the filter. Any filter that you create is automatically saved. You can edit and remove filters that you have created. To override the filter criteria for the list page and show the entire list, click Clear Filter. Filters are saved across sessions per browser. If you switch to a different browser, reselect a filter to apply it. Chapter 3: Quick Tour 15

16 Page Filters Create a List Page Filter You can create and save multiple filters. 1. Open the list page that you want to filter. 2. Click Add/Edit Filter. The filter window appears. 3. Select the Create a New Filter option. 4. In the Properties section, enter the name in the Filter Name field. 5. Make selections in the drop-down lists following the Filter Name field to select and refine filter criteria. The first drop-down list lets you select a field. The second lets you enter an operand such as greater than or less than. The third lets you select a value to complete the criteria. The operands and values for the field selections vary according to the field selected in the first drop-down list. 6. Click Add to define additional criteria. 7. Click Filter when you are done. The list page is filtered using the criteria that you defined, and the filter is saved automatically. Edit Filters You can edit a filter name and can change the criteria. You can also delete a filter. 1. Open the list page for the filter you want to edit and click Add/Edit Filter. The Filtering window appears with the Show Existing Filters options selected. 2. In the left pane, select the filter. The properties display in the right pane. 3. Edit the filter and click Filter. The changes are saved and the list page is filtered with the new criteria. 16 Getting Started Guide

17 A Search for an Object Search for an Object Based on your product membership, you can search on objects (for example, user stories, issues, tasks, releases) for the product. A system administrator can search on objects across all products. Note: There can be a slight delay when indexing newly created items for searching. Search can take up to several minutes before a new item displays in the search results. 1. At the top-right of your workspace, enter a keyword or a number (ID) in the text field. For example, enter a title, description, or ID of an object. Note: Enter the search string, without using wildcard characters before the string. The following examples show correct and incorrect search strings: Correct: as a user, I Incorrect: *as a user, I * Click the magnifying glass icon. The search results appear, grouped alphabetically by the type of item. List Pages The following sections explain how to work with a list page and manage the information it contains: List Display and Pagination Sort List Page Information (see page 18) List Page View and Edit (see page 18) Edit List Page Fields (see page 20) Configure Columns for a List Page (see page 21) Chapter 3: Quick Tour 17

18 List Pages Sort a List Page by Column On some pages where data is displayed in list table format, you can sort the list on any of the columns. 1. Move the cursor over a list column heading. 2. Click the list column heading menu button, and do one of the following: Select Sort Ascending or Sort Descending to order the list items alphabetically in the order you want. Click Group By This Field to group like items in the column together in the list. Note: If you sort or group by a column field with multiple values, the sort function sorts for each of the values in the column field. For example, when sorting a product column field that contains multiple products for a requirement, the sort function groups by each product. To remove a list page sort and return to the original listing, click Clear Grouping. List Page View and Edit To display a list page, go to the Product Vision menu and select the appropriate menu item. If the Actions column on the list page contains links for View and Edit for a list item, you can change the list item. You can use the links to do the following: Edit. You can open the details page for the item and change the values in any of the fields that are active. 18 Getting Started Guide

19 List Pages View. You can open the detail page in view-only mode. If you are the creator of the list item, or the product owner, you can click Edit to change the field values. If the Actions column contains only a View link, you cannot change the details because you do not have the appropriate rights. Some actions can be completed in View mode even if you are not the owner of the list item. The following table indicates what you can do from View mode. View mode action Product owner or creator can perform? User who is not a product owner or creator can perform? Add or delete requirements for products, releases, and features. Open and edit requirements for products, releases and features. Create a version or submit a requirement draft for approval. Yes Yes Yes Yes No No Chapter 3: Quick Tour 19

20 List Pages View mode action Product owner or creator can perform? User who is not a product owner or creator can perform? Approve a requirement draft. Product Owner only Restore a previous version of a requirement. Yes Yes Add or delete releases for a product. Yes Yes Open and edit releases listed for a product. Yes No Add, edit and delete notes for a requirement. Add and remove an attachment for a requirement. Add, edit, and delete attachments for a feature. Yes Yes No Yes No Edit List Page Fields Many fields on list pages can be edited inline, saving clicks to get to the detail page of the list item you want to change. 1. Click in a list page field to begin editing. If the field can be edited, it activates so that you can change values. When you change a field value, a small red triangle appears in the upper left of the field flagging the updated value. 2. Click Save to save the updated value. Fields that cannot be edited in-place include fields that have more than one value. If you sort or group by a column field with multiple values, the sort function sorts for each of the values in the column field. You cannot edit the value of the field in-place because there would multiple objects that are impacted by the changes. 20 Getting Started Guide

21 Detail Pages Configure Columns for a List Page You can choose the columns that display on some list pages. You can remove the default columns and add the columns that you want. If you add custom fields (also known as attributes), the custom fields are available to add to the appropriate list page as columns. For example, if you add custom fields for requirements, the custom fields will be available for the requirements list page. 1. Open the list page and click Configure. 2. Specify the columns you want included in the list and the correct order. 3. Click Save. To restore configuration defaults for a list page, click Restore Defaults. Detail Pages You open a detail page by clicking View in the Actions column of a list page. From the details page, you can do one or more of the following actions: View the properties for the list page item in a read-only state. Add associations with other Product Vision, Agile Vision, or Idea Vision items. For example, from the detail page of a requirement, you can associate user stories, child requirements, and roles. Link inbox items from Idea Vision. Add notes or attach files. Click the Edit button to edit the properties for the item you are viewing. List sections appear on the detail pages for associations. The sections can be collapsed and expanded. If you expand or collapse sections on a detail page, the pages displays the way you last viewed it when you reopen the page. Editing Rules The following list provides general guidelines for working in Product Vision: You can edit or delete any item that you create. Chapter 3: Quick Tour 21

22 Editing Rules A product owner has the right to edit any requirement, release, feature, source, or persona associated with the product. For example, as a product owner, you can edit the requirement associated with your product. You do not need to be the creator or an assigned owner of the requirement. A product owner can remove the right of the creator to edit a requirement, release, feature, source, or persona associated with a product. A feature can have other owners other than a product owner or creator. These additional owners also have the right to edit any requirements associated with the feature. 22 Getting Started Guide

23 Chapter 4: Sources and Personas Sources provide a convenient ways to trace the source of a requirement and personas provide a way to describe the likely user of a product. This section contains the following topics: Sources (see page 23) Personas (see page 25) Sources You can define a profile for a source of a requirement. Sources let you trace requirements back to their origins. Knowing how many sources requested a requirement and who the sources are can help you determine how quickly the requirement must be delivered. It is a factor in determining which requirements get done for a release of a product. Sources can provide information about which geographic or market segments are involved. Product Vision provides the following source types: Business unit. Identifies a requirement from internal parts of your business. Customer. Identifies a requirement from active or prospective customers. Geography. Identifies a requirement specific to one or more geographies. Industry. Identifies a requirement specific to one or more industries. You can define additional custom fields (attributes) for a source if you find that the default fields provided are not adequate for the information you want to collect and store for sources. Additional custom fields are added from the Administration menu. See the Administration Guide for more information. Create a Source Create a source to describe the originator of a requirement or an organization that is interested in having a requirement fulfilled. 1. Go to the Product Vision menu, and click Source from the Business Planning menu. The source list page appears. Chapter 4: Sources and Personas 23

24 Sources 2. Click New Source. 3. Complete the following fields: Type Specifies the source type. After you select a type and save, the type cannot be changed. Values: Business Unit, Customer, Geography, Industry. 4. Click Save and Close. After you create a source, you can edit the source to add complete information. Edit Source Details Edit the source details for a requirement specify detailed information about the source. 1. Open the sources list page and click Edit in the Actions column next to the source name. 2. Complete or edit the appropriate fields and click Save. The following fields require explanation: Type Specifies the source type. After you select a type and save, the type cannot be changed. Values: Business Unit, Customer, Geography, Industry. View Source Details The Source Details page contains information about a source that you can view. To display the page, click View in the Actions column of the source on the sources list page. In View mode, you can: Add a new requirement for the source Link an idea with a source If you are the source owner, you can click Edit on the Source Details page and change the source. 24 Getting Started Guide

25 Personas Personas A persona can be a real person or a composite of a person who represents a buyer or someone who influences the decision to buy a product. Associating a persona with a requirement can provide detailed information about who is expecting a requirement to be completed and how the requirement fits into the business model for the person. A persona can provide information about the issues that the requirement will satisfy including business needs, pain points, and buying habits. Create a Persona Create a persona to indicate a person in an organization or a representative composite of a person who might influence a decision to buy your product. Once you create the persona, you can add full information by editing persona details. 1. Go to the Product Vision menu, and click Persona from the Business Planning menu. The persona list page appears. 2. Click New Persona. 3. Complete the appropriate fields. 4. Click Save and Close. After you have created the persona, you can add more detail by editing the persona details. Edit Persona Details 1. Open the personas list page and click Edit in the Actions column next to the persona name. 2. Complete or edit the appropriate fields. The following fields require explanation: Influenced By Specifies other personas that influence a persona. 3. Complete the persona by filling in detailed information in the free-form text sections. Each text section contains a text formatting bar so that you can manipulate text. 4. Click Save. Chapter 4: Sources and Personas 25

26 Personas View Persona Details The Persona Detail page contains in depth view-only information about a persona. To open the page in view mode, click View next to the persona on the personas list page. 26 Getting Started Guide

27 Chapter 5: Product Setup This section contains the following topics: Products (see page 27) Releases (see page 31) Requirements (see page 33) Features (see page 39) The Product Roadmap (see page 41) Products When you create a product, you create a detailed picture of the product for future reference. You can include information about finances, customers, competing products, geographic market segment, industry market segment, and features. You can also include more in-depth information about the product's strengths, weaknesses, opportunities, threats, and the problems addressed. Create a Product After you create the product, edit the product details to add complete information about all aspects of the product. 1. Go to the Product Vision menu, and click Products from the Detailed Planning menu. The products list page appears. 2. Click New Product. 3. Complete the requested fields. The following fields require explanation: Product Owner Specifies the name of the owner or owners of the product. 4. Complete one of the following actions: Click Save to save the Product and edit the product details. Click Save and New to save the Product and create a new product. Chapter 5: Product Setup 27

28 Products Create a Product Release You can create a release for a product if you are the product owner or the system administrator. 1. Go to the Product Vision menu, and click Releases from the Detailed Planning menu. The release list page appears. 2. Click New Release. 3. Complete the following fields: Target Cost Defines the total planned cost for the release. This value is a high-level estimate that can be entered and edited in Product Vision. When CA Clarity PPM and Product Vision are integrated, planned cost information comes from CA Clarity PPM and is read-only in Product Vision. This field is a way to enter and track original rough estimates directly using Product Vision. Target Effort Defines the total planned effort for the release in hours. This value is a high-level estimate that can be entered and edited in Product Vision. When CA Clarity PPM and Product Vision are integrated, planned effort information comes from CA Clarity PPM and is read-only in Product Vision. This field is a way to enter and track original rough estimates directly using Product Vision. 4. Complete one of the following actions: Click Save to save the release and edit the release details. Click Save and New to save the release and create another release. After you create the release, edit the release details to add complete information about all aspects of the release. Edit Product Details 1. Open the products list and click Edit in the Actions column of the product. 2. On the product's edit page, complete or edit the following fields as necessary: Product Name Specifies the name of the product. 28 Getting Started Guide

29 Products Product Prefix Specifies a prefix for identifying Agile Vision user stories that make up the product backlog. Product Description Active Provides a text description of the product. Specifies the product is active and can be tracked in Product Vision. Default: Selected Lifecycle Stage Specifies stage of development of a product. Values: Concept, Under Development, Introduced, Growth, Mature, Decline, End of Life. Competitor Specifies that the product is a competitor product rather than a product of your business. Planned Revenue Specifies the earnings that are expected from a product. Actual Revenue Specifies the earnings received to date on the product. Planned Cost Specifies the intended cost of a product. Actual Cost Specifies the real cost of the product to date. Planned Effort Specifies the estimated effort to deliver the requirement. Actual Effort Specifies the real effort spent to deliver the product to date. Chapter 5: Product Setup 29

30 Products 3. In the multi-value selection boxes, select the values you want associated with the product for the following: Personas Features Competing Products Geography Market Segment Industry Market Segment Customers 4. Complete the freeform text sections by filling in detailed product information about the following: Strengths Weaknesses Opportunities Threats Problem Addressed You can enter up to 32,000 characters in each text box. 5. Click Save. View Product Details The Product Detail page contains information about a product that you can view. To display the page, click View in the Actions column of the product on the products list page. If you are the product owner, you can click Edit on the Product Detail page and make changes to the product. In View mode on the Product Detail page you can: Change the product owner Create a release or requirement Create a scrum team 30 Getting Started Guide

31 Releases Releases Product Vision has the following release types: Product release This release type indicates an update or change to a product and therefore must be associated with a single product. If Agile Vision is also used, any releases created also appear in Agile Vision. Master release This release type can be associated with multiple products and their releases. When you assign a product release to a master release, all user stories and requirements within the release are automatically assigned to the master release. If you do not want to assign all user stories and requirements to the master release, you can associate individual user stories or requirements, if the product is associated with the master release. Note: For more information about master releases, including how to create a master release, see the Administration Guide. Edit Product Release Details You can edit the release details for a product. 1. Open the releases list page and click Edit in the Actions column of the release you want to edit. 2. On the release's edit page, complete or edit the requested fields as necessary. The following fields require explanation: Target Cost Defines the total planned cost for the release. This value is a high-level estimate that can be entered and edited in Product Vision. When CA Clarity PPM and Product Vision are integrated, planned cost information comes from CA Clarity PPM and is read-only in Product Vision. This field is a way to enter and track original rough estimates directly using Product Vision. Target Effort 3. Click Save. Defines the total planned effort for the release in hours. This value is a high-level estimate that can be entered and edited in Product Vision. When CA Clarity PPM and Product Vision are integrated, planned effort information comes from CA Clarity PPM and is read-only in Product Vision. This field is a way to enter and track original rough estimates directly using Product Vision. Chapter 5: Product Setup 31

32 Releases View Product Release Details The Release Detail page contains extensive information about a release. To display the page, click View in the Actions column of the release on the releases list page. If you are the release or the product owner, you can complete the following tasks in View mode. Create a requirement Create a sprint Create a baseline 32 Getting Started Guide

33 Requirements Requirements You create requirements to identify and track needed abilities for the product. Requirements that you create are listed on the Requirements list page. You can filter and sort the requirements to see only the information you want in the list. Requirements that you create are listed on the Requirements list page. You can filter and sort the requirements to see only the information you want in the list. You can enter requirements in Product Vision using one of the following methods: Click the Requirements link on the Detailed Planning menu and click New Requirement. Open a product, source, release, or feature in View mode and click New Requirement in the Requirements section. Requirements have version control and can be either a draft or an approved version with a version number. You can view requirements for a specific product, release, and feature from the detail page for that object. Requirements use version control to manage drafts and approved versions of a requirement. When you create and save a requirement, the Status field changes to Draft. The method for creating an approved version depends on whether Requirement Change Management (RCM), is enabled: If RCM is enabled, the requirement owner sends an approval request to the product owner. The product owner approves or rejects the requirement draft. If approved, the requirement state changes to Approved and the version number of the requirement increments. If RCM is not enabled, either the requirement owner or the product owner can create a new approved version. The status changes to Approved and the version number increments. Requirements that you create are listed on the Requirements list page. You can filter and sort the requirements to see only the information you want in the list. Chapter 5: Product Setup 33

34 Requirements Create a Requirement You can create a requirement draft from the Requirements page. 1. Go to the Product Vision menu, and click Requirements from the Detailed Planning menu. The Requirements list page appears. 2. Click New. 3. Complete the requested fields. The following fields require explanation: State This field is defined by your company. Typically, this field is used to label different workflow stages for a requirement. Products Specifies the product or products to which the requirement applies. You can select more than one product to associate with the requirement. 4. Click Save and Close. The details page appears and the status of the requirement is Draft. After you create a requirement, edit the requirement details to add complete information about all aspects of the requirement. You can then have the draft approved and create the approved version of the requirement. Edit Requirement Details You can edit the properties for a requirement. 1. Open the requirements list page and click Edit in the Actions column of the requirement you want to edit. 2. On the Requirement Edit page, complete or edit the appropriate fields. The following fields require explanation: Planned Cost Specifies the planned cost for the requirement. When Product Vision is integrated with CA Clarity PPM, this data comes from CA Clarity PPM and is read-only. If you are integrated with CA Clarity PPM, manual edits will be overwritten. 34 Getting Started Guide

35 Requirements Planned Effort Specifies the planned effort for the requirement in labor hours. When Product Vision is integrated with CA Clarity PPM, this data comes from CA Clarity PPM and is read-only. If you are integrated with CA Clarity PPM, manual edits will be overwritten. Actual Cost Displays the actual cost of the requirement. When Product Vision is integrated with CA Clarity PPM, this data comes from CA Clarity PPM and is read-only. If you are integrated with CA Clarity PPM, manual edits will be overwritten. Actual Effort Displays the actual effort in labor hours charged to the requirement. When Product Vision is integrated with CA Clarity PPM, this data comes from CA Clarity PPM and is read-only. If you are integrated with CA Clarity PPM, manual edits will be overwritten. Remaining Cost Displays the amount of planned cost that remains. When Product Vision is integrated with CA Clarity PPM, this data comes from CA Clarity PPM and is read-only. Remaining Effort Displays the amount of planned effort hours that are left. When Product Vision is integrated with CA Clarity PPM, this data comes from CA Clarity PPM and is read-only. Planned vs Actual Cost State Displays the difference between the planned cost and the actual cost. This field is read-only. This field is defined by your company. Typically, this field is used to label different workflow stages for a requirement. Is Active 3. Click Save. Specifies that the requirement is active and can be assigned to releases and features. Inactive requirements do not appear in the list views or hierarchy views. Default: Selected 4. Click Back to List. Chapter 5: Product Setup 35

36 Requirements View Requirement Details The Requirement Detail page contains information about a requirement such as the requirement owner, financial data, associated products, release and features, and the version history. If change management is enabled for requirements, you can see the approval history. If you are the requirement owner or the owner of an associated product or feature, you can click Edit on the page. You can also change the requirement. 1. Go to the Product Vision menu and click Requirements from the Detailed Planning menu. The requirements list page opens. 2. Click View in the Actions column of the requirement to open the requirement in View mode. In View mode, you can complete the following tasks. These tasks are described in the Product Vision online help. Create a version of the requirement (when RCM is disabled). Submit a requirement draft for approval (when RCM is enabled). Add a child requirement. Create a user story (if used with Agile Vision). Add an existing user story. To learn about user stories, see the CA Agile Vision Online Help. Create or add an existing epic. To learn about epics, see the CA Agile Vision Online Help. Add a note. Add an attachment. Approve a requirement (when RCM is enabled). Restore a previous version of the requirement, if you are a requirement owner or product owner. View and Manage Requirements Lists The Requirements list page has three list viewing options available: All Records. From this view, you can create new requirements or view and edit individual requirements. 36 Getting Started Guide

37 Requirements Requirement Hierarchy. This is the default view. Use this view to see and manage parent-child relationships between requirements and to create new requirements. Traceability Matrix. Use this view to see the user cases associated with a requirement. You can also click a link to see the detailed information about the requirement, including associated source and persona information. View the Traceability Matrix The Traceability Matrix allows you to see the origin of a requirement and any user story associated with the requirement through Agile Vision. View the Requirements Hierarchy 1. Display the requirements list page. 2. In the View field, select Traceability Matrix. 3. Click one of the following links for information: Click a requirement name to see detailed information about the requirement. The requirement includes the source or persona that originated the requirement and product and release information. Click a user story name to see details about how the requirement is being fulfilled in Agile Vision. You can filter the Traceability Matrix requirements using the filter options. Click Add/Edit Filter to create a filter, specify the criteria, and click Filter to filter the view. The requirements hierarchy lets you quickly identify which requirements have been associated as parent and child. The list shows in order by parent with the children below the parent. 1. Display the requirements list page. 2. In the View field, select Requirements Hierarchy. From this list, you can perform the following tasks: Click in a field to update values in-line. The field activates if the value can be updated. Right-click on a requirement to see a menu that allows you to view, edit, delete, expand, or collapse the requirement. Chapter 5: Product Setup 37

38 Requirements A gray arrow indicates a collapsed hierarchy with the children hidden. A black arrow indicates an expanded parent with the children listed. In the following illustration, the expanded hierarchy has four levels. You can create an unlimited number of levels in a hierarchy. Track Requirements with Charts and Reports You can track your requirements through predefined charts and reports. These charts are available on the Salesforce.com Vision Public Dashboard. 1. Log in to Product Vision and click Setup in the navigation toolbar. 2. Click the Dashboards tab. The dashboard appears. If the Product Vision dashboard is not visible, click Go to Dashboard List, under the dashboard title. The Vision Public Dashboard appears. 3. Select Product Vision Dashboard. The dashboard appears with the following charts: Requirements - State Bar Chart Requirement - Product Pie Chart Requirement - Average Age Line Chart Requirement - Release Pie Chart Requirement - Trend Line Chart Requirement - Source Pie Chart 38 Getting Started Guide

39 Features 4. Click on the chart to view options for generating a report. You can modify the criteria for the report with selections from the Summarize information by and Show lists. You can also specify time ranges. See the page help to learn more about the dashboard. Best Practice: If you plan to customize the report or chart, create a custom dashboard and report to avoid impacting other users. See the Salesforce.com page help to learn more. Features Features describe the abilities of the product. Associate a feature with a single product when the feature is created. A feature can be linked to multiple requirements. You can view the planned and actual information for the feature requirements rolled up to the feature level. Create a Feature You can create a feature to describe new functions and abilities of a product. 1. Go to the Product Vision menu, and click Features from the Detailed Planning menu. The features list page appears. 2. Click New Feature. 3. Complete the following fields: Target Cost Defines the total planned cost for the feature. This is a high-level estimate that can be entered and edited in Product Vision. When CA Clarity PPM and Product Vision are integrated, planned cost information comes from CA Clarity PPM and is read-only in Product Vision. This field is a way to enter and track original rough estimates directly using Product Vision. Chapter 5: Product Setup 39

40 Features Target Effort Defines the total planned effort for the feature in hours. This is a high-level estimate that can be entered and edited in Product Vision. When CA Clarity PPM and Product Vision are integrated, planned effort information comes from CA Clarity PPM and is read-only in Product Vision. This field is a way to enter and track original rough estimates directly using Product Vision. 4. Click Save and Close. After you create the feature, edit the feature details to add complete information about all aspects of the feature. Edit Feature Details You can edit specific feature properties. 1. Open the features list page and click Edit in the Actions column of the feature you want to edit. 2. Complete the requested fields. The following fields require explanation: Target Cost Defines the total planned cost for the feature. This is a high-level estimate that can be entered and edited in Product Vision. When CA Clarity PPM and Product Vision are integrated, planned cost information comes from CA Clarity PPM and is read-only in Product Vision. This field is a way to enter and track original rough estimates directly using Product Vision. Target Effort Defines the total planned effort for the feature in hours. This is a high-level estimate that can be entered and edited in Product Vision. When CA Clarity PPM and Product Vision are integrated, planned effort information comes from CA Clarity PPM and is read-only in Product Vision. This field is a way to enter and track original rough estimates directly using Product Vision. 3. Click Save and Close. 40 Getting Started Guide

41 The Product Roadmap View Feature Details The Feature Detail page contains information about an individual feature that you can view. To display the page, click View in the Actions column of the feature on the features list page. If you are the feature owner or an associated product owner, you can click Edit on the page and change the values for feature. In View mode on the Feature Detail page, you can: Create a requirement draft (see page 34) Add a notes and attachments to a feature. To learn more about notes and attachments, see Product Vision online help. The Product Roadmap The product roadmap displays the release time line for a product. The roadmap provides a view of master releases, with a high-level view and drill-down into releases and requirements. The monthly, quarterly, and yearly views show short-term and long-term implementation plans for delivering requirements and features. From the roadmap, you can easily link to product, release, and requirement detail pages, from which you can view, create, edit, clone, and delete objects. The first time you open the product roadmap, it displays the first product alphabetically. Select a product from the drop-down list, and the following time you open the roadmap, the product that you last viewed is displayed. Roadmap Navigation The roadmap provides multiple navigation choices that help you plan your releases. The default view shows the collapsed view of products and master releases and begins with the current date. You can navigate to dates earlier than the current date. Chapter 5: Product Setup 41

42 The Product Roadmap From the roadmap, you can use the following navigation controls: Specify the product name for the Roadmap Select a name from the Product list. The products are listed in alphabetical order. Zoom in or out with date ranges Select a date range from the Time Frame options. The zoom options are monthly, quarterly, or yearly time frame. Click the Navigation arrows to scroll horizontally. The double arrows take you to the next and previous pages. The single arrows scroll by one unit of time, based on the current time frame selection. The unit of time changes when you select a different time frame. Show or hide features associated with releases or requirements. Click the View Show Features or Hide Features options. Expand or collapse objects for master releases, releases, and features. Click the up or down arrows next to an object to expand or collapse a view of any child objects (child release or a requirement). Note: Requirement versions appear in the Roadmap, but requirement drafts do not appear. Click an object and to display the details page. View Details for Items in the Roadmap You can view high-level information for an item in the roadmap, such as a release. You can also open the item details page from the Roadmap. 1. From the Roadmap, select the product. 2. Choose one of the following options to view details for an item: Hover over the object with the pointer to view high-level information. The tool-tip for the object appears and displays the start and end dates, associated master release or products according to the object type. Click More to open the detail page for the object. Click the release or requirement object in the Roadmap area to open the Details page. The Details page for the object opens in view mode. 3. Expand master releases, products, releases, or features to display nested items. 42 Getting Started Guide