TP 2 User Guide

TargetProcess v.2.10 — User Guide TARGETPROCESS USER GUIDE v.2.10 User Guide This document describes TargetProcess functionality and provides information about TargetProcess usage. 1 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide INTRODUCTION ...................................................................................................................................................... 6 PROJECT PLAN STRUCTURE ............................................................................................................................................... 6 ITERATIVE DEVELOPMENT SUPPORT ................................................................................................................................... 8 USER INTERFACE: GENERAL PRINCIPLES ............................................................................................................... 10 LISTS .......................................................................................................................................................................... 11 OTHER INTERFACE AIDES................................................................................................................................................ 14 Next/Prev Navigation (new in v.2.10) ................................................................................................................. 14 Inline Editing ....................................................................................................................................................... 14 Easy Linkage ........................................................................................................................................................ 14 Context Help........................................................................................................................................................ 15 Last Action Message ........................................................................................................................................... 16 GENERAL ACTIONS ............................................................................................................................................... 17 INTEGRATED WINDOWS AUTHENTICATION ........................................................................................................................ 17 LOGIN ........................................................................................................................................................................ 18 SEARCH ...................................................................................................................................................................... 18 CUSTOMIZABLE DASHBOARDS ......................................................................................................................................... 19 TODO LIST .................................................................................................................................................................. 19 CONVERT ENTITIES FROM ONE TYPE TO ANOTHER (NEW IN V.2.10) ....................................................................................... 21 ADMINISTRATION ................................................................................................................................................ 22 USER & ROLE MANAGEMENT ......................................................................................................................................... 22 Add Users ............................................................................................................................................................ 22 Roles & Permissions ............................................................................................................................................ 23 AUDIT HISTORY ............................................................................................................................................................ 24 CUSTOM PRIORITY AND SEVERITY VALUES ......................................................................................................................... 25 EMAIL NOTIFICATIONS ................................................................................................................................................... 25 DISABLE HTTP ACCESS (NEW IN V.2.10) .......................................................................................................................... 27 PLUGINS ..................................................................................................................................................................... 27 Add New Profile .................................................................................................................................................. 28 See Profile Log ..................................................................................................................................................... 28 PROJECTS & PROCESSES ....................................................................................................................................... 29 PROCESS SETUP ............................................................................................................................................................ 30 Custom Terms ..................................................................................................................................................... 31 Ideal Hours and Abstract Points Effort Units ...................................................................................................... 32 Time Tracking Practice Customization ................................................................................................................ 32 ENTITY WORKFLOW CUSTOMIZATION ............................................................................................................................... 33 CUSTOM FIELDS ........................................................................................................................................................... 35 Add Custom Field ................................................................................................................................................ 36 Custom Fields Functionality ................................................................................................................................ 37 PROGRAMS & PROJECTS ................................................................................................................................................ 37 Add Program ....................................................................................................................................................... 37 Add Project to Program....................................................................................................................................... 38 Programs List ...................................................................................................................................................... 38 Manage Teams inside Entire Program ................................................................................................................ 39 Prioritize Projects ................................................................................................................................................ 39 PLANNING MODULE ............................................................................................................................................. 41 PROJECT PLANNING: FIRST RELEASE ................................................................................................................................. 41 Create Project Team ............................................................................................................................................ 42 Features (Themes/Epics) ..................................................................................................................................... 43 2 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Add Feature......................................................................................................................................................... 43 Add User Stories .................................................................................................................................................. 43 Quickly Add Tasks to User Story .......................................................................................................................... 45 Add Release......................................................................................................................................................... 45 Prioritize User Stories and Bugs .......................................................................................................................... 46 Release Planning ................................................................................................................................................. 48 Iterations Planning .............................................................................................................................................. 49 Iterations Planning using Iteration Plan Grid ...................................................................................................... 51 Assign Team Members ........................................................................................................................................ 54 Rank Concept ...................................................................................................................................................... 54 Split User Story .................................................................................................................................................... 56 Finish Iteration .................................................................................................................................................... 57 PROGRAM LEVEL RELEASE PLANNING ............................................................................................................................... 58 Add Program Release, Generate Project Releases and Iterations....................................................................... 58 Plan and Track Releases ...................................................................................................................................... 59 PROGRESS TRACKING..................................................................................................................................................... 61 Task Board .......................................................................................................................................................... 62 Daily Progress (Actual Remaining Time) ............................................................................................................. 62 Dashboard Components...................................................................................................................................... 63 Yesterday Tab...................................................................................................................................................... 64 IMPEDIMENTS MANAGEMENT ......................................................................................................................................... 64 Add Impediment.................................................................................................................................................. 65 See Impediments ................................................................................................................................................. 66 Private/Public Impediments ................................................................................................................................ 66 Reports ................................................................................................................................................................ 67 BUG TRACKING ..................................................................................................................................................... 68 BUGS WORKFLOW ........................................................................................................................................................ 68 Add Bug ............................................................................................................................................................... 69 Assign Bug ........................................................................................................................................................... 69 Change Bug Status / ToDo List ............................................................................................................................ 69 TEST CASE MANAGEMENT .................................................................................................................................... 70 TEST CASES CONCEPT OVERVIEW..................................................................................................................................... 71 TEST CASES LIBRARY...................................................................................................................................................... 71 ADD TEST CASES .......................................................................................................................................................... 72 ADD TEST PLAN AND ASSIGN TEST CASES .......................................................................................................................... 72 ADD TEST PLAN RUN..................................................................................................................................................... 73 RUN TEST CASES .......................................................................................................................................................... 74 TEST CASES PRIORITIZATION ........................................................................................................................................... 75 QUALITY STATS ............................................................................................................................................................ 76 Test Cases for User Story..................................................................................................................................... 76 TIME TRACKING .................................................................................................................................................... 77 ADD TIME ................................................................................................................................................................... 77 USING A TIME SHEET ..................................................................................................................................................... 78 Custom Activity ................................................................................................................................................... 79 Navigation........................................................................................................................................................... 79 VIEW SPENT TIME......................................................................................................................................................... 79 PEOPLE MANAGEMENT ........................................................................................................................................ 80 ALLOCATIONS .............................................................................................................................................................. 80 Who is overloaded?............................................................................................................................................. 80 3 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Who is available for an upcoming project?......................................................................................................... 80 Who can be re-allocated to another project? ..................................................................................................... 81 What assignments does each person have? ....................................................................................................... 81 Change Allocation ............................................................................................................................................... 82 LOAD REPORT .............................................................................................................................................................. 82 HELP DESK MODULE ............................................................................................................................................. 84 HELP DESK SECTIONS .................................................................................................................................................... 85 REQUESTERS MANAGEMENT........................................................................................................................................... 86 COMPANIES MANAGEMENT ........................................................................................................................................... 87 REQUESTS MANAGEMENT .............................................................................................................................................. 87 Add Request Manually ........................................................................................................................................ 88 Add Request from Email...................................................................................................................................... 88 Add Request via Help Desk Portal ....................................................................................................................... 89 Requests list ........................................................................................................................................................ 90 CREATE BUGS, FEATURES AND USER STORIES FROM REQUEST ............................................................................................... 90 TRACK REQUEST-TO-REQUIREMENT RELATIONS.................................................................................................................. 90 MERGE REQUESTS ........................................................................................................................................................ 91 HOW TO USE HELP DESK FOR GENERAL SUPPORT ............................................................................................................... 91 AUTO-REPLY (NEW IN V.2.10) ........................................................................................................................................ 92 AUTOMATICALLY BIND INCOMING EMAILS/REQUESTS TO THE PROJECT (NEW IN V.2.10) ........................................................... 93 HELP DESK PORTAL ....................................................................................................................................................... 93 Help Desk Portal Setup ........................................................................................................................................ 94 Help Desk Portal Modes ...................................................................................................................................... 94 Authentication .................................................................................................................................................... 94 Registration ......................................................................................................................................................... 95 Add Request ........................................................................................................................................................ 95 Requests Lists ...................................................................................................................................................... 96 Votes ................................................................................................................................................................... 97 Request Details ................................................................................................................................................... 97 EMAIL INTEGRATION ............................................................................................................................................ 98 PROJECT INBOX ............................................................................................................................................................ 98 Configuration ...................................................................................................................................................... 98 Usage .................................................................................................................................................................. 99 Sending Emails .................................................................................................................................................... 99 PERSONAL INBOX.......................................................................................................................................................... 99 BIND EMAILS TO ENTITIES ............................................................................................................................................ 100 Bind Email to Entity Action................................................................................................................................ 100 Emails in Entity View ......................................................................................................................................... 100 SUPPORT TICKETS (NEW IN V.2.10) ............................................................................................................................... 101 Enable Email Notifications ................................................................................................................................ 102 Enable Inbound Email Integration .................................................................................................................... 102 REPORTS ............................................................................................................................................................. 102 CUSTOM REPORTS ...................................................................................................................................................... 103 COMBINED REPORTS ................................................................................................................................................... 107 REPORTS IN SPECIFIC PROJECT ....................................................................................................................................... 108 PLANNING REPORTS .................................................................................................................................................... 109 Burn Down Charts ............................................................................................................................................. 109 User Stories Count by States Burn Down .......................................................................................................... 111 QUALITY ASSURANCE REPORTS...................................................................................................................................... 112 Bugs Distribution by Severity ............................................................................................................................ 112 4 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Bugs Dynamic.................................................................................................................................................... 113 Bugs Progress .................................................................................................................................................... 113 Bugs Count by States Burn Down ...................................................................................................................... 115 TEST CASES RUNS REPORTS .......................................................................................................................................... 116 Test Cases Runs by Release/Iteration/Build ...................................................................................................... 116 Test Cases by User Story ................................................................................................................................... 117 TIME TRACKING REPORTS ............................................................................................................................................. 117 Time Spent Summary ........................................................................................................................................ 117 PRINTABLE REPORTS ................................................................................................................................................... 118 SOURCE CONTROL INTEGRATION ....................................................................................................................... 119 SETUP SUBVERSION INTEGRATION .................................................................................................................................. 119 1. Install Subversion on the Server .................................................................................................................... 119 2. Configure Subversion Parameters in TargetProcess ..................................................................................... 119 3. Configure Project........................................................................................................................................... 119 BACKWARD INTEGRATION (VIEW ENTITIES FROM SUBVERSION CLIENT) ................................................................................. 120 SETUP SOURCE SAFE INTEGRATION ................................................................................................................................ 121 1. Install Source Safe on the Server ................................................................................................................... 122 2. Configure Source Safe Parameters in TargetProcess .................................................................................... 122 3. Configure Project........................................................................................................................................... 122 SETUP PERFORCE INTEGRATION ..................................................................................................................................... 122 1. Configure Perforce Parameters in TargetProcess ......................................................................................... 123 2. Configure Project........................................................................................................................................... 123 BIND COMMITTED FILES TO BUGS .................................................................................................................................. 123 VIEW FILES AND REVISION DIFFERENCES ......................................................................................................................... 124 TAGS (NEW IN V.2.10) ........................................................................................................................................ 125 TAG ENTITIES ............................................................................................................................................................. 125 SEARCH BY TAG .......................................................................................................................................................... 126 MANAGE TAGS .......................................................................................................................................................... 126 Add Tags ........................................................................................................................................................... 126 Delete Tags ....................................................................................................................................................... 126 Rename Tags ..................................................................................................................................................... 127 MANAGE BUNDLES ..................................................................................................................................................... 127 Add Bundle ........................................................................................................................................................ 128 Add/Remove Tags ............................................................................................................................................. 128 TAGS BOARD ............................................................................................................................................................. 128 IMPORT/EXPORT ................................................................................................................................................ 130 IMPORT FROM CSV..................................................................................................................................................... 130 EXPORT INTO CSV ...................................................................................................................................................... 131 APPENDIX A. RESOURCES ................................................................................................................................... 133 TargetProcess is a Web-based project management tool that powers agile software development processes, focusing on Project Planning, Project Tracking and Bug Tracking practices. TargetProcess supports Extreme Programming and other modern iterative methodologies. 5 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Introduction This section describes main ideas behind TargetProcess software. It should help you to understand TargetProcess better. Project Plan Structure Each project may consist of several entity types depending on Project size and requirements. The overall structure is shown in the diagram below: Program: Generally this is a large Project. For better manageability, a large Project may be divided into several smaller projects (Project 1 and Project 2 in the illustration above). In most cases a Program is not required, but if you have Projects with several teams, a Program will help organize the work and track progress better. Project: A Project is simply work encompassing one or more features that must be created or modified. Feature (or Epic): A Feature is a high level requirement. Examples are “Advanced Search”, “CSV Import/Export”, or “Leads Management”. In most cases, Features are required for large and medium Projects. Each Feature contains several User Stories. User Story: A User Story is a unit of work that can be used as requirements and as a planning item. For smaller Projects, Features are overhead, so User Stories take all the responsibility. 6 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Typical examples of User Stories are “Search for Contacts”, “Filterable List of Contacts”, or “Custom Drop Down Fields”. Task: A Task is the smallest planning unit that describes a small piece of functionality. Examples: “Add User UI Creation”, “Add User Controller Implementation”, “Add User Business Logic Implementation”. For large Projects, it is better to use the complete hierarchy. Program -> Project -> Feature -> User Story -> Task However, for small Projects, a simplified hierarchy may be sufficient: Project -> User Story -> Task Hierarchy example: Program: NewWave CRM Project: NewWave CRM Core Feature: Basic Contacts Management User Story: Quick Add Contact Task: UI Design Task: Implement Add Contact Logic User Story: Contacts List Task: Filters Task: List Sorting Task: Contact List Page and Base Logic Task: UI Design User Story: Delete/Undelete Contact Feature: Users Management Feature: Permissions Project: Outlook Sync Feature: Import/Export Contacts to Outlook User Story: Export Contacts Task: Duplicate Checking Development Task: Export Rules Implementation Task: Export UI Implementation User Story: Import Contacts Feature: Import Scheduled Tasks from Outlook Feature: Read Emails Online Feature, User Story, and Task are planning items that allow creating a Work Breakdown Structure (WBS). Let’s see how to create a Project plan. 7 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Iterative Development Support TargetProcess supports iterative development. The iterative project planning approach is described in many sources. We recommend “Planning Extreme Programming” by Kent Beck and Martin Fowler, if you are new to the concept. Other sources are in Appendix A. Basically, each Project can have several Releases and each Release can have several Iterations. (See the diagram below.) All Iterations should be of equal duration. In this example, we use 2 weeks. 8 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide You may assign Features to Releases, thus creating a high level plan (Road Map). Also you may assign User Stories to Iterations, thus creating a low level plan (Iterations Plan). One Feature can spread over several Iterations. However, you should implement the Feature in the Release, or else split a large Feature into two or more smaller Features. The entire planning process can be described in several steps: 1. Add Requirements a. Add Features b. Add User Stories for Features 2. Create Project Schedule a. Add Releases and Iterations (TargetProcess can generate Iterations for you during Release creation) 3. Assign planning items a. Assign Features to Releases b. Assign User Stories to next Iteration 4. Add details to the plan a. Add Tasks for User Stories b. Assign team members to Tasks 9 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide As a result you will have high level Project plan and a plan for the initial Iteration. You may also plan future Iterations, but this is not required. Such plans will likely be changed after the first Iteration has been completed. User Interface: General Principles The User Interface in TargetProcess consists of several parts. 1. Top menu containing high level links like Users list, Projects list, and Admin 2. Search 3. Tabs containing Add actions and links to Practices (Planning, QA, Requirements) when you are inside a Project 4. Help area containing clickable, context-dependent workflows for various tasks. 5. Main area containing lists, edit forms, and all other content. 10 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Lists Lists in TargetProcess are unified and have several common parts. 1. 2. 3. 4. 5. 6. 7. Add entity link Batch actions Sorting columns Highlight current list area Filters Context actions Inner list Add entity link in list header Add a new entity to the current list. Sorting columns Click a column name to sort items in the list. Current area Highlight current list area Context actions Lists item-related actions. For example, if you are in the User Stories list, the following actions available: Add Task, Add Time, Add Bug and Add Test Case. 11 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Common actions View , Edit and Delete actions are represented by icons. Collapsing Click / to expand/collapse the list. Releases list contains Iterations, Iteration list contains pse User Stories, User Stories list contains Tasks. Paging Click the Next/Prev links at the bottom of the list to move to another page. Batch actions (delete, copy, update) , update Select the required items and click the More Actions link in list header. Click the required action. Filters Click the Filter link in the table header to see the filter panel. You may save the current filter and load it later. 12 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide 1. Filters 2. Saved filters management area Customizable columns and inner lists To turn off unnecessary columns, click Customize, uncheck columns, and click Save Settings. 13 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide 1. Visible columns 2. Inner lists Other Interface Aides There are also several aides, such as Context Help and Color Coding, that improve overall usability. Next/Prev Navigation (new in v.2.10) You may navigate entities in list one by one. Filter entities in list and click any entity to see view page. Right near the entity title there will be Prev / Next links. Click Next link to see next entity in the list. Inline Editing Inline editing is available in User Stories, Bugs, Requests and Features lists. To enable inline editing for row just double click table row. Change required values and push Enter to save change. You may cancel editing by pushing Escape key. Easy Linkage You may quickly reference entities like bugs, user stories, features, etc. when creating comment or description. For example, you are adding a comment to user story and want to add a link to 14 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide bug with id = 85. You may just type id:85 in comment field and TargetProcess will automatically render this as a link to required bug. Context Help Available in certain sections via Show Info links In add/edit forms, a help message appears when a specific field receives the focus. 15 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Last Action Message When something is added, updated or deleted, TargetProcess shows a message. This ensures you that the action has been processed correctly. The message contains links on the entity view page and the entities list, so you can quickly navigate to view entity details. 16 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide General Actions Integrated Windows Authentication TargetProcess supports Integrated Windows Authentication. Two actions are required to enable it: • Enable the Integrated Windows Authentication for TargetProcess virtual folder (Internet Information Services Manager -> right click on TargetProcess virtual folder -> Properties > Directory Security -> Authentication and access control). IMPORTANT: Disable anonymous access, otherwise integration will not work. • Specify the Active Directory User Logon Name for users in TargetProcess. (Example: If you setup the Windows domain CompanyUsers and user login ted, then you should specify the Active Directory User Logon Name as CompanyUsers\ted) Then when a user accesses TargetProcess, he will be automatically authenticated and redirected directly to the Dashboard screen. 17 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Login After TargetProcess system installation, you can login using the following access parameters: Page: http:///default.aspx Login: admin Password: admin Important: It is recommended that you change the login and password after the first login! It can be done in People area. Search Search has four modes: • • • • Global search: In effect when outside any specific Project. Shows results from all Projects. Project search: In effect when inside a Project. Shows results from the current Project only. Jump: Entering an entity ID redirects to the entity view page (for example, type 123 in the search box and click Search button to jump to entity with 123 id). Search by Tag: Type tag:[tagName] to find entities tagged tagName. For example, type tag:"Visual Studio" to find all entities tagged “Visual Studio”. Following a search, you may filter the results by entity type (for example, see only Bugs or User Stories in results). 18 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Customizable Dashboards You may customize both the Global and the Project Dashboards. On a dashboard page, click the Customize dashboard link at the top to enter customization mode. 1. Dashboard components catalogue 2. Dashboard zones 3. Use drag and drop to customize dashboard When you are done, click the Finish customizing link at the top. ToDo List TargetProcess provides an integrated ToDo list for all assignments, including User Stories, Tasks, and Bugs. You may do the following actions in ToDo list: • Sort assignments by similar columns like Name, Rank, etc • Filter assignments by current release or iteration, by state, by custom field value • Show/Hide different columns to customize ToDo list for your needs • Change states of assignments • Add time for assignments 19 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide In latest version custom fields column added as well as a filter by custom field value. 20 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Convert Entities from One Type to Another (new in v.2.10) Sometimes is required to convert bug to user story or feature to user story. You may do the following conversions in TargetProcess: Feature Feature to Story to Task to Bug to Yes Yes Yes Story Yes Task Yes Yes Bug Yes To do the conversion, navigate to entity view and find Convert link in the Actions section. Click Convert link and new popup appears: Select required target entity and push Convert button. Current entity will be deleted and new with selected type will be created. 21 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Administration User & Role Management Add Users Project teams can be composed of system users. To add a user, login to the system and click the People link on the top menu. Then click Add -> Add Person. Administrator Active User has unlimited access to all projects User is able to login into the system. It is possible to reuse licenses by deactivating users. User has read-only access to all projects Observer Complete the required fields labeled in bold type. Then click Save or Save & Add New. 22 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Roles & Permissions TargetProcess has role-based permissions on add/edit/delete actions. For example, you may . prohibit developers from deleting anything in the system. Click the Admin link at the top and then click Roles to see the list of roles. Click the (edit) icon for the Developer role. /uncheck Check/uncheck boxes as needed and click Save. Note that there are no restrictions on view actions inside a Project. For example, if a developer belongs to the Project A team, she can view all the information inside Project A (bugs, reports, team, etc.). But if she does not belong to Project B, she will not see any information from Project B. Available permissions: 1. Restrict user access to Projects (administrator has full access, while other roles do not). Sometimes you do not want to disclose Project information to a user. For example, you 23 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide want to add your customer to a Project team, but the customer should not have access to other Projects. 2. Restrict editing and deleting of entities for each role. Audit History TargetProcess stores all information about changed entities (additions, updates and deletions), so you can see who made the change and when it was modified. To see the complete audit history, navigate to the Project, click Admin then the Audit History tab. You may filter history records by User, date range and entity type. You can see the change history for a specific entity on the entity view page. For example, to see changes to a User Story, navigate to the User Stories list and click a User Story name. Then click the History tab. 24 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Custom Priority and Severity Values You may customize the values of Priority for Feature, User Story, and Bug as well as Bug Severity. Click Admin -> Priority/Severity to see a list of Priorities for all entities. You may delete, edit, or add new a Priority. Note that Importance works together with Priority. Importance is a numeric representation of Priority. If two entities are of equal Priority, the top Priority will be the one with the smallest (numerically) Importance. For example, if you have a Must Have Priority with Importance = 0 and another Must Have Priority with Importance = 1, then the Must Have Priority with the zero Importance receives top Priority. You may set default priority and severity for entities. Email Notifications TargetProcess can send email notifications when an entity is added and when an entity is assigned/reassigned. For example, when a User Story is assigned, TargetProcess can send notifications to: • • • • Any role in the project team (Developer, Project Manager or other) The entire project team An assigned user The User Story owner To enable email notifications, click Admin then General Settings. Check the Enable Email Notifications box, specify SMTP server, port and access parameters if required. Save the changes. 25 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Then navigate to Workflow and select the required entity (for example, User Story) and click the Assign tab. Check the Notify by email box and select the user groups to be notified. Save the changed Workflow. 26 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Disable HTTP Access (new in v.2.10) You may disable HTTP access and allow TargetProcess users to connect via HTTPS only. Navigate to Admin -> General Settings and mark Disable HTTP access checkbox: Plugins Starting from v.2.8 TargetProcess provides plugins architecture. You may create custom plugins using C# API and add them into TargetProcess plugins folder. There is a separate guide that describes plugins architecture and provides information about custom plugins implementations. To see installed plugins, navigate to Admin -> Plugins section. All plugins divided into categories and each plugin may have many profiles. Depending on plugin nature, you may have different profiles for different projects for example or based on some other criteria. 27 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide If plugin supports Synchronizable interface, you may check connection of the plugin or reset synchronization date. If you click Reset Sync Date button, synchronization will be scheduled within specified time frame (setting in plugin profile). This may be useful when you tune plugin settings and want to run synchronization again. Add New Profile To create new plugin profile, click Add Profile link. Profiles for each plugin are different; it is a responsibility of plugin developer to create correct plugin setting. By default TargetProcess has only one plugin installed Bugzilla Integration. Check correspondent section of this user guide see how to configure and use Bugzilla Integration plugin. See Profile Log It is a responsibility of Plugin developer to log all plugin activities. You may see them in Log section. Log contains all sync session with final result (success of failed) and additional information. You may click on record date to see comprehensive details of the sync session results. 28 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Projects & Processes In real life, each Project may have its own unique process. No Project management application can support all possible processes, but TargetProcess’ goal is to provide great flexibility. The Processes concept makes this possible. Currently a Process consists of Practices and each practice can be customized. Also it is possible to customize Terms for each Process. Future releases of TargetProcess may introduce Tools and other Process-related features. Supported practices/customizations: • Planning o User Story effort is a sum of Tasks effort o Ideal Hours or Points effort units • Bug Tracking • Time Tracking o Close Assignable if time remaining is zero o Make time description field visible o Mark time description field required • Requirements Management • Test Case Management • Source Control • Help Desk 29 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Process Setup TargetProcess supports flexible settings for each Project via the Process concept. Each Process consists of Practices like Planning, Time Tracking, Bug Tracking, etc. It is possible to enable/disable Practices and customize each Practice. For example, if you are starting a very small project and only want to use the Planning module without Bugs, Test Cases and other items, click the Admin link at the top and then the Processes link. Finally, click Add. 30 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Fill in any required fields, uncheck boxes as needed, and save the new Process. Then you can create the Project and select only that Process for it. Since there will be no Time Tracking, Bug Tracking, and Requirements areas in the newlycreated project, the interface will be much simpler. Custom Terms In TargetProcess you may customize the terminology used in each Process. For example, you may create terminology for SCRUM or any other process you have. The following terms may be changed: • • • • • • Release Iteration User Story Feature Bug Impediment Click Admin -> Processes. Then click edit for the Process you want to change and click Terms tab, fill in any required terms, and save the changes. All Projects that use this Process will now use your custom terms. For example, if you replace Iteration with Sprint, you will not see the word Iteration inside the Project area, but only the word Sprint. Also you may reset the terms in a specific Process to restore them to their original values. 31 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Ideal Hours and Abstract Points Effort Units You may customize Practices for each Project. For example, you can set the effort units (Points or Ideal Hours), and you can choose to close/not close a User Story if there is zero time remaining. To customize a Practice, navigate to the Processes list and click the (edit) icon for a Process. Then click the Customize link for a Practice. The Planning practice customization page is shown in the diagram below. Select the required values and save your changes. For example, you may use Points effort units for one Project and Ideal Hours for another Project. Your choice depends on team experience and personal preferences. Time Tracking Practice Customization You may customize Time Tracking practice with the following settings: • Close Task, User Story, or Bug if time remaining is zero • Make time description field visible/hidden 32 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide • Mark time description field required/optional Entity Workflow Customization You can create a custom Workflow for each entity and for each process. This affects all projects based on the process, so it is recommended that you create the Workflow before starting a Project. Click Admin -> Processes -> Edit -> Workflows and select an entity type to manage the Workflow. For example, let’s change a Workflow for a User Story. The initial Workflow is shown in the diagram below: 1. Application Events (Add entity, Change entity state, Assign entity) 2. Rules (Notify by email, assign entity to person) 3. Entity State This User Story has two states: Open and Done. We are going to add an Accepted state that will follow the Done state. Click the Add New State link. 33 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide . acto As you can see, each Entity State (except the final state) should have an Actor. An actor plays a defined role in the entity Workflow. Suppose we have three states for a User Story: Open, Done, and Accepted; and we have two Actors: Developer and Acceptor. ; When the User Story is in the Done state, it should be assigned to an Acceptor, so the Done state should have an Acceptor Actor. Let’s add this Actor. Click the Manage Actors link. The Actors list will appear on the right. Click Add New for the Actor, give the Actor a name, and click Update. (edit) icon for the Done state, and select the Acceptor actor. Select Accepted Now click the as the next state and click Save. We have defined the Workflow as shown in the diagram below: 34 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide We may also add rules for each state. Currently, only the Assign to and Notify by email rules are available. If you want to assign it to the Project Manager for final verification when the User Story is Done, you would enable the Assign to rule for the Done state (by checking the box), check the Project Manager box, and click the Save Workflow button. If the Project team has a member with the Project Manager role, he will be assigned to all completed User Stories and will see them in his ToDo list. Custom Fields Custom fields allow gathering and storing specific information about an entity. Custom fields are available for all entities in TargetProcess (Project, User Story, Bug, Time, etc.) You can create Custom Fields for each entity and for each process. This affects all projects based on the process, so it is recommended that you create custom fields before starting a Project. 35 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Add Custom Field Navigate to Click Admin -> Processes -> Edit -> Custom Fields and click the Add link. Each custom field relates to a specific entity (User Story, Bug, Project, etc.) Select the desired entity, specify a label that will be visible in the add/edit entity form, select the type of custom field (Text, Checkbox, Drop Down, Date, Rich Text or URL) and save it. It is possible to add the same custom field for several assignable entity types (Bug, User Story, Task, Feature, Request, Test Run). When you select any of the assignable entity type, checkbox list with all the other entity types appears. Just select required entity types. For example, To add Risk custom field to Bug, User Story, Feature and Request you may mark the following checkboxes: 36 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Custom Fields Functionality You will see custom fields on these pages: 1. Add/Edit entity 2. View entity 3. Entities list You may sort and filter by custom fields in lists. Check the “Enabled for filter” box during custom field creation, if you want to filter data by this custom field in lists. Programs & Projects Usually a Program is just a large Project. For better manageability, a large Project may be divided into several smaller Projects. In most cases Programs are not required, but if you have Projects with several teams, Programs will help to organize the work and track progress better. Add Program Click the Add -> Add Program link on the left to see the Program addition form. Fill in any required fields and save the Program. 37 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Add Project to Program Click the Add -> Add Project link on the left. Select a Program from the drop down list, fill in other fields as needed, and save the Project. Programs List Click the Programs link on the top to see the Programs list. Click the “+” sign to see all Projects in the Program or the “-” sign to hide the Projects. The Program area consists of the following parts: 38 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide • • • • • • Bugs: contains bugs from all projects and program itself Planning -> User Stories backlog: contains unassigned Program User Stories. Planning -> Releases: contains program level releases Planning -> Release Plan: program level release plan General -> Program team Help Desk: contains all requests from all projects Manage Teams inside Entire Program You can manage all Project teams inside a single Program. Navigate to Program and click General -> Team. You may reassign people from one Project to another, change allocation percentages and dates, and change roles. Adjust values as needed and click the Save button. Prioritize Projects You may prioritize projects using drag and drop right in projects list. Drop required project row and move it higher or lower in the list. Projects will change rank after re-prioritization. Projects with higher rank have higher priority. 39 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide So far this information is used in overall ToDo list. Assignments from projects with higher priority will be on top of ToDo list (if the list sorted by Rank). 40 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Planning Module Project Planning: First Release Basically, the agile planning process consists of the following steps: 1. Create Features. A Feature is a high level requirement. For large Projects, it is recommended to add Features and create a Project Roadmap. 2. Create User Stories. Estimate each User Story using ideal days or points. Two items are important: a. Effort units will remain the same during the whole Project. b. An Iteration’s Velocity is measured in the same effort units. 3. Create a Release with Start and End dates and split the Release into several Iterations of equal length. (It is recommended to make each Iteration from 2 weeks to 1 month in length, depending on your environment and Project size.) 4. Assign several most valuable or risky User Stories to the first Iteration. 5. Complete as many User Stories as possible during the first Iteration and define first Iteration’s Velocity. The Iteration Velocity is the sum of all implemented User Stories’ effort during the Iteration. For example, during the Iteration #1, assume you have implemented the following User Stories: a. Users Authentication – 4 points b. Users’ contact information management – 3 points c. Forms validation – 2 points d. Internal mailing engine – 7 points The Velocity of the first Iteration will be Velocity = 4+3+2+7 = 16 points Then you set the Velocity of the next Iteration based on the average Velocity of all previous Iterations. In our case, the predicted Velocity of Iteration #2 will be exactly 16 points. Using this iterative approach, you get significant advantages: • You can predict with very good accuracy how much effort the project team will accomplish during the next Iteration, and you can make fair prediction about the true Release date. • The most valuable Features and Requirements will be implemented first. This is good for the customer and for the Project as well. • You can easily change the plan based on the customer’s real needs. System requirements will change, and change requests are handled much more efficiently. 41 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Let’s see how TargetProcess can help you in agile project planning. Create Project Team A Project team may be created from all available system users. So if you want to add a new team member who does not have a system account, you first create a new account, as described in the Add User section. To create a Project team, choose the Project from Projects list, click the Admin tab and then click the Team link. Use the Add To Team and Remove From Team buttons to build a team. You may select several users at a time by holding the Ctrl key. You may set roles, possible weekly effort, and allocation parameters for each team member. Note that allocation percentage and allocation end date are important parameters, they influence overall people allocation report. 42 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Features (Themes/Epics) High level requirements are represented by the Features concept in TargetProcess. A Feature is larger than a User Story, and one feature may contain several User Stories. In some sources Features are called Themes or Epics. Features are similar in behavior to User Stories but with these exceptions: 1. Features can only be assigned to Releases, not to Iterations. 2. Features can spread over several Releases. Add Feature Navigate to a project and click the Add -> Add Feature link on the left. Enter a Name and Description for the Feature and select a Priority. The Initial Estimate field contains the anticipated effort for the Feature. At this point you may also assign the Feature to a Release. Click Save & Exit to add the new Feature to the current Project. Add User Stories Choose a Project and click the Add -> Add User Story link on the left. 43 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide 1. 2. 3. 4. 5. Enlarge description area if required Bind User Story to Feature Quickly assign User Story to current Release or Iteration, assign User Story to developer Quickly add several tasks to User Story Attach files and tag User Story There is only one mandatory field: Name. You may assign a User Story to two developers (simple pair programming support). Alternatively, you may assign it only to a Release, thus creating a Release Back Log. The Description field should contain User Story details. This is a WYSIWYG field, so it is possible to present the User Story description in a more user-friendly format. Business Value indicates User Story importance from the customer’s point of view. The most valuable User Stories should be implemented as early as possible. You may assign a User Story to Iteration using the Release/Iteration drop-down. (By default, a new User Story is put into the Back Log.) 44 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide You will often add several User Stories in a row. Use the Save & Add New button to facilitate this process. The most complex thing about a User Story is effort. In TargetProcess, effort is measured in one of two possible units: Ideal Hours or Points. You may select effort units for your Project by customizing the Project’s process (see the Process Setup section). In the diagram above, we use ideal hours. There are two possible cases for User Story effort calculation: 1. A User Story (US) can be considered a Task with its own effort included in the total User Story effort. So US Total Effort = Sum(Tasks Developer Effort) + US Developer Effort 2. A User story is just a container and its effort is a sum of all related Tasks’ effort. Then the calculation will be US Total Effort = Sum(Tasks Developer Effort) This is a customizable setting which you may change for any Process. In the diagram above, the first model is implemented, so the total User Story effort is 31h (tasks effort) + 33h (own user story effort) = 64h Quickly Add Tasks to User Story You may quickly create tasks when adding or editing user story. There is Tasks section in the bottom of the form. You may type task name, set task effort and click Add link. All these tasks will be created after Save action. Add Release Chose a Project, then click Add -> Add Release 45 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide TargetProcess will automatically generate Iterations for the new Release. You must set Start Date, Finish Date and Iteration duration in days. Then save the Release. The system will create required Iterations with default names (like Iteration #1.1). Prioritize User Stories and Bugs A common task for a Project Manager/Product Owner is prioritizing User Stories and Bugs. For example, you may have 5 “Must Have” User Stories and 10 “Fix ASAP” Bugs. It may appear that 3 of the Bugs are most important in the current Iteration, then the 5 User Stories should be implemented, and then the other Bugs should be fixed if possible. The Prioritize tab in the Iteration Planning area supports this scenario. 46 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide You may reorder User Stories and Bugs. Prioritization changes Rank of User Story or Bug. Rank column visible in lists as well as in ToDo list. You may right click on user stories and bugs to see details like Description, State and Assigned people. 47 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Release Planning TargetProcess supports high level Release planning by assigning Features, User Stories and Bugs to Releases. Click the Planning tab and the Release Plan link. • • • Left area contains project backlog. It contains Features, User Stories and Bugs. You may o Filter backlog to see only features, for example; o Sort backlog by name, priority and effort; o Right click on item to see additional details. Right area contains releases timeline with current and future releases. You may expand releases to see all assigned items. There is a timeline switcher on the top. You may select between Weeks scale and Months scale. To assign a Feature, User Story or Bug you may drag and drop it on the Release area (on the right). You may reassign item from one release to another. Expand release details, drag the item and drop it into required release box. Each Feature may contain several User Stories, and User Stories can be assigned to different Releases. For example, you can release Feature A in Release #2, but still have some User Stories implemented in Release #1. In this case, the Feature will have a different effort in each Release. If you move a Feature to another Release, all open and not started User Stories will move with this Feature, while all closed and in progress User Stories stay in the previous Release. You may right click on user stories and features to see details like Description, State and Assigned people. 48 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Iterations Planning It is possible to assign a User Story to an Iteration while adding the User Story, but the more common practice is to plan Iterations using the Iteration Plan page (Planning -> Iteration Plan). An Iteration Plan consists of three lists which contain User Stories and Bugs. You may select any Iteration in any list and have quite a flexible playground for Iteration planning. Planning itself is easy, just drag the User Story or Bug you want to assign and drop it on the required Iteration. (Available drop zones will be highlighted.) In the diagram below, we assign a Bug to Iteration #1.2. Also you are prioritizing User Stories and Bugs during Iteration planning, thus having top priority items first in developers’ ToDo lists. This almost completely eliminates questions like “What should I work on first?” Sometimes you don’t want to change priorities during iteration planning. For example, Product Owner already set required priorities and you should not change them. In this case you may disable prioritization. Click Customize link and unmark the checkbox shown on the picture below 49 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Also you may filter User Stories and Bugs in any list (backlog and iteration). Click on Filter link, select required filters and push Filter button. You may right click on user stories and bugs to see details like Description, State and Assigned people. 50 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Iterations Planning using Iteration Plan Grid Alternative mechanism is Iteration Plan Grid. It is a new iteration planning concept that appeared in v.2.6. Click arrow icon on Planning tab and select Iteration Plan Grid link. Iteration Plan Grid consists of three areas. You may select iterations in two top areas select Product or Release backlog in bottom area. The main idea of this area is to visualize important and large User Stories and Bugs. User story with top effort has large size, while user story with small effort has small size. The most important user story is visually different from the least important. Use drag and drop to assign/reassign User Stories. 51 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide 1. Iteration area size represents Iteration Velocity. Iteration area contains assigned User Stories and Bugs. 2. Product/Release backlog area. Shows User Stories and Bugs from backlogs. It is possible to sort them by effort, priority and alphabetically. 3. Closed blocking bug marked with grey color and blocking icon. 4. Keyword filter helps to quickly find User Story. 5. Size of User Story or Bug shows effort; color shows priority. It is possible to edit items right there. Right click on User Story and context menu will appear: 52 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide You may change User Story name, effort and priority. IMPORTANT: This feature may not work in FireFox by default. Go to Tools -> Options -> Enable JavaScript -> Advanced and mark Allows script to Disable or replace context menu checkbox. After that you may use right click to edit entities. 53 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Assign Team Members You can assign User Stories, Tasks and Bugs to team members. Click the Assign Team Members tab. The list on the left contains unassigned Bugs, Tasks and User Stories. The list on the right contains all team members. You can assign a User Story or Bug by dragging and dropping it on a developer. Bug will immediately appear in corresponding ToDo lists. For example, you can assign the “Javascript error in FireFox” Bug to Jerry Mouse. When Jerry logs in, he will see this Bug in his ToDo list. Rank Concept Prioritizing items, you assign them specific Rank that is visible in User Stories List, Bug List and ToDo. Rank is a reverse order of item in Prioritize list. For example, you have 5 items in the list. Then the first item will have rank 5, while the last item, will have rank 1. Rank has some rules: • It exists only for open User Stories and Bugs • Higher rank means higher importance • All Tasks within User Story inherit User Story’s rank. For example, if you have User Story with rank 34, all tasks in this User Story will have rank 34 54 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Set Iteration Velocity When the first Iteration has been completed, it is time to set the Velocity for the next Iteration. Choose Project, click the Planning tab and the Iterations link to see the Iterations list. Find the required Iteration and click the (edit) icon. Fill in the Velocity field and save the Iteration. Add Tasks Quite often it is necessary to split a User Story into several Tasks, especially if the User Story is quite large and should be implemented by two or more people. For example, a “Simple Shopping Cart” User Story may have several Tasks: pping • Create GUI design of shopping cart • Implement business classes (ShoppingCart, Order) • Create database tables To add Tasks for a particular User Story, navigate to the User Stories list. Find the required User Story and select Add Task from the Add menu: 55 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide The form for Task addition will appear as shown below. You must specify a Task Name; other fields are optional. Notice the User Story effort calculation area in the diagram above. When you add a Task, you see total User Story effort and how this Task changes User Story effort. In this example, the User Story has 26h of its own effort, and this new Task adds 8h of effort. If you check the Subtract this effort from User Story effort box, 8 hours will be subtracted from the User Story’s own effort and total effort will remain 26h. Split User Story Sometimes you may need to split a large User Story into two smaller User Stories. Navigate to a specific User Story view page and click the Split link in the Actions list to see the Split area. 56 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide 1. Update effort and assignments 2. Move tasks from original to new user stories TargetProcess immediately creates a new User Story and you may • Move several Tasks to the new User Story, • Cut and Paste part of the description from the original to the new User Story, and • Assign the new User Story to a specific Iteration or Release. • Set user story effort. • Assign user story to team member. Click Save & Exit to apply the changes or Undo to delete the new User Story. Finish Iteration When the Iteration end date has passed, you may still have open User Stories. Usually you will want to move all open User Stories to the next Iteration. Navigate to Planning -> Iterations and find the Finish link. 57 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide You will see two options available: 1. Split “in progress” User Stories that have Tasks and move not started User Stories to the next Iteration. 2. Move all open User Stories to the next Iteration. Click one of the two buttons as needed. NOTE: It is not possible to Undo the “Finish Iteration” action. Program Level Release Planning Program Level Release Planning allows to create releases and iterations for all projects inside program and to plan program and projects release on the one screen. Add Program Release, Generate Project Releases and Iterations There are two concepts of Release in TargetProcess: • • Program Release – release of whole program. It combines several projects releases and set one final release date that is a good reference point for all projects. Project Release – release of a single project. To add Program Release go to specific program, click Add -> Release link. You will see a form for release addition. 58 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide It is required to specify release name, start and end dates. Also you may generate releases in all projects inside program as well as iterations. All generated iterations will have equal duration. Plan and Track Releases Click Planning -> Release Plan link to navigate to Program Level Release Plan. This screen consists of two sections: Backlog on the left and Release plan diagram on the right. 59 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide 1. Program backlog contains all user stories and features from all projects inside current program. You may filter backlog items by project and sort them by name, priority and effort. 2. Release plan shows all current and future releases for all projects. Current releases marked blue color. 3. Current release for project contains all user stories and features assigned. Each release has total assigned effort and progress information as well as forecasted release date. If forecasted date exceeds original release date you will see dashed blue border on the right. Also you may use +/- buttons to expand/collapse assigned items. 4. Program release deadline and forecasted program release dates. 5. Each item (user story or feature) has effort and name. Color of the item represents priority (green items have top priority while white items have lower priority). Done items marked gray color. It is required to use drag and drop to assign features and user stories to release. The following assignments can be used: • • • Assign user stories and features from backlog to release (to any project). If you assign user story from Project A backlog to Project B release it will be moved to Project B Assign user stories and features from release to release in the same project Assign user stories and features from release to release in different projects (in this case user story will be moved from one project to another) 60 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide You may edit release start and end dates. Right click release bar and context menu will appear. Modify required values and click Save link. Progress Tracking The Reports tab contains all available reports and charts. The Progress section in the Tracking area is the main feature for daily Iteration tracking. 61 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide The Task Board powers daily Tasks management activity. Also there are several dashboard components for progress tracking: • • Progress Summary Time Spent Summary And there is a Yesterday tab in the Dashboards area that shows what happened yesterday. Task Board The Task Board is an area that powers effective Tasks management. When all User Stories are set for Iteration, this is the best place to manage Tasks. Click Planning -> Task Board. The Task Board provides the following actions: • Change Task state (from open to done, for example) • Assign/Re-assign people to Tasks and User Stories • Update remaining time for Tasks • Show Tasks for a specific person • See User Story Impediments You can customize the Task Board view. You can setup a very simple layout with a minimum of detail or a complex one with many details. Click the Customize link and uncheck boxes as desired to hide specific information. Daily Progress (Actual Remaining Time) The only way to get actual information about User Story/Task completeness is to ask the developer. TargetProcess does exactly that. When a developer adds a time record, she should enter a remaining time value as well. Using this information, actual work remaining can be calculated. 62 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide The table below shows daily remaining time for each User Story and Task for the current Iteration. If remaining time increased in compared to the previous day, it will be highlighted in red. If remaining time decreased, it will be highlighted in green. Thus you see daily team progress and can identify problematic Tasks and User Stories. Also you can see how much time has been spent on each Task. You can move your mouse over a time remaining cell to see a tool tip as shown below. Dashboard Components Navigate to Dashboards and click the Customize Dashboard link on the right. Then check the Time Statistics and Progress Summary boxes in the Controls Catalogue and click the Add button. Selected dashboard components will appear in the main area. Click the Finish customizing link. The Progress Summary component answers the most important question in software development: “When will the release be completed?” This knowledge comes from the historical data analysis and the remaining work calculation. TargetProcess forecasts the Release finish date and shows the current Release and Iteration progress. 63 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Yesterday Tab The usual questions every Project Manager asks herself in the morning are these: • • • What did we accomplish yesterday? Are there any new requirements from the customer? How did our team members spend their time yesterday, and were there any problems? The answers are on the Yesterday Dashboard screen. Impediments Management An Impediment (or Block) is an obstacle that prevents User Story/Task/Bug completion. For example, you may have Impediments such as these: 64 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide • • • New server for performance testing will be purchased Jan-20, so we are unable to start Jan 20, performance testing till that date for now Teddy Bear left the company and complex User Story “Patterns recognition algorithm” can’t be implemented by any person on our team. This task needs highly specialized knowledge. Jerry doesn’t want to communicate at all with team. TargetProcess provides the functionality to manage Impediments in your Project: • Add Impediments to User Stories, Bugs, and Tasks. • All User Stories, Tasks, and Bugs with Impediments are marked with a special symbol so you can quickly see all related Impediments. • You may create public or private Impediments. Private Impediments will be visible to the owner and responsible persons only. • There are several reports that show Impediment dynamics and distribution. Add Impediment Click the Add -> Add Impediment link to see the form for Impediment addition. > You may assign the Impediment to a person, mark it as private (in which case it will be visible to b you and the assigned person only), and bind the Impediment to a User Story, Bug, or Task. 65 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide See Impediments There are several places in TargetProcess where you can view the Impediments: 1. Impediments list in the Tracking -> Impediments area 2. Impediments related to a particular assignable entity ments An assignable entity with Impediments is marked with the below, the User Story has one open Impediment. icon. For example, in the diagram Click the Impediments icon, to see a popup window with an Impediments list. You may change Impediments the Impediment state in the list or navigate to Impediment details. Private/Public Impediments Sometimes you may need to create Impediments that should be hidden from the Project team. In general, that may be not a good practice, but in real life you likely will have problems with practice, people, like “John can’t even complete tasks with average complexity. It seems he needs some training or pairing with an experienced developer”. Obviously, you don’t want to decrease John’s motivation by allowing him to see this comment. Such Impediments may be marked as on private and thus visible only to the creator. You must check the Private box during Impediment creation. 66 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Moreover, it is possible to hide (temporarily) all private Impediments. This may be required while a co-worker is sitting near you and you show him assignments in TargetProcess. You may accidentally click the wrong link allowing him to see private Impediments. Navigate to Settings, uncheck the “Show private Impediments in lists?” box, and save your changes. Now private Impediments will be invisible even to you. Reports TargetProcess provides two reports to track Impediments more effectively. The first report shows private/public Impediment distribution by priority. The graph above shows that there are two private Impediments with critical priority, which means that there are likely some problems with that team. Another graph shows the private/public Impediments dynamic by dates. 67 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide The graph above shows that two Impediments have been added today. In general, this report is useful for broader period of time; that is, to display the problems dynamic for an entire Iteration or Release. Bug Tracking Bug Tracking in TargetProcess differs from most existing Bug Tracking systems. • Bug addition simplicity: You will find only the most important fields in the Bug addition form. Almost all Bug Tracking systems have 20 or more fields, but usually only 3-5 of them really used. • User Story -> Bug relationships: You can track how many Bugs each User Story has. This helps to define the most difficult User Stories and plan the next Iteration accordingly. • Integrated ToDo list for Bugs and other Project Tasks. Bugs Workflow Basic Bug workflow will likely look like this: 1. Add Bug a. Add attachments b. Add comments 2. Assign Bug to developer 3. Change Bug status 68 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide a. Fix b. Verify and close Add Bug Choose a Project and click the Add -> Add Bug link on the left. Only the Name field is required. Severity and Priority determine Bug importance. If it is a Blocking Bug with Priority Fix ASAP, it likely should be fixed in the current Iteration. You may bind a Bug to a User Story and assign it to an Iteration or Release. Also you may assign the persons who will fix and verify the Bug. Assign Bug Bugs are assigned in the same manner as a User Story. Change Bug Status / ToDo List As soon as the Bug has been assigned, it appears in the developer’s ToDo list. The developer may change Bug status to Fixed or Invalid, add a time record for the Bug, or view Bug details. 69 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Test Case Management The Test Cases module closes the gap between Development and QA. The Test Cases and Bug Tracking modules provide comprehensive information about the actual state and quality of User Stories. Usually, QA uses MS Excel or MS Word to run manual test cases and bug tracking software to post bugs. This makes manual testing more complicated. A typical workflow: 1. 2. 3. 4. 5. QA opens test plan in Excel, reads test case QA runs application that should be tested and verifies test case QA switches to Excel and marks test case as failed, specifies build number and run date QA switches to bug tracking tool and adds a bug Finally, QA makes report in MS Word and sends it to Project/Product Manager With TargetProcess, this workflow much simpler: 1. QA opens test plan in TargetProcess, reads Test Case 2. QA runs application that should be tested and verifies Test Case 3. QA switches to TargetProcess, marks Test Case as failed, and adds a Bug No reports are required, since all data is available online in real time. No additional software like Excel or a Bug Tracking tool is needed, since TargetProcess does all the work (except the testing itself). As you can see, fewer tools and fewer steps will save time and keep QA focused on functional testing. 70 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Test Cases Concept Overview Briefly, the Test Cases module should be used this way: 1. 2. 3. 4. 5. 6. Add a Test Plan. Add Test Cases and assign them to the Test Plan. Create a Test Plan Run for a Build or Iteration. Assign the Test Plan Run to QA. Run Test Cases against a specific Build. View Test Cases stats. The diagram below shows the relationships among entities in the Test Cases module. Test Cases Library TargetProcess has a library of Test Cases. The Test Cases library contains general Test Cases that can be reused in different Projects. For example, login functionality is the same in many Projects, so you can create a Test Case for login once and put it into the library. Then you can copy your login Test Case into other Projects. You can filter Test Cases with tags. You should tag each Test Case thus creating natural Test Case categorization. Example workflow: 1. Add a Test Case called “Basic Login” and tag it with “login”. Check the “add to Test Cases library” box. 2. Click the QA link on the top menu. 3. Type “login” in the Tags filter on the left and click Filter. TargetProcess will show only Test Cases that have the tag “login”. 71 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide 4. Check the “Basic Login” Test Case. 5. Select the required Project from the drop down above the Test Cases list and click Copy. Add Test Cases Click the Add -> Test Case link on the left menu to see the Test Case addition form. Each Test Case should contain Steps/Success information and relate to a User Story. In the Steps field, describe all steps that should be performed in the Test Case. In the Success field, describe expected results. Add Test Plan and Assign Test Cases Test Plan is an entity that groups Test Cases. For example, you may create a Test Plan for smoke testing and a Test Plan for testing several User Stories. Each Test Case may be included in different Test Plans. Click the Add -> Test Plan link on the left menu to see the Test Plan addition form. Type the Test Plan name and a brief description, set the expected effort that will be required to execute Test Plan and click the Save & Assign Test Cases button. TargetProcess adds the Test Plan and displays the page for Test Case assignment. The left panel contains all unassigned Test Cases; the right panel contains Test Cases for the selected Test Plan. To add Test Cases to the Test Plan, check the boxes for the required Test Cases and click the >> button. 72 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide To assign Test Cases later, click the QA -> Test Plans link, find the required Test Plans, position your mouse over the Actions link, and select the Assign Test Cases action. Add Test Plan Run Usually you want to have historical data about Iteration/Build quality. For example, if Build 1.0.0 has 50 failed Test Cases and Build 1.0.5 has 15 failed Test Cases, it is clear that quality is improving over time. To support this concept, TargetProcess introduces the Test Plan Run entity. Simply speaking, you may run the same Test Plan over different Builds and have run results stored in TargetProcess. To add a Test Plan Run, click Test Runs -> Add. Select a Test Plan for this run, then select Release/Iteration, and Build, if applicable. Select a person who will run the Test Cases and save the Test Plan Run. In the diagram above, we’ve 73 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide created a run for Build 1.0.1 and assigned it to Teddy Bear. This Task will appear in Teddy’s ToDo list. Run Test Cases To run Test Cases, navigate to the Test Runs list and click the appear. Run link. Test Runner will Test Runner contains two areas: The current Test Case on the left and all Test Cases grouped by User Story on the right. You may 1. Mark the Test Case as Passed or Failed. 2. Add a Bug, if the Test Case failed (leaving the current page). ( 3. Click the Test Case name on the right to load this Test Case into the left area and execute it. When a Test Case has Passed, Test Runner loads the next Test Case. When all Test Cases have run, you will see the results and may rerun a specific Test Case. 74 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Test Cases Prioritization It is possible to prioritize Test Cases using drag and drop in all lists. Test Case has Priority and Rank. Rank is an order of Test Case and Test Case with higher priority has higher ranks. Navigate to QA -> Test Cases list and sort Test Cases by Rank. Drag table row and drop it to required place thus changing Test Case rank. 75 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Prioritization is available in the following places: • Test Plans list – inner list of test cases • Test Plan view – tab with test cases • Test Plan Runner Quality Stats There are several places where you can find quality stats for Release/Iteration/Build or a specific User Story. 1. User Story view page 2. Reports section in the QA area 3. Test Runs list Test Cases for User Story To see all Test Cases for a User Story, navigate to User Story view. (For example, enter a User Story ID into the search field, and TargetProcess will redirect you to the User Story view.) The Test Cases tab contains all Test Cases with their last run states. 76 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Time Tracking Time Tracking may be useful in several cases: • You want to have more precise progress information, like a Daily Progress report. • You want to compare estimated effort and actual effort. • You want to know how much time was spent for each User Story. • Your employees are paid by the hour, so you need to track time to calculate actual payments. Add Time You have two options when adding a time record: bind it to a User Story or just to a Project. Sometimes there are general tasks that are not related to a User Story. In such a case, the time will be bound only to a Project. To add a time record, select a Project and click the Add -> Add Time link on the left menu: Choose an assignment, write a small description about your activity, select a date, and enter spent and remaining time. 77 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide You can also add time for a User Story from other places: ToDo, User Stories list, User Story/Task view. Using a Time Sheet You may use a Time Sheet to add time for a whole week. Click Dashboard -> Time Sheet Note that a Time Sheet contains Tasks that are assigned to the current Iteration only. For example, if you have a Bug that is in the Back Log, the Bug will not appear in the Time Sheet. To add time for a specific day: 1. Click the cell for a Task for the required day. 2. A new window with Description, Spent, and Remaining fields will appear. 3. Fill the Description field with a description of the activity, specify spent time and estimated remaining time, and click Enter. 4. Time will be added into the database immediately. To delete time: 1. Click the cell for a Task for the required day. 2. Click the Delete link. Or navigate with the Tab key on your keyboard to the required cell and press the Delete key. 78 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Custom Activity You may add custom activities to track time on. For example, Meetings, Email handling, and so on. 1. Click the Add Custom Activity link below all assignments. 2. Specify an activity name. 3. Set the estimated time and click Save Navigation • • • Use the Prev and Next links to navigate by weeks. Use the keyboard (up, down, left, right arrows) to navigate by assignments/days. Use the Delete key to delete time entries. View Spent Time To view all time records for a Project, click the Tracking tab and the Times link. You can apply filters to Time Spent records. For example, you may display time spent by user during the last month. Also it is possible to view spent time for all projects. Click Time link at the top and the click Time List link. 79 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide People Management Allocations TargetProcess provides information about overall people allocations and workload. Click People -> Allocations. The allocations tab answers the following questions: Who is overloaded? Overloaded persons with a current allocation > 100% are highlighted red. For example, in the diagram above, Jerry Mouse is overburdened by 50%, so his allocation should be changed. Who is available for an upcoming project? You can filter people to find who is available on a specific date for a specific role/position. For example, if a Project starts on 3/14/2007 and you want to find developers available for it, you may apply the filter shown below. 80 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Who can be re-allocated to another project? Often the allocation percentage does not give enough information for decision making. For example, a person may be allocated 100% but in fact has just a few Tasks, and nobody knows what he is doing in his “spare” time. The allocations view provides detailed information about current assignments. The diagram above clearly shows the situation. Both developers have 100% allocation. Jerry Mouse is a very busy developer. He has 5 User Stories and 2 Bugs assigned, and his total current assigned effort is 150 hours. So even the best case scenario shows that he will be busy next month and can’t be re-allocated. Jim Hook has only one User Story assigned, so it is possible to re-allocate him on another Project soon, if required. What assignments does each person have? Even when one person has 3 User Stories and another person has only one, it may happen that the one User Story is much more complex and important. You may click User Stories, Bugs, and Tasks links to see exact assignments. This information may help to make the right decision in complex cases. 81 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Change Allocation You can change allocation percentages for Projects from this view. Expand a person and find the Allocation and End Date text boxes. Set the new allocation percentage and allocation end date and click the Save Changes button at the bottom of the page. People may work full-time (usually 40 hours a week) or specific weekly hours. You can set how many working hours each person has. IMPORTANT: The Project Manager may change the allocation percentage and allocation end date in the Team area of his Project. It is recommended to review allocations and provide correct information for the Project each week to have an accurate overall allocation report. Load Report The Load Report shows the total assigned effort for each person. Click People -> Load Report. If you don’t use the Points effort unit, the report will show only the Hours effort. However, if you use Points, there may be two efforts: assigned points of User Stories and Bugs, and assigned hours of tasks. The report will show Hours and Points efforts separately, since there is no conversion between Hours and Points. 82 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide 83 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Help Desk Module Help Desk module provides the complete feedback loop between customers and project development team. The Help Desk module structure shown below. Help Desk in TargetProcess consists of several sub-modules: • Help Desk Admin. Integrated into TargetProcess application. 84 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide • • • Email Integration. TargetProcess may receive emails and convert them into requests, bugs, user stories and features. Import from Excel. It is possible to import requests from Excel into TargetProcess. Help Desk Portal. External application that may be installed on your web server and integrated with your web site. Typical request workflow: 1. Customer sends request with idea via Help Desk Portal. 2. Team Lead accepts request and creates user story from request. 3. Team Lead assigns user story to next release. 4. Customer logins into Help Desk Portal and sees that request accepted and scheduled for the next release. 5. Customer sees related user story and leaves some comments. 6. Development team implements user story and Team Lead marks request as Closed. 7. Customer sees that request is implemented. Help Desk Sections There are two main concepts and sections in the TargetProcess Help Desk module: Requests and Requesters. • Request: feedback from customer with idea, question, problem or bug report. Requests may be product specific or general. • Requester: person who sends the request. 85 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide There are two requests list in TargetProcess. General requests list contains all requests, project requests list contains requests related to current project only. • • • General Requests List – Help Desk link in top menu. Project Requests List - Help Desk tab in project area. Requesters List – People -> Requesters. Requesters Management It is possible to add requesters manually, but in some cases requesters created automatically: • If you enable email integration, then requester will be created for each new email address. For example, if TargetProcess receives email from teddy@bear.com, it will create requester with teddy@bear.com email. • If new user sends request from Help Desk Portal, new requester will be created (user should fill First/Last Name, Email, Login and Password fields) To add requester manually, go to People -> Requesters and click add link. There are no required fields in this form, since you may know only email for example or only full name and phone. Requesters list contains all requests grouped by requester. 86 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Companies Management Company entity was introduced to enable Company mode in Help Desk Portal. In this mode customers from one company will be isolated from customers from another company. Thus you may use Help Desk Portal in a more flexible way and hide unnecessary information from users. Company functionality allows you to: • Add/Edit/Delete companies • Bind projects to company • Bind requester to company Companies management can be done in Admin -> Companies area. Requests Management Requests may be added from different sources: 1. Manually using Add Request action. 2. Semi-automatically from email. 3. By end users via Help Desk Portal. 87 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Add Request Manually To add request manually, click Add -> Add Request You may specify several requesters. This information may be used to prioritize requests. If a feature requested by 50 end users it is likely more important than a feature requested by 5 people. Add Request from Email Go to Inbox -> Public Inbox. Find required email, click Actions -> Create Request. 88 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide TargetProcess will automatically set Name, Description, Requesters and Request Type fields. You should set Request Type, Priority, and Product and Save request. Also it is possible to create request from a part of email message. Just select required text and Create Request action will appear. Add Request via Help Desk Portal See Help Desk Portal section below. 89 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Requests list Requests list is a core of Help Desk module. It powers requests management. You may do the following actions: • Filter and sort requests • Create user stories, features and bugs from requests • See related user stories, features and bugs in inner lists • Merge duplicated defects • Assign requests to team members • Change requests state Create Bugs, Features and User Stories from Request TargetProcess allows to create requirements from requests. Navigate to requests list, find request and click Actions -> Create Bug link. TargetProcess will show Add Bug form with prefilled Name and Description fields. Set other required bug parameters and Save new bug. Track Request-to-Requirement Relations TargetProcess tracks Requests-to-Requirements relation. It is possible to: • See related requirements in requests list and Request View • See related requests in User Story View, Bug View and Feature View 90 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide It is always known who and when requested specific functionality or report specific bug. Merge Requests Sometimes you may find or receive two equal requests. In this case it is possible to merge them. When you merge two requests the following rules applied: • • • Comments from both requests combined Attachments from both requests combined Requesters from both request combined To merge several requests: 1. Select requests in list using checkboxes 2. Click Merge link 3. Select primary request. Name, Description and other parameters will be used from primary request. Secondary requests should not have related bugs, user stories or features. Only primary request may have related requirements. 4. Click Merge button How to Use Help Desk for General Support 1. Go to Admin area and create special Support Process which will include just Planning and Help Desk practices. 2. Create separate support project “Support” and select Support Process for it. 3. Create team for Support project. The team should include all support personnel. 91 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide 4. Configure special email address for Support project. Users should send they requests to this address. 5. Configure Help Desk Portal 6. Go to Admin and configure email notifications for requests addition. Thus support team will be notified immediately when new request added into TargetProcess Usage specifics: 1. Use Requests list in Support project to manage all incoming requests. 2. Assign requests to specific people and requests will be visible in ToDo lists 3. If request targeted specific product it is possible to change Project field in request, thus assigning it to the product 4. Do not add releases and iterations 5. Do not create features and defects from requests Auto-Reply (new in v.2.10) It is possible to configure auto-reply email to requester when new request created. Navigate to Admin -> Plugins area, find Auto Reply To Requester plugin, click Add Profile link. 92 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide You may configure auto-reply for specific projects with different templates. Specify the profile name and select Project. Change email Body if required (please be careful with special template placeholders like #${Request.ID}). Click Save & Exit. If Help Desk Portal installed and configured, requester will receive a link to the created request to Help Desk Portal, otherwise link will not be included into email. If Tickets are enabled, email will contain special line to support tickets functionality. Automatically Bind Incoming Emails/Requests to the Project (new in v.2.10) Company may have many products and only one support email. People send requests to one mailbox and there should be a possibility to sort incoming emails/requests to different projects based on keyword in the email subject. You may specify such rules. Navigate to Admin -> Plugins area, find Bind Email/Request to Project plugin, click Add Profile link. Here you should specify different keyword for different projects. For example, we have two projects: Project Alpha and Project Beta. We may ask users to put Alpha or Beta into support/request email subject and configure email sorting rules as shown below: Click Save & Exit to save profile. Help Desk Portal Help Desk Portal is a separate application written on ASP.NET 2.0. It may be installed on any server and interacts with TargetProcess via Web Services API. 93 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Help Desk Portal provided with source code and you may customize it as required. Help Desk Portal provides the following functionality to end users: • Post requests/ideas/issues • Votes for requests • View requests with statuses • Discuss requests via comments threads • Attach files to requests • View related bugs and user stories Help Desk Portal Setup You may freely download Help Desk Portal from http://www.targetprocess.com/support.asp and follow Installation Guide. Help Desk Portal Modes There are 3 modes for Help Desk Portal that defines requests visibility and people access: • • Private: Customer will see only his requests. Company: Customer will see all requests posted by people from his company. In this mode each requester should be bind to Company and each product should be bind to Company as well. In this case, when adding new request, only products for related company will be available. This mode is useful for service development companies that have many customer groups. Global: Customer will see all requests without restrictions, except requests marked as Private. This mode is useful for product development companies, how have many end users. • Authentication Only registered users (Requesters) may login to Help Desk Portal. If anonymous access is enabled, then users may register with request post. If it is disabled, it is required to create Requester in TargetProcess application. Go to Admin -> General Settings and find Help Desk section. There are two options: • When you add requester manually TargetProcess may send notification to requester with access parameters to Help Desk Portal. • When requester added into TargetProcess automatically (from retrieved email for example), TargetProcess may send notification as well. It is required to enable email notifications and the first option if you want to allow manually added requesters to post requests via Help Desk Portal. 94 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Registration Requests may be added by registered users. User should lick Register link and fill out registration form: First Name and Last Name, email, password. If Help Desk Portal configured in Company mode, all new registered users should be approved by administrator. Administrator should select a company for each new requester, otherwise they will be unable to login. If Help Desk Portal configured in Private or Global mode, requesters may login right after the registration. Add Request It is required to select exact product when adding new request. Since there are 3 modes for Help Desk Portal, products visibility is different: • • Global or Private: User will see all projects that have Product checkbox marked. Company: User will see all projects that have Product checkbox marked and relates to the user’s company. You may mark Program or Project as a product. Go to Projects list, click Edit for required project, find Product checkbox, mark it and Save changes. 95 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Requests Lists Help Desk Portal users may see all submitted requests in My Requests area and All Requests in All Requests area. It is possible to sort requests, edit them and view details. All Requests area contains different requests based on Help Desk Portal Mode: • • • Private: There is no All Requests list at all in this mode Company: The list contains all requests posted by users from the same company as logged user Global: The list contains all requests from all products. 96 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Votes You may vote for requests. Each vote is a person who requested the feature. For example, if request has 4 votes it means that 4 customers or leads requested this feature. When you add your vote, the request becomes visible in My Requests list. Request Details Navigate to My Requests and click on request name link. Request view area shows all related information. User may add comments and attachments. 97 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Email Integration Starting from version 2.5, TargetProcess may retrieve emails from specified mailbox and do some actions with the emails: • Create requests from emails • Bind emails to user stories, features, bugs and other entities There are two types of inboxes: Project Inbox and Personal Inbox. • Project inbox should be used for support or general project communication. • Personal inbox should be used for your own needs. It contains internal messages (sent by TargetProcess users inside the system) and emails sent by other people. Project Inbox Configuration Go to Projects list and click Edit for required project. Find Inbound Email Integration section and mark Enabled checkbox. Specify Mail Server, Port, Login and Password and push Check connection button. TargetProcess will show success message if email connection works fine. TargetProcess may check emails automatically each 10 minutes. To enable automatic email check corresponding option. Also TargetProcess may create requests from all incoming emails. 98 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Usage Click Inbox link in the top right corner and then click Public Inbox. Click Check Email link to receive all emails from specified email account. TargetProcess will show how many messages will be retrieved and start the process in a separate thread. You may click Public Inbox link to check progress. It is a simple email client. You may read emails, delete them, and mark them as read or unread. Two specific business actions are Create Request from email and Bind email to entity (user story, bug, feature, etc.). Sending Emails Click Compose Message link. You may send emails to any email address. Personal Inbox Personal Inbox resembles Public Inbox. It has settings in different place however. Click Settings link in top menu on the right and then click Email Settings tab. Specify required parameters and save changes. 99 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Then go to Inbox -> My Inbox and click Check Mail link. My Inbox contains internal messages and emails. • Internal messages created by TargetProcess system for events like task assignment and task completion. Also TargetProcess users may send internal messages. • Emails are receiving from configured mail box. Bind Emails to Entities TargetProcess may bind emails to entities like Feature, User Story, Bug, Iteration and other. Bind Email to Entity Action Navigate to Inbox, click Actions link and click Bind To… link. Popup window with entities list will appear. You may filter entities by Name or sort them by ID, Type and Name. When you find the required entity click on entity name and email will be attached to it. Emails in Entity View Entity View contains all attached emails. Navigate to entity view and find Messages section. 100 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide You may view attached emails and unbind them from entity. Support Tickets (new in v.2.10) It is possible to configure tickets support in TargetProcess. How tickets work? The simplest flow: 1. Person sends email to TargetProcess support 2. TargetProcess automatically create request from this email 3. TargetProcess admin read the request, add a comment and send email notification to the person 4. Person receives the email with admin reply 5. Person reply to email 6. TargetProcess receives the email and create a comment from this email to the request. Thus person may interact with support department via emails, while support department communicates via TargetProcess only. Several steps required to setup tickets. 101 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Enable Email Notifications Navigate to Admin and find Email Settings option. Configure SMTP Server to allow TargetProcess send emails. Enable Inbound Email Integration Go to projects list, click Edit for the project and setup inbound email for the project. Make sure that Check email and Create Requests automatically options marked. Reports There are three types of reports in TargetProcess: 102 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide 1. Custom Reports 2. Combined reports for selected Projects 3. Reports inside a specific Project Custom Reports To generate custom report click Reports link on the top and click Create New Report button. Report Wizard has the following steps: 1. 2. 3. 4. 5. 6. 7. 8. Select Report Type Select Columns Set Filters Configure Summary Columns Change Column Order & Add Sorting Group Results By Field Add Chart Save and Run Report Custom Fields are fully supported by Report Engine. You may add them as columns, filter by custom fields and group by custom fields. On the first step it is required to select entity for report. For example, you may create report for user stories, bugs, features, time and so on. 103 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Internet Explorer.lnk On second step you may specify report columns. It is possible to have associated entities columns as well. For example, if you creating report for user stories you may include iteration name column. 104 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide On third step you may specify filters. For example, for user stories report you may select open user stories assigned to specific person, that have zero spent time. It is required to select property, operator and value. 105 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide On fourth step you may configure summary columns. For example, request has a collection of Comments, so you may add columns like count of all comments in a user story and latest comment date. To add columns like Sum of Spent time by Developer do the following: 1. 2. 3. 4. Specify column name (# Developer Spent Time) Select Time collection Select Sum operator Click Filter link and specify filter as shown on picture below Finally you save the report for future use. From final results you may do the following actions: 1. 2. 3. 4. 5. Export results to CSV file (click export to excel link) Navigate to entity in the report (click on id link) Group entities by any column Sort by any column Edit report 106 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Combined Reports Click the Reports link in the top menu to see the combined reports interface. The left side contains all Projects, and the right side offers three possible combined reports: Project Progress Report, Quality Assurance Report, and People Report. Each report may include several subreports. To generate a combined report 1. Check the required project(s). 2. Select a combined report from the drop down list. 3. Check/uncheck sub-reports as needed. 4. Click the Generate button. In the generated report that opens in a new window, you may hide different sub-reports on the fly. 107 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide These reports have been modified for printing. Click File -> Print Preview in your Web browser > to preview the printed version. Reports in Specific Project You can see a list of all Project reports, organized by type, in the Reports tab. 108 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Planning Reports Burn Down Charts The most important high level project progress indicator is a Burn Down chart. It shows how User Stories were implemented during a Release. A Project Manager could compare team performance among Iterations and get general information about Project status. Let’s check the following data: Iteration #3 #4 #5 #6 User Stories done Effort 80h 100h 60h 40h According to this Burn Down Chart, it is clear that something has gone wrong since Iteration #5. It is up to the Project Manager to identify specific problems; the chart just indicates that there are some troubles to be addressed and resolved. The chart below is for the current Release. Yellow bars show effort needed to complete this Iteration; green bars show done effort for this day; and blue bars show estimated forecasted effort. 109 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide 1. Ideal line shows how much effort team should accept to complete release on time 2. Done vs. Remaining effort 3. Forecasted effort This chart answers two important questions: 1. When will the Release be completed? 2. Are we making good progress? As you can see, based on previous progress, we need two Iterations to complete this Release. Also we see that progress is slowing down during the 3 latest Iterations. There must be reasons for that. 110 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide User Stories Count by States Burn Down The User Stories Count by States Burn Down Report shows User Stories dynamics. It is particularly interesting if you have many states for User Stories, such as open, in progress, and accepted. In this case, the chart shows how User Stories implementation is going. 111 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Quality Assurance Reports Bugs Distribution by Severity This chart helps to define overall Project quality. If there are many open Blocking and Critical Bugs, action should be taken to improve quality. For example, introduce Test-Driven Development, try Pair programming, or another tactic. Concrete actions are up to the Project Manager; this chart helps to define when to apply these actions. 112 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Bugs Dynamic Bugs Dynamic report shows how many bugs where opened, fixed or closed each day or week. For example, 5 Bugs were Opened, 6 were Fixed and 3 were Closed. The report also shows how many new Bugs found each day, so it is possible to predict when new bugs ratio will be small enough to make a release. Bugs Progress The Bugs Progress Chart shows open/closed Bugs dynamics. It answers the following questions: • • Is the Bug fixing dynamic positive or negative? How many Bugs have been added each day? The chart below shows bugs progress for many Iterations. It is clearly visible that project has more and more open bugs in the end of each Iteration and quality probably suffers. 113 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide 114 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Bugs Count by States Burn Down The Bugs Count by States Burn Down Report shows Bugs dynamics. For example, the chart below shows that the Bugs dynamic is not positive. There may be Bugs that are not fixed or many new Bugs may have appeared. The first assumption is more likely, since the Bugs in Fixed state value does not change. 115 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Test Cases Runs Reports There are two reports in the QA -> Reports section: Test Cases Runs by Release/Iteration/Build and Test Cases by User Story. Test Cases Runs by Release/Iteration/Build The Test Cases Runs by Release/Iteration/Build report shows overall quality state over Releases/Iterations/Builds. For example, the chart below shows that 20 test cases failed in Beta Version release and 28 test cases where not run at all. 116 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Test Cases by User Story The Test Cases by User Story Report shows the quality of specific User Stories. You can see the quality of all User Stories in the current Release or current Iteration. For example, the chart below shows that only one User Story has failed test cases, while two other User Stories have been completed and tested. Time Tracking Reports Time Spent Summary The Time by Person report displays total spent time for all users in a team for a selected period of time. 117 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Printable Reports Several lists (Features, Test Cases, User Stories, Bugs) have the Print action. Navigate to a User Stories list and click the Printable View link to a see list of User Stories, related Bugs, Test Cases, Tasks and other info. You may hide/show areas using checkboxes on the right. You can also print selected User Stories. Select the required User Stories and click the Printable View link and only the selected User Stories will be included in the report. 118 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Source Control Integration TargetProcess Source Control integration helps avoid some repetitious actions for developers. For example, when a developer fixes a Bug, he usually does the following: 1. 2. 3. 4. 5. Commit change into source control system with comment that includes Bug ID Go to TargetProcess and find fixed Bug Add the same comment to the Bug Change Bug state to Fixed Optionally, add spent time on Bug With subversion integration, all these actions can be replaced by one: 1. Commit change into source control system with proper comment that includes Bug ID TargetProcess will do the rest automatically. Additional options include viewing files associated with the Bug as well as viewing differences. Setup Subversion Integration IMPORTANT: User logins in TargetProcess and Subversion should be the same. For example, if Teddy Bear uses the login ‘ted’ in TargetProcess, he should have the login ‘ted’ for the Subversion repositories as well. Otherwise comments and times will not be added automatically on commit. 1. Install Subversion on the Server Download the latest Subversion client from http://subversion.tigris.org/project_packages.html and install it on the server where TargetProcess installed. Installation does not require any additional knowledge. Just click Next when prompted. 2. Configure Subversion Parameters in TargetProcess Go to Admin -> General Settings area and set the following parameters: • Path to svn.exe – path to installed Subversion client. Usually it is c:\program files\Subversion\bin\svn.exe • Connection Period (sec) – defines how often TargetProcess will retrieve changes from the repository. This value is in seconds, so 3600 means that TargetProcess will check the repository each hour. It is recommended to set value to no less than 600 (10 minutes). Otherwise it may affect performance. 3. Configure Project There is a Source Control section on the Project Add/Edit page. 119 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide 1. Create a new Project (or edit an existing one). 2. Select a Process which contains the Source Control Integration practice (Read the Project & Process section to learn more about selecting practices). 3. Select a type of Source Control in the Source Control Integration section (Only Subversion will now be available) 4. You will see the fields shown below: • • • Path to Project: contains full SVN (Subversion) path to your Project in the repository Login and Password: SVN user login and password. Login should be the same in TargetProcess and Subversion Start Revision: On first start, TargetProcess will retrieve all revisions and create records in its database. This may be a very time-consuming process. Often you don’t want to import all revisions, but just start from a specific revision. For example, if you have 1000 revisions, the process may take several hours. In this case, it would be better to set revision 900 as the starting point. Click the Check connection button to ensure that all settings are correct and TargetProcess can access the repository. Backward Integration (View Entities from Subversion Client) You can add backward integration in some Subversion clients (for example, TortoiseSVN). This allows you to open a specific Bug or User Story with one click from within Subversion. The idea behind this is that SVN clients can create URL which links to TargetProcess dynamically. There is a page http://TargetProcessServer/View.aspx?id=SOME_ID where SOME_ID is any valid ID (Bug or User Story, for example). To enable integration with TortoiseSVN, you must set the following properties in the Project folder (right mouse button click -> Properties -> Subversion Tab -> Properties): bugtraq:logregex #(\d+) 120 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide bugtraq:url http://TargetProcessServer/View.aspx?ID=%BUGID% The first property extracts an entity ID from a log message, and the second provides the URL. When you apply these properties, you may click Show Log to see the commit message. All IDs will have links to the TargetPocess entity view page. Setup Source Safe Integration IMPORTANT: User logins in TargetProcess and Source Safe should be the same. For example, if Teddy Bear uses the login ‘ted’ in TargetProcess, he should have the login ‘ted’ for the Source Safe as well. Otherwise comments and times will not be added automatically on commit. 121 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide 1. Install Source Safe on the Server It is need to install Source Safe on the server because TargetProcess use Source Safe components for integration. 2. Configure Source Safe Parameters in TargetProcess Go to Admin -> General Settings area and set the following parameters: • Connection Period (sec) – defines how often TargetProcess will retrieve changes from the Source Safe. This value is in seconds, so 3600 means that TargetProcess will check the repository each hour. It is recommended to set value to no less than 600 (10 minutes). Otherwise it may affect performance. 3. Configure Project There is a Source Control section on the Project Add/Edit page. 5. Create a new Project (or edit an existing one). 6. Select a Process which contains the Source Control Integration practice (Read the Project & Process section to learn more about selecting practices). 7. Select “SourceSafe” in the Source Control Integration section 8. You will see the fields shown below: • • Path to Project: contains full path to srcsafe.ini file and to your Project in the Source Safe. Login and Password: Source Safe user login and password. Login should be the same in TargetProcess and Source Safe Click the Check connection button to ensure that all settings are correct and TargetProcess can access the repository. Setup Perforce Integration IMPORTANT: User logins in TargetProcess and Perforce should be the same. For example, if Teddy Bear uses the login ‘ted’ in TargetProcess, he should have the login ‘ted’ for the Perforce as well. Otherwise comments and times will not be added automatically on commit. 122 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide 1. Configure Perforce Parameters in TargetProcess Go to Admin -> General Settings area and set the following parameters: • Connection Period (sec) – defines how often TargetProcess will retrieve changes from the Perforce. This value is in seconds, so 3600 means that TargetProcess will check the repository each hour. It is recommended to set value to no less than 600 (10 minutes). Otherwise it may affect performance. 2. Configure Project There is a Source Control section on the Project Add/Edit page. 1. Create a new Project (or edit an existing one). 2. Select a Process which contains the Source Control Integration practice (Read the Project & Process section to learn more about selecting practices). 3. Select “Perforce” in the Source Control Integration section 4. You will see the fields shown below: • • Path to Project: contains full path Perforce server and to your Project in the Perforce. Login and Password: Perforce user login and password. Login should be the same in TargetProcess and Perforce Click the Check connection button to ensure that all settings are correct and TargetProcess can access the repository. Bind Committed Files to Bugs TargetProcess connects to the Subversion server periodically to retrieve log messages for each revision that was committed. A log message must be written with special keywords to be bound to an existing entity. In general, every line of a log message may contain four specific parts that TargetProcess will use: ID, new state, time spent, and a comment. Line pattern values (inside [] brackets) should be replaced by your content: 123 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide “#[ID] state:[NEW STATE] time:[h.m:h.m] comments:[ANY COMMENT]” • • • #[ID] is any valid User Story or ID (e.g. #302). All committed files will be bound to this Bug. state:[NEW STATE] is a valid state for a Bug (e.g. state:fixed, state:open, state:closed). time:[h:h] is valid time spent and time remaining in hours (e.g. time:2, time:3.5, time:5.5:8). The last example means 5 hours and 30 minutes spent and 8 hours left remaining. comments:[ANY COMMENT] is any comment you want to attach to the entity • Several examples of log messages (the entity with ID 745 is a Bug): Log message #745 Bug #745 was closed “Hurrah! #745 is state:fixed time:2 comments: Added checking of result when creating a file” Results All files committed with this revision will be bound to the Bug with ID 745. All files committed with this revision will be bound to the Bug with ID 745. • All committed files will be bound to the Bug 745 • The Bug 745 will be marked as fixed • New time record with 2 spent hours will be created and associated with Bug 745. • New comment “Added checking of result when creating a file” will be added to the Bug 745. All committed files will be bound to Bugs 745, 746 and 747 and these Bugs will be marked as fixed. “Fixed bugs #745 #746 #747 state:fixed” View Files and Revision Differences The Source tab inside the Bug view contains all revisions and files that were associated with the Bug during commits. You may do the following: • • View file: click the file name to retrieve it for the specified revision View differences between the current revision and previous revision: click the Diff link for the required file and revision 124 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Tags (new in v.2.10) TargetProcess supports information categorization via Tags. It is possible to specify tags for all entities in the system. Tag Entities You may specify tags when adding/editing entity. Click Add -> User Story link and find Tags section in the bottom of the form. Click Tags link to expand the section. You may type tags into the field or select tags from the cloud. In the cloud you see 100 first tags based on sort settings. You may sort tags by rank (most used tags have higher rank) and alphabetically. Also you may filter tags in the cloud by typing first letters into the filter field. You may add tags to several entities at once using batch action. Go to list (for example, User Stories list), select several user stories and click More Actions link. 125 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Type several tags space separated and push Add button. Tags will be added to selected entities. Search by Tag There are two ways to find entities by tag. Type tag: tagname in the search box The search above will find all entities that have bugzilla tag. The other way is to use filters in lists: Manage Tags You may add, delete and rename tags in a project. Click Admin in project area and navigate to Tags section. Add Tags Type new tags space separated into Add Tags text field. If you want to use phrases as tags it is required to enclose them into “” (for example, “complex tag”). Added tags will appear in current project. Delete Tags Type tags or select tags from the cloud in Delete Tags section. Push Delete button. Selected tags will be deleted from current project and from all entities in current project. 126 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Rename Tags You may rename several tags into one new tag. It is the same as merging several tags into one. Select one or several tags in Old Tags field, type tag in New Tag field and push Rename button. Manage Bundles Bundles are a way to group related tags. It is quite powerful mechanism for advanced categorization. For example, you may create bundles like Teams, Modules, Components, Browsers, OS, Technical, etc. Tag may belong to several bundles in general. In TargetProcess there are two types of bundles: • Exclusive. If you create bundle and mark Exclusive checkbox, entity may have only one tag from this bundle. For example, you create bundle Teams with tags Team A and Team B. You want to assign some user stories to Team A and to Team B. It will be not possible to assign the same user story to both teams. • Non-Exclusive. Entity may have many tags from such bundle. For example, you may create Technical bundle with tags architecture, database, and business logic. You may create user story that will have all these tags. 127 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide 1. Add bundle. 2. Bundles list. 3. Tags in bundle. You may add tags to bundle or remove tags from bundle. Add Bundle Click add link near Bundles title. Specify bundle name and mark checkbox Exclusive if you want to create exclusive bundle (IMPORTANT: It is not possible to change bundle type later, so decide wisely!). Push Save button to add the bundle. Add/Remove Tags Click on bundle name in bundles list, tags area will be filled with tags that are already in the bundle. You may click to tags in cloud to add/remove them or just type tags in the tags field. Push Save button to save changes. Tags Board Tags Board is a powerful way to categorize entities. Typical example is to create Modules bundle and tags in the Modules bundle like UI, Authentication, Reporting, etc. The purpose of Tags Board provide a flexible way to tag existing entities. 128 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide 1. 2. 3. 4. 5. 6. Bundle selector. Allows to select required bundle Entities filter area. Entities sorting. Entities backlog Entities assigned to tag Tags in the current bundle Left area contains entities backlog – all entities that have no tags from the current bundle. On the screenshot above backlog contains entities that do not have tags from Modules bundle. For example, you want to set modules for existing entities. You’ve created Modules bundle and required tags in the bundle. The flow will be: 1. Navigate to Tags Board 2. Select Modules bundle in the drop down. Right area will be filled with all tags from Modules bundle. 3. Click Filter Entities link, mark User Stories and Requests entities and click Filter link. As a result backlog will be filled with user stories and requests entities. 4. Drag user story from the backlog and drop it to required tag in the right area. Thus you set the tag to entity. Entity removed from backlog and tagged. 129 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Individual entity box has some additional features like color coding and tooltip. • Background color represents entity priority (green background – high priority). • Right side border represents entity type (blue – user story, red – bug, etc.). The colors are the same as for entity icons. • Tooltip shows full entity name, effort and priority for assignable entities like Features, User Story, Bug, Task. There are two modes in the Tags Board based on Bundle nature. • Entity may have only one tag from exclusive bundle. If you drag entity from Tag A and drop it to Tag B the entity will have Tag B only. • Entity may have several tags from non-exclusive bundle. If you drag entity from Tag A and drop it to Tag B the entity will have both tags: Tag A and Tag B. Import/Export TargetProcess provides Import/Export from/to CSV format for Bugs, Features, User Stories and Test Cases. Import from CSV TargetProcess imports entities in the current Project only. Select a Project and click Admin -> Import to start the import wizard. 130 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Select the required entity type (Feature, User Story, Bug or Test Case), browse for a *.csv file and specify the number of columns to be imported. You may wish to set the number slightly higher than the actual column count. Then select the column delimiter and click Next. In the next step, you must specify a mapping between CSV file columns and entity properties. For example, a User Story entity may have an “Effort” property while in the CSV file you may have an “Estimated Effort” column. You may import custom fields as well, there is no difference between native entity field and custom field for the Import wizard. TargetProcess tries to define the mapping by itself, but in complex cases it may fail. When you finish mapping columns, click Next and TargetProcess will start importing. The last step shows import results and a complete import log. Export into CSV Navigate to a User Stories list and filter User Stories to get the required list. Click the Export link and TargetProcess will generate a file for saving. You may either open it via your Web browser or save it on disk. If you have any questions about TargetProcess, send an email to info@targetprocess.com 131 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Web site http://www.targetprocess.com Support forum http://support.targetprocess.com 132 © 2004-2008 TargetProcess, Inc. www.targetprocess.com TargetProcess v.2.10 — User Guide Appendix A. Resources Agile Estimating and Planning By Mike Cohn (strongly recommended) http://www.mountaingoatsoftware.com/book/view/1 Wikipedia http://en.wikipedia.org/wiki/Incremental_and_iterative_development Planning Extreme Programming by Kent Beck, Martin Fowler http://www.amazon.com/exec/obidos/tg/detail/-/0201710919/002-5598678-3693648 Agile Software Development by Alistair Cockburn http://www.amazon.com/exec/obidos/tg/detail/-/0201699699/qid=1088001735/sr=13/ref=sr_1_3/103-5739680-9585429 Agile Project Management with Scrum by Ken Schwaber http://www.amazon.com/Agile-Project-Management-MicrosoftProfessional/dp/073561993X/ref=pd_bbs_sr_1?ie=UTF8&a mp;s=books&qid=1215592679&a mp;amp;amp;amp;sr=8-1 The Art of Agile Development by James Shore and Shane Warden http://jamesshore.com/Agile-Book/ 133 © 2004-2008 TargetProcess, Inc. www.targetprocess.com