CollabNet TeamForge 5.3 Evaluator s Guide

Transcription

1 CollabNet TeamForge 5.3 Evaluator s Guide Thank you for evaluating CollabNet TeamForge 5.3. This Evaluator s Guide will help you experience the key features of CollabNet TeamForge by walking you through common usage scenarios based on sample projects and users already present in your VMware download. If you have any questions or comments about this guide, or installing and configuring the trial, please feel free to post in our feedback forum. You can also look here for more community resources. Required Setup This guide assumes you have already downloaded and installed the TeamForge VMware trial. Visit the CollabNet TeamForge "Try It" page to download the trial software. Refer to Install CollabNet TeamForge on a Virtual Machine for instructions about how to install and configure the trial download. Each of the sections below assumes you have completed the previous sections. Later sections may refer to artifacts created in earlier sections, and also provide less detailed instructions for common steps, such as logging in and navigating within TeamForge. Sample Users To simplify the evaluation, this guide only uses six users: TeamForge Administrator, Default site administrator (User Name: admin, Password: admin) Sally, Default Project Manager (User Name: project_manager, Password: sample) Alex, Default Product Manager (User Name: product_manager, Password: sample) Eric, Default Product Executive (User Name: product_executive, Password: sample) Nancy, Default Product Developer (User Name: product_developer, Password: sample) Terry, Default Product Tester (User Name: product_tester, Password: sample) In the following examples, the project manager usually performs these duties. Once you have completed the exercises in this guide, feel free to delete all of the sample users. (See the Cleanup section at the end of this guide for details.) Contents Set up your evaluation environment... 2 Section 1: Follow a user story through the Agile lifecycle... 7 Section 2: Manage your project workspace Section 3: Manage your TeamForge site Clean-up: Delete Sample Users Other cool TeamForge stuff Page 1 of 41

2 Set up your evaluation environment In this section, you will setup your CollabNet TeamForge environment, including: Logging in and setting the administrative password Changing addresses for sample users, and adding a new user Install Tortoise SVN for committing code to the source code repository Log into TeamForge as the site admin user: User Name: admin Password: admin Since this is your first time logging in, you may be asked to change your password. For security reasons, it is a good idea to change it now. However, you can keep the same password by typing admin in both the New Password and Confirm New Password fields. Click the Admin tab at the top of the page. Under Site Administration, click the Users icon. Click the link for Sally, the Project Manager. Page 2 of 41

3 Click the Edit button. Replace the address with the address you want to associate with the user who will be playing the project manager role for your evaluation. Notifications to the project manager are sent to this account, and messages sent to TeamForge from this account are identified as coming from the project manager user. Choose English for the locale, if not already set. Click the Update button. Return to the User Admin page by pressing the Back button on your browser three times. Click the link for Alex. Click Edit and replace with the address you want to associate with the user who will be playing the product manager role for your evaluation. Make sure this is a different address than the one you entered for the project manager user. Click the Update button. Page 3 of 41

4 Repeat this process to edit the addresses for Terry, Nancy, and Eric. Make sure you use a different address for each user. Next, create a sample developer user. Return to the User Admin page and click the Create button in the lower right. Enter brokerage_dev as the User Name, sample as the password and Brokerage Developer as the Full name, and enter an address for this user. Click the Create button in the lower right. Click LOGOUT at the upper right of the page to log out as the site admin user. The next couple of steps assume that you will use Tortoise SVN for Subversion development. However, other clients like Subclipse or AnkhSVN, or even command line, can be used for Subversion development. If you would like to use a tool other than Tortoise SVN you can skip these steps. Visit the Tortoise SVN downloads page, and download the current version. Tortoise SVN is available for 32 bit and 64 bit Operating Systems. TortoiseSVN comes with an easy to use installer. Double-click the installer file and follow the steps. The installer will take care of the rest. Page 4 of 41

5 Next, you are going to check out the source code for the repository. But before you do that, you will need to find out the URL of the repository. You can find this out by clicking the Source Code tool button at the top of the TeamForge site. You will see the Brokerage System Repository. Copy the URL info for the next steps. The URL is the last part of the Checkout Command highlighted in the screenshot at right. It is also a good idea to monitor this repository for any changes; you can do this by selecting the radio for Brokerage System, and then click the Monitor button. After the installer completes, go to the folder where you want to put the source code for the Brokerage System project. Right-click in this folder, and click SVN Checkout from the menu. Enter the URL of the repository. Then click OK. Page 5 of 41

6 Enter your Username and Password. This is the same user name and password for logging in to TeamForge. Click OK. After the download completes, click OK. The folders for branches, tags, and trunk, with check marks, correspond to the directories in the source code for the Brokerage System project. The check mark indicates that a freshly checked out working copy is available, and the setup process for Tortoise SVN is complete. Page 6 of 41

7 Section 1: Follow a user story through the Agile lifecycle In this section, you will learn how CollabNet TeamForge can track a user story through its lifecycle. You will: Assign a user story artifact to a new iteration. Add a mockup and associate it to the user story. Associate the user story to an existing test artifact. Break the story into child tasks with estimates. Update task effort for the child tasks. Observe metric changes for the release Commit code and associate commit with user story. Part 1: Create a new iteration 1a. Log into TeamForge as the project manager, Sally: User Name: project_manager Password: sample In this exercise you will create a new iteration for a release. An iteration typically will last anywhere from 1-4 weeks, and is a good way to break up larger deliverables into manageable smaller time boxes. 1b. Go to your project by mousing over Projects, then My Projects, and finally click Brokerage System (Sample) 1c. Go to the Tracker tool by clicking Tracker. Page 7 of 41

8 1d. Select Release 1 from the Planning Folders section in the left panel. Then click New. 1e. In the Create Planning Folder dialog, enter Iteration 3 for the Planning Folder Name, and optionally enter a description. To show a burndown chart for the iteration, enter a start and end date. Click Save. Part 2: Assign a user story to an iteration 2a. Check the box next to artf1093, then click Plan For In this exercise you will learn how to assign a user story to an iteration. There should be a handful of stories that you will work on during the course of the iteration. This process is also referred to as populating the iteration backlog. The project team should get together and agree on the user stories that will fit in the iteration. Page 8 of 41

9 2b. In the Plan For dialog, expand the node for Release 1 by clicking on the + icon. This will display all of the iterations in Release 1, including the one you created. Click your new Iteration 3 link. Then click the Update button at the bottom of the dialog. Now artf1093 is planned for Iteration 3. Part 3: Associate a document with a user story 3a. Click the link for artf1093 to go to the detailed view of the artifact. In this exercise, you will learn to link other documents that already exist in TeamForge to a user story. User stories often have documents such as user requests and mockups that you need to refer to while working on a user story, and creating an association is an easy way for other members on your team to find related information. 3b. In the artifact detail view, change the Status to In Development. Then click the Associations tab. 3c. On the Associations tab, click the Add button at the bottom of the screen. Page 9 of 41

10 Note: To find the document that you want to add, click the Documents link in the project toolbar, then click the link for Mockups & Flows in the Document Folders section, and finally click the link for OrderScreen. The Document ID is located in the Document Details section. 3d. In the Add Associations Wizard popup, enter doc1006 in the input box next to Enter Item ID. Then click Next > at the bottom of the dialog. doc1006 3e. Now you can see that you are about to associate artf1093 with doc1006: Order Screen. Add an Association Comment, such as This is a mockup for the order screen. Then click the Finish and Add Another button at the bottom of the dialog. The document is now associated with the user story, and you are ready to add another association. Part 4: Associate a test artifact with a user story Note: To find the artifact that you want to add, go to the Tests Tracker, and click the link for Test single step process for mutual fund orders. In this exercise, you will learn how to link a test script with a user story. It is essential for developers and testers that there is a connection between the user story the developer is implementing, and the test script used for testing the implementation. 4a. In the Add Associations Wizard popup, enter artf1066 in the input box next to Enter Item ID. Then click Next > at the bottom of the dialog. artf1066 Page 10 of 41

11 4b. Now you can see that you are about to associate artf1093 with artf1066: Test single step process for mutual fund orders. Optionally add an Association Comment, such as This is the test script that should be used for testing the Mutual Order Screen. Then click the Finish button at the bottom of the dialog. The test artifact is now associated with the user story. Part 5: Create a child task artifact for a user story 5a. From your current view, click the Dependencies tab. In this exercise, you will learn how to create a task for a user story. Tasks are the discreet development activities necessary to implement the user scenario described in a user story. Tasks can be independently estimated, assigned, and completed, allowing for parallelism. 5b. Click the arrow icon on the Create Child In drop-down button, then click Tasks from the menu. 5c. Fill in the fields for the newly created child artifact. Change the Status to In Progress. Enter values for Estimated Effort and Remaining Effort. Also change the Assigned To drop-down value to Nancy, the developer on your project. After you have filled in all of the pertinent data, click the Save button at the bottom right of the screen. 5d. You now see the artifact that you just created as a child of artf1093. Create another child task by clicking the Create Child in drop-down button, and filling out the artifact information again. Page 11 of 41

12 5e. You now see both of the artifacts that you created as children of artf1093. Observe that the estimated and remaining effort for each task also appears. 5f. Click the Status / Comments tab. 5g. Now you are going to make the effort of the child tasks be summed up as part of the story effort. Click the Sum effort from children checkbox. 5f. The effort displaying now is the sum of the effort of the children tasks that you just created. Now return to the artifact explorer view by clicking the Update button. Part 6: Update effort for tasks 6a. Go to the Iteration 3 Planning Folder by clicking Iteration 3 in the Planning Folders section of the left panel. In this exercise, you will learn how to update effort for tasks. It is essential that all of the project team members update their estimated and remaining effort for their assigned tasks (and user stories if they are not summed from tasks) on a daily basis. These updates are reflected in the burndown for the iteration-specific planning folder and any planning folders that contain it. 6b. Go to the first child task that you created by clicking the link for the task s artifact id. 6c. Update the fields for Remaining Effort and Actual Effort. Then click the Update button. Page 12 of 41

13 6d. Repeat the process for the second task by clicking the link for the task s artifact id. 6e. Update the fields for Remaining Effort and Actual Effort. This time, also update the field for Estimated Effort to indicate a change in the original estimate. Next, click the Update button. 6f. Observe that the effort fields for the tasks that you updated are reflected in the Iteration 3 planning folder view. The parent User Story fields have changed too, based on your changes to the child tasks. Part 7: Observe metrics for a release 7a. Go to the planning folder for Release 1, by clicking the Release 1 link in the Planning Folders section in the left panel. In this exercise, you will learn about metrics that are available for every planning folder. The metrics available give you a diagnostic view of how healthy your release is, including metrics for burndown, open artifacts by priority, and open vs. closed artifacts 7b. Observe the charts for Release 1. Click any chart for details. 7c. Click the Burndown chart on the left. A popup displays a detailed view of the smaller chart. Hover over the graph to see further detail, for a particular day. The stacked bar chart represents Remaining Effort by priority. The green line represents Estimated Effort. The blue line represents Velocity Trend, which is calculated by the progress of Remaining Effort over the course of Release 1. Page 13 of 41

14 Click Close to close the popup. 7c. Click the Open by priority chart in the middle. A popup displays a detailed view of the chart, with counts of artifacts open, broken down by priority. Click Close to close the popup. 7d. Click the Open Vs Closed chart on the right. A popup displays a detailed view of the smaller chart, with counts of total artifacts open and closed. Click Close to close the popup. Part 8: Commit code and associate the commit with a user story 8a. From your current Release 1 planning folder view, click artf1093 from the list of artifacts below. This is the user story that you will commit against. 8b. In your local file system, create a file called orderscreen.htm in /trunk/src. The file will show up with a? icon, indicating that the file is not versioned. In this exercise, you will learn how to commit code and associate the commit with the user story. From the project manager s perspective, you can find out what has been checked in for the story, and from the developer s and tester s perspective, you can look at the revisions, and see what necessitated the code change. Page 14 of 41

15 8c. Right-click orderscreen.htm and click TortoiseSVN, then Add. 8d. The icon changes to a +, indicating that orderscreen.htm has been scheduled to be added to version control. Right-click on orderscreen.htm and click SVN Commit. 8e. Enter a message, including the artifact id, encapsulated by square brackets [artf1093]. This ensures that the artifact is associated with the commit. After entering a message, click OK. Page 15 of 41

16 8f. A commit dialog tracks the progress of your file being added to version control. After it finishes, click OK. 8g. Observe that the icon for orderscreen.htm has changed to a check mark, indicating that the file has been checked in, and is current. 8f. Now go back to your web browser, and click the Associations tab for artf g. You will now see the commit that you just made. Click the link next to the commit id, to see the commit detail. 8h. In the commit detail, you will see the commit message you entered, with a link back to artf1093. To see a detail of the file that you commited, click the trunk/src/orderscreen.htm link in the SCM Files tab 8i. You will now see the revisions of the file you committed. Here you can select versions for diff ing, and make annotations. Since this is the first version of the file, just look at the file by clicking the view link for Revision 2. Page 16 of 41

17 8j. Observe that the file that you checked in is the same as the one that appears in this view. Part 9: Close child tasks and update status of user story 9a. Go to the Iteration 3 planning folder, by clicking Tracker, then click Iteration 3 from the Planning Folders section in the left panel. In this exercise, you will learn how to close tasks, and change the status of the user story. During the course of the iteration, it is important to close tasks as they are finished so that your metrics are up-to-date. Also, it s important to change the status of the user story when all of the tasks have been completed, so that you can communicate to your project team that the story is ready for User Acceptance testing, or ready for testing. 9b. Click the link for the first child task artifact. 9c. In the artifact detail, change the Status field to Completed, and update the Remaining Effort and Actual Effort field. The Remaining Effort should be 0, and the Actual Effort should reflect the actual amount of effort that was needed to complete the task. Click Update after you have finished changing the fields. Page 17 of 41

18 9d. Now you will see the Iteration 3 view. Ensure that Open only is selected next to Iteration 3 so that only open artifacts appear. Next click the link for the last open task. 9e. In the artifact detail, change the Status field to Completed, and update the Remaining Effort and Actual Effort field. Click Update after you have finished changing the fields 9f. Now you should just see the parent user story artf1093 in the Iteration 3 planning folder view. Click the link for artf g. In the artifact detail, change the Status field to Ready for UAT. This indicates that the story is ready for User Acceptance Testing. Alternatively, you could update the Status to Ready for QA if your process is different. Click Update to return to the Iteration 3 view. Page 18 of 41

19 9h. Now you will see just artf1093 in the Open only view of Iteration 3. The remaining and actual fields have been updated based on the new effort values for the child tasks. Section 2: Manage your project workspace In this section, you will learn how CollabNet TeamForge makes it easy to administrate the tools for your project. You will: Add a member to your project workspace. Assign a role and permissions to a project member. Enable project tools and external linked applications. Customize the workflow for an artifact tracker. Use Hudson to build and test. Part 1: Add a member to your project workspace 1a. Go to your project by mousing over Projects, then My Projects, and finally click Brokerage System (Sample) In this exercise, you will learn how to add a member to your project workspace, so that you can make the project available to other site users. 1b. Go to the Project Admin tool by clicking on the top button menu. 1c. In the left panel, click the User Membership link. Page 19 of 41

20 1d. The Project Membership page lists the project members in your workspace. Click the Add button to add a member. 1e. In the list of available members, check the box next to Brokerage Developer (the user you created earlier) and click the Save button at the bottom. 1f. Notice that the user you added now appears in the Project Membership list. Part 2: Assign a role to a project member 2a. In the left panel, click the Permissions link. In this exercise, you will learn how to assign a role to a project member, so that you can ensure that members assigned to the role have the proper permissions to view, edit, and submit in the appropriate project tools. Page 20 of 41

21 2b. Next, click the User-Role Matrix tab. 2c. Check the box for the Brokerage Developer row in the Product Developer column. This assigns a Product Developer role to the user Brokerage Developer. Click Save at the bottom of the screen. Part 3: Update permissions for a project role 3a. Click the Roles tab, to navigate to the list of roles. In this exercise, you will learn how to update permissions for a project role, so that you can change permissions for project tools. 3b. Click the Product Developer link to edit this role. 3c. Click the Tracker link in the left panel to view the planning folder permissions for the Product Developer role. Page 21 of 41

22 3d. Observe that the Product Developer role has permission to submit, edit, and view all trackers, and you do not want developers to submit or edit Epics and Tests. 3e. Uncheck the box for All Trackers in the Submit/View section, and check the boxes for Defects, Stories, and Tasks. Do the same for the EditView section. In the View Only section, check the boxes for Epics and Tests. Next click the Save button to save your changes and return to the main Permissions page. Part 4: Enable project tools in your project workspace In this exercise, you will learn how to enable project tools in your project workspace, so that project members can access the tools they need for the project. Page 22 of 41

23 4a. In the left panel, click the Project Toolbar link. 4b. Check the box next to Reports, then click Save at the bottom. This enables the reporting tool for all members in your project workspace. Part 5: Add a linked application to your project workspace 5a. Click the Linked Applications tab. In this exercise, you will learn how to add an external application, and make it part of TeamForge. This will allow your project members to easily find the other tools that are needed for the project. Page 23 of 41

24 5b. Click the Create button at the bottom of the screen. 5c. Enter an Application Name, and a URL where the linked application will be hosted. Optionally, specify an icon for the linked application. Once you are finished, click the Save button. 5d. The linked application has now been created. 5e. To access your new Linked Application click the link for it, which shows to the right of the Project Admin tool. 5f. The Linked Application appears below the toolbar, similar to the other project workspace tools. After you are done playing around with your Linked Application, click the Project Admin link. Part 6: Customize the workflow for an artifact tracker In this exercise, you will learn how to customize the workflow of an artifact tracker, so you can add more statuses, and conditions for which project members can change the state of the status. Page 24 of 41

25 6a. In the Project Admin Menu, click the Tracker Settings link. 6b. Click the Stories link in the Trackers table. 6c. In the Tracker Fields tab, click the Status link in the Field Management section. 6d. In the Values table, click the Add button, to add a value for Status. 6e. Enter a value, and click the Move Up link to order the values. The order in the table determines the order of the drop-down values in Stories artifacts. 6f. After you reorder the values, click the Save Field button at the bottom of the screen. Page 25 of 41

26 6g. A prompt will display, warning you of possible delays. Click OK. 6h. Your changes to the Status field have now been updated. Next you will adjust the workflow for that new value. Click the Workflow tab. 6i. Click the link for the Status value that you just created. 6j. In the select box corresponding to the Roles to Make this Transition column, Ctrl+click the Product Executive, Product Manager, and the Project Manager roles. Click the Save button at the bottom of the screen. 6k. Now the Roles to Make this Transition column displays the roles that you selected for the new status value role. Part 7: Use Hudson to build and test In this example, you will learn more about Hudson Continuous Integration. Page 26 of 41

27 7a. In the Project Admin Menu left panel, click the Build & Test Integration link. 7b. If you already have Hudson running in your environment, enter the URL in the Override URL input box, and specify the behavior of how links will open. After that click the Save button. If you do not have Hudson running, just click the Build & Test button in the project toolbar to learn more about Hudson, and skip the next step. 7c. Click Build & Test in the project toolbar to see your Hudson integration. 7d. Logout of TeamForge, by clicking the LOGOUT link at the top right of the screen. Page 27 of 41

28 Section 3: Manage your TeamForge site In this section, you will learn how CollabNet TeamForge makes it easy to administrate the tools for your project. You will: Add a user group to your site and add a user to the group. Create a template from an existing project. Create a project using a project template. Learn more about integrations to Source Code Management (SCM) tools. Part 2: Add a user group to your site and add a user to the group 2a. Log into TeamForge as the site administrator by entering the User Name and Password, and then clicking the Log In button. In this exercise, you will learn how to add a user group to your site, so that you can group users together within projects, and ensure that they have similar permissions. 2b. Click the Admin link in the top navigation bar. 2c. Click the Groups link in the Admin toolbar. 2d. A list of available user Groups appears. To make a new group, click the Create button at the bottom of the screen. 2e. In the Create Group page, enter a Full Name and Description for the group. Then click Create at the bottom of the page. Page 28 of 41

29 2f. The group that you created now appears in the Groups list. To add users to the group, click the link for the new group. 2g. In the Users table, click the Add button. 2h. In the Found Users select box, click Brokerage Developer, then click Add. The user Brokerage Developer is now ready to be added to your new group. Add more users if you want, and when you are done, click the OK button at the bottom of the screen. 2i. Brokerage Developer now appears in the Users table for the group. You can add a group to your project by going to the Group-Role Matrix in the Permission section of the Project Admin tool. Click the Return button to go back to the list of groups. Part 3: Create a template from an existing project 3a. Click the Projects link in the Admin toolbar. In this example, you will learn how to create a template, so that similar information is available when creating new projects. Page 29 of 41

30 3b. Select the project that you want to create the template from. For this example, use the Brokerage System project. Click the Brokerage System (Sample) link to go to that project. 3c. Click Project Admin from the project toolbar. 3d. In the Project Settings tab, click Create Project Template. 3e. In the template options page, enter a Name and Description for the template. Check the boxes for each of the project tools that you want to include in the template. After you have selected the options you like, click OK at the bottom of the page. 3f. A message lets you know that a template is being created. Back on the Project Settings page, your template is available for new projects. Part 4: Create a project using a project template 4a. Click Admin in the top navigation bar. In this example you will learn how to create a project from a template, which simplifies the project creation process, and ensures that the foundation content is in place for the new project. Page 30 of 41

31 4b. In the All Projects tab, click the Create Project button. 4c. In the Create Project form, enter a Project Name, Description, and select the template that you just created from the Project Template dropdown. If there is a URL that you would like to use for the project, enter a URL Name, otherwise the system will create one for you. Click the Create button when you are ready to create a new project. 4d. A message lets you know that a project is being created. 4e. After the project has been created, you will see the Project Home for the new project. Part 5: Learn more about integrations to SCM tools 5a. Click the Admin link in the top navigation bar. In this example, you will learn more about integrations to SCM tools, such as Subversion and CVS. 5b. In the Admin toolbar click the link for the Integrations tool. Page 31 of 41

32 5c. Click the Subversion link in the SCM Integrations tab. 5d. Review the Integration information. Observe that you can change options such as Repository Base URL, Repository Root, and SCM Viewer URL. When you are done reviewing the Integration, click the Cancel button. Page 32 of 41

33 Clean-up: Delete Sample Users Log into TeamForge as the site admin user: User Name: admin Password: admin Click the Admin tab at the top of the page. Under Site Administration, click the Users icon. Check the boxes next to the users you wish to delete. Then click the Delete button at the bottom of the page. Click the OK button in the pop-up dialog to confirm. Now you are ready to create your own users! Do not forget to visit our TeamForge community if you have questions or other feedback. Good, bad, or ugly - we love to hear from our users! Page 33 of 41

34 Other cool TeamForge stuff In this section, you will learn about other cool stuff that you can do with CollabNet TeamForge. You will: Search for items (artifacts, documents, wiki pages) by keyword across projects. Add a document using CollabNet Windows Desktop. Part 1: Search for items by keyword across projects 1a. Click Search in the top navigation bar. In this exercise, you will learn how to search for items by keyword across projects, so that you can quickly and easily find items. 1b. In the Search Criteria screen, enter Order Screen in the keywords input box. Next, check the boxes for Search Attachments and Search Comments. In the select box below the keyword input box, Shift+Click all of the project tools. In Projects select the projects that you want to search across. Click the Search button to begin the query. 1c. You now see a list of artifacts that match your query for Order Screen. You can click on any artifact in this result to take you to the detail of that artifact. Page 34 of 41

35 1d. In the Search Results left panel, click the Discussions link to look at forums and posts that match your criteria. 1e. Notice that there is a post matching your search criteria. You can click the link for the post to view more detailed information. Next, click the Topics tab. 1f. There is also one topic that matches your search criteria, which you can also click. 1g. Now click Documents in the Search Results left panel. 1h. Here you will see all the documents that have Order Screen as part of the title or attachment. Next, click the Source Code link in the Search Results left panel. 1i. Here, you will find the one commit from a previous step. Click the link for the commit id. 1j. Now you will see the commit detail in the Source Code tool. Part 2: Install the CollabNet Windows Desktop In this example, you will learn how to install the CollabNet Windows Desktop, necessary for the next exercises. Page 35 of 41

36 2a. In a browser, open the Get It page for the CollabNet Windows Desktop. Click the Download button to start downloading the CollabNet Windows Desktop. Note: You must be registered and logged into open.collab.net before you can download the tool. 2b. A confirmation message thanks you for downloading the desktop. 2c. A popup shows that you are downloading CDMSWE. Select Save File, and click OK. 2d. Unzip the file using your favorite unzipping tool, such as WinZIp or Winrar. After you unzip the file, navigate to the unzipped location, and double-click the Setup icon. 2e. Click through the steps in the Setup Wizard to install CollabNet Desktop Microsoft Windows Edition. Page 36 of 41

37 2f. After the installation completes, launch Collabnet Desktop Windows Edition. Part 3: Create a connection to your TeamForge Site in the Windows Desktop 3a. From the File menu, click New, then CollabNet Site. In this exercise, you will learn how to create a connection to your TeamForge Site in the Windows Desktop, so that all of your project information is available in the desktop client. 3b. In the Add CollabNet Site dialog click CollabNet TeamForge from the Add a new site section. Then click Next. Page 37 of 41

38 3c. Now Enter the Collabnet Site URL and enter a title for the CollabNet Site. Then click Next. 3d. Enter your User Name and Password that you use to log into TeamForge. Optionally enter a Server Time Zone, and Validate you server Settings. Then click Finish. 3e. The site now shows up in the Site Explorer section on the left. A Favorites tab will display for the site you entered. A connection to your TeamForge site is now complete. Part 4: Add a document to your project using the Windows Desktop In this exercise, you will learn how easy it is to update TeamForge documents using CollabNet Windows Desktop. Page 38 of 41

39 4a. In the Site Explorer panel, expand the nodes for Brokerage System > All Projects > Brokerage System (Sample) > Documents > Mockups & Flows 4b. In Windows, navigate to the folder that contains the document that you want to add to TeamForge. 4c. Drag the document from your windows folder to the Mockups & Flows folder in CollabNet Desktop - Windows Edition. Page 39 of 41

40 4d. In the Create Document dialog, fill in the required fields, and any other optional fields that are relevant to the document. Then click OK. 4e. The document BetterOrderScreen.png now appears in the Mockups & Flows document folder. 4g. To see the document in the web version of TeamForge, right click BetterOrderScreen.png and click Web Browser from the menu. Page 40 of 41

41 4f. Observe that the document is also available in the web version of TeamForge. Thank you for reading the evaluation guide for CollabNet TeamForge 5.3. This is just a small sample of the powerful features that TeamForge offers, to learn more visit the CollabNet TeamForge product page. For more information about other CollabNet products, such as Subversion or Lab Management, please visit the CollabNet Products page. If you are interested in learning about training for TeamForge or Subversion, please visit the CollabNet Training page. Page 41 of 41