Category: versionone

VersionOne – Collaboration ”; Previous Next In this chapter, we will learn how collaboration takes place with VersionOne. As soon as sprint/project team is formatted, they can utilize the collaboration tools to keep update and track of sprint/project. To access the collaboration tools, click on the Collaboration symbol present at the side menu bar as shown below − A user can see the different communities at the left side along with where they are members of and conversation is another tool in collaboration. Community Community stands for VersionOne community. All members of VersionOne are part of this. They can access articles, blog or other important details here. A Topic is an article content within a community. Topics contain agreements, best practices and documents that promote the Agile. To view a topic, select the community present at the left side under Community section. Click on View to view one of the topics with all its details. Consider the following screenshot to understand the step − Once the details of the topic displays, double-click anywhere in the content or click on the edit symbol at the top right to start editing the content. After editing click on Save button. User even can edit title of the content. At the bottom of the content, a user can attach paperwork by clicking on the Add Attachment button. The max file size is 4 MB. A user can start a conversation under the conversation section. The following screenshot displays how to work with content − A user can even delete a topic with the required permission. To delete a topic, click on View to expand the topic content. At the top right, the delete symbol is present, click there as shown below − It opens the Delete Confirmation pop-up. When a user clicks on Delete, it deletes the topic. The following screenshot displays the delete pop-up − Print Page Previous Next Advertisements ”;

VersionOne – Filters ”; Previous Next Filters are used to narrow down or expand the lists of items displayed in a page. It helps to focus on items that are important. Filter is available on each page and section at the left side as shown in the screenshot below − Filter Specifications Filters come with a wide range of options and features. A user can make use of the filters according to his requirements. Consider the following are few important features of filters − Select multiple filters at a time. Add multiple values for each field. Filter by more than one Owner, Team or Priority. Filter checkboxes, dates and numbers. Use LESS THAN and GREATER THAN. Use BEFORE and AFTER, in addition to IS. Press the Enter key while typing in the Find supported filter field. Use the CTRL+SHIFT+F keyboard shortcut to invoke the filter options. How to Use Filter The use of filters helps to get the desired data on the page and trim off the unwanted data from the user perspective. Following steps display how a user can utilize the filter functionality − Click on Filter dropdown that displays the all available option. A user can select any of the option at a time. If sub-options are available, a user can select those as well. For example, Status → Future, In Progress, Done, Accepted. Priority → Unassigned, Low, Medium, High; Similarly, Team, Workitem, Rollup Category, Sprint, etc. After selection, click on Apply (if sub-option is present), otherwise filter will be applied directly as soon as selected from dropdown as shown below − After selection, a user can see the selected filters at the right side of the filter as shown below − Clear Filter After the application, a filter needs to be cleared as well. Next time, this makes it easy for the next user to fetch the details. In general terms, clear filter allows to display all details at the page. To clear a single filter − Click on the ‘-‘ symbol next to the name of the filter. To remove the applied filters, restore the default settings − Click Clear All Filters in the top right corner of the page. The following screenshot displays how to clear the filters − Print Page Previous Next Advertisements ”;

VersionOne – Edit Defects ”; Previous Next Editing a defect involves many actions. The different actions can be – modifying details of the defect, closing it, deleting it, add into the watch list, block it with issues or another defects, convert into story etc. In this chapter, we will discuss how to go about editing defect details, closing a defect and deleting a defect. Edit Defect Details While editing the defect details, a user can edit all the details of the defect including title, priority, estimation and dependencies. The only unmodified field is unique id of the defect, it can never change or modify. There are three ways to edit a defect. The ways will be discussed as options below − Option 1 The steps in this option are recommended to quickly edit the title, estimated points, projects, priority, owner and order. Go to Product Planner → Backlog. It opens the backlog page. Double-click on row to make the column editable. The column changes from the view only to edit mode. After editing, click on Save. It saves all the modified details of the corresponding row. The following screenshot displays how to edit the defect details − Option 2 Go to Product Planner → Backlog Click on the Edit button present corresponding to each row of the defect It will open the defect details in the Edit mode. After editing, click on Save/Save & View. The following screenshot displays how to access the edit functionality − Option 3 Click on Story Title/ID to open the Story Details page. Click on the Pencil icon next to the field to enable editing. It makes the field editable. Make the appropriate changes and then press Enter/Return on the keyboard. It saves the modified details of the respective field. The following screenshot shows the edit functionality at the defect details page − Close a Defect Once all the tasks of a defect are completed, it can be closed to claim the work done in the sprint. A closed defect can be re-opened later if required. In this section, we will discuss how to close a defect. Closing a defect tells that all the work related to it is completed and that the fixes are done. Once a defect is closed, a user can re-open it if the same bug appears again. Quick close update the status of defect and closes it in a single click. There are many ways to close a defect. The ways will be discussed as options below. Option 1 Go to Product Planner → Backlog. Click on the Edit dropdown present corresponding to each row of the defect. Select Close or Quick Close as shown in the screenshot below − If a user selects Close, it opens an additional window. Here, select a status and click on Close Defect as shown below. If Quick Close is selected, it directly closes the defect without any additional input. Option 2 Click on the Defect Title/ID to open the Defect Details page. Click on the Edit dropdown. Select Close or Quick Close as shown in the screenshot below − If a user selects Close, it opens an additional window. Here, select a status and click on Close Defect. Delete a Defect A deleted defect cannot be tracked and visualized later. Deletion usually happens if a defect is not needed or if it is duplicate. In this section, we will discuss the deletion of a defect. If a defect is created in error or duplicate, then only it should be deleted. For tracking the defect, it must be closed instead of getting deleted. Deleting a defect hides all of its references. If a defect is deleted, all its child items such as link, attachments, task or test sets are also deleted. Let us now see the different steps involved to delete a story − Go to Product Planner → Backlog. Click on the Edit dropdown present corresponding to each row. It displays all the available options to take action. Select Delete as shown in the screenshot below − It will open the read only detail of the defect with the Delete button. Click on the Delete button as shown below − Similar steps can be followed to delete the defect from the Defect Detail page − Click on Defect title/id to open the defect detail page. Click on the Edit dropdown and select Delete. It will open the read only detail of the defect with the Delete button. Click on the Delete button to delete the record of defect. Print Page Previous Next Advertisements ”;

VersionOne – Taskboard ”; Previous Next Task board represents the different tasks available in the sprint and grouped by backlog item and/or defect. Each task is associated or categorized by task status. Taskboard is used during the team”s daily meeting to get a quick progress of the overall work within the team”s sprint. A user can track the progress by moving tasks to a different status. To access Taskboard, from the main menu, select Team Planner → Taskboard. On the Taskboard, Tasks are displayed in different status columns (for example, None, In Progress, Completed). Task card displays the task title, owner and total work estimate. Task cards are color-coded by type (i.e., Design, Code, Admin) to provide an at-a-glance look at the balance of work across project work functions. Click the Legend button at the top right of the board to see the color representation and to customize the color-coding scheme by task type. The following screenshot displays the Taskboard − Track/Update a Task A task can be updated from the Taskboard. A user can track and later update efforts spent for the task. A user can update the overall status of the task as well. Consider the following points related to the updation of a task. When a user hovers over Task title, it displays a detailed description of the task. To update a task, open the dropdown menu in the top right corner of the card. Select the appropriate action (edit, assign an owner, assign yourself, track the effort and To Do for the task, close, or watch the task) as shown below − To change a task status, click and drag the Task Card to the appropriate status column in that row. As work progresses, enter Effort and update the remaining To Do hours for each task via the Edit function on the Task Card dropdown menu. Now, click on Save as shown in the screenshot below − Print Page Previous Next Advertisements ”;

VersionOne – Login ”; Previous Next In this chapter, we will learn the steps involved to log into VersionOne. Follow these steps to log into VersionOne. Step 1 − To login into VersionOne, go to your sample website, provided into email while creating the free trial. It will open a login page. Step 2 − Enter your registered email address as Username and Password (selected while creating the account). Step 3 − Click on the Login button. Following screenshot shows how to login into VersionOne using credentials − On Error While logging in, a user can face errors due to wrong combination of username/password. A user can utilize different available features to reset password and login again. Here, we will see what errors a user can face and how to find resolution to such instances − Due to unsuccessful login, a page as shown in the screenshot below might appear. Error may occur due to wrong combination of email id or password. Following screenshot shows the error message a user receives if the credentials are not correct − If you forgot the password, to recover it − Click on “Forget Password” beside the Login button. Enter the Login Email. Click on the Reset Password button. It asks to enter registered email to send the password reset link. The following screenshot shows how to recover the password if you forgot − A user will get an email with details to reset the password. On Successful Login In this section, we will discuss how VersionOne works on successful login. On successful login, the My Subscription page gets displayed. The following screenshot displays the welcome page of VersionOne on successful login Print Page Previous Next Advertisements ”;

VersionOne – Notification ”; Previous Next Notification is subscription based. Subscription allows controlling the types of notifications a user receives. It is based on the event types that a user subscribes to. For example, if a user wants to know when a work item is assigned to him, he can set up a subscription to notify. User can also subscribe when a story is closed or even when the status of a defect changes. This way, a user can keep track of the things. Subscription To get a notification, a user needs to subscribe to the notification service first. Until it is not subscribed, a user cannot receive any notification. In this section, we will discuss how to subscribe for a specific notification. To view the user’s subscription for notification, go to My Home → Subscription as shown below − In the My Subscription page, a user can see the subscriptions made by him. In the Notification Types, a user can see all type of notification that can be subscribed for. To subscribe for a notification, click on the Subscribe button present at the right side as shown below − It opens a pop-up wherein, a user can enter Title, Description, select Project, Owner and Team to narrow down the subscription. Now, click on the Subscribe button as shown below − Delete a Subscription Whenever a user wants to stop receive any notification, he should delete the notification at the subscription page. In this section, we will discuss how to delete a subscription. To delete a subscription, go to My Home → Subscription. At My Subscription, click on the Edit dropdown at the right side. Select Delete from the available options and it de-subscribe the notification as shown in the screenshot below − Print Page Previous Next Advertisements ”;

VersionOne – Team Rooms ”; Previous Next TeamRooms is the place where a user can track and view the progress at the project level as well as sprint level. In TeamRoom, day to day progress can be tracked at the individual level. To access the team Rooms, go to Team Planner → TeamRooms as shown in the screenshot below − It opens the TeamRooms created for different project/release. A user can click any of these to see the corresponding details. Add a Team Room Usually, a scrum master adds the TeamRoom. Let us now see the steps to add a TeamRoom. Navigate to Team Planner → Team Rooms. It displays the Team Rooms page with all the available rooms. To add a Team Room, click on the Add TeamRoom button present at the top right. It opens the Add TeamRoom window, where a user can enter title, select Team Flow and schedule. Now, click on the Save button present at the bottom of the page. Note − Users having Team Lead or above roles can only add a TeamRoom. The following screenshot displays how to add a TeamRoom − TeamRoom Panels TeamRoom consists of many important details. In this section, we will discuss the details displaying into TeamRoom. To view the TeamRoom detail, go to Team Planner → Team Rooms and click one of the available rooms. By Default, Backlog is selected. Otherwise, click on backlog to display the backlog items in the left side. Click on the additional panel tab to display the items as explained below − Sr.No Panel & Description 1 Backlog Displays unscheduled backlog. These items might fall into sprints by grouping backlog items into sprint based on their estimates and the current average velocity. Items display in rank order, with the highest ranking at the top. The item”s estimate is also display if an estimate value exists. Drag and drop the backlog items between columns to update the status. 2 Storyboard Shows all the stories (displayed as story cards) in a sprint/iteration in the selected sprint. 3 Taskboard Displays tasks grouped by story, defect and by task status in the selected sprint. 4 Testboard Displays acceptance tests grouped by backlog item, defect and by test status in the selected sprint. 5 List View This panel shows a list of work items in the selected sprint. 6 Closed Allows reviewing the closed work. Items are grouped by their sprint and sorted by sprint start date. Item estimates display when assigned to the item and estimate totals display on the sprint. 7 Conversations Shows all conversations started in the room as well as conversations that mention work items in the room. 8 Activity Stream Shows all the activity that has occurred on the assets in the TeamRoom. Items display in reverse-chronological order and only display once in the list based on the most recent change. 9 Estimably Allows the creation of an Estimably estimation game. After starting a game, drag items from the Backlog panel into this panel to estimate them. Note that when user submits the results of a game, the estimate for that item is also updated. 10 Scorecard Instant access to a barometer of key project performance indicators at the project, program, portfolio item, and team level. 11 Topics View Communities Topics directly within the TeamRoom. The following screenshot displays the TeamRooms overview − Print Page Previous Next Advertisements ”;

VersionOne – Introduction ”; Previous Next VersionOne is a web-based project management tool used by testers, developers and other stake holders to manage, track and organize software testing efforts. It follows and covers full life cycle of Agile Methodologies. It supports from first step as Product Backlog to the project’s final step as completion and delivery. Interesting Points VersionOne supports a wide range of functionalities and is one of the best available project management tools for Agile. VersionOne is joining CollabNet to bring DevOps into the table. Following are a few interesting facts about VersionOne − VersionOne helped to bring the Agile Management tool in 2002. VersionOne is also known as the Agile Management tool. It is developed and copyright by VersionOne Inc. VersionOne is a web based tool that supports all browsers especially Chrome, Firefox, IE etc. It supports different windows OS like Windows XP, Vista, 7, Mac, etc. VersionOne provides 30days trial period. It supports all phases of planning, scheduling, collaborating, tracking and reporting for projects, releases, iterations, epics, stories, defects, tasks, tests, teams and team members. VersionOne was named as one of the Best Places to Work by the Atlanta Business Chronicle. Now, CollabNet and VersionOne have merged to accelerate innovation across Enterprise Software Development and Delivery in 2017. VersionOne can be customized using various methodologies such as SAFe, Scrum, Kanban, Lean, XP, and DAD. License and Free Trial VersionOne is used at commercial level across various software industries. It allows the new users to go through the tool by providing limited free access. In this section, we will see how VersionOne connects with different user groups at personal and commercial level − VersionOne is a commercial tool and available as Trial version for a limited period of 30 days. For personal use, a user can register and get a hands-on experience of VersionOne. To utilize VersionOne services, a license is required. After 30 days, if a user wants to continue using VersionOne, a license is required. By purchasing one of the products, VersionOne provides license key to continue for a certain time period based on purchase agreements. VersionOne provides free license for 30 days for cloud based access as well as local server set up. User can set up host server into his local machine as well by following installation guidelines and fulfilling pre-requisite. VersionOne Uses There are a wide range of benefits and usage of VersionOne depending on team size, type of work and other factors. The benefits and usage are listed below − VersionOne is used in tracking all QA activities from the 1st phase of software testing lifecycle in Agile. Tracking can be started from adding the requirements to accepting the requirement by the Product Owner. VersionOne is useful in Project Management, Defect Management and to customize into different agile methodologies as per the requirements. A user with proper role can customize the VersionOne fields, boards, reports, displays according to project requirement and standards. In addition to the above, VersionOne also supports agile portfolio management, product road mapping, regression test management, customer idea management, agile visualizations and custom reporting and analytics. It supports all macro level activities performed by QA. VersionOne is very useful in performing QA tasks like planning, scheduling, collaborating, tracking and reporting for projects, etc. VersionOne Specifications The base of VersionOne is combined with different and latest technologies and ideas. To use a developed VersionOne tool, hardware and software supports are required at Server as well as Client side. Following table lists down important specification of VersionOne − Sr.No. Specification Description 1 Application copyright It is taken by VersionOne Inc. It provides Commercial and Trial Version. 2 Tool scope It can be used as Project Management and defect tracking It is utilized as Agile Management Tool 3 Testing Methods Agile Testing Automation testing Exploratory Testing Functional/Manual Testing 4 Tool Objectives Complete life cycle of Agile Methodologies Desktop Testing Web Testing Report statistics 5 Management Features Product Backlog Resource Management Defect Management Project Management in Agile Reporting 6 Hardware Requirements for Server CPU: Dual Core 2GHz and latest Memory : 4GB and aboveRAM 7 Error Handling Capture screenshots 8 User interface Available Plugin GUI usability Mobile UI Server and Web based Print Page Previous Next Advertisements ”;

VersionOne – Useful Resources ”; Previous Next The following resources contain additional information on VersionOne. Please use them to get more in-depth knowledge on this. Useful Links on VersionOne VersionOne − Official Website Reference for VersionOne. VersionOne Wiki − Wikipedia Reference for VersionOne. To enlist your site on this page, please drop an email to [email protected] Print Page Previous Next Advertisements ”;

VersionOne – Release Planner ”; Previous Next Release Planning is an optional activity. In this planning, the development team schedules the work items to be delivered in a release, also called a project. As part of the effort, team estimates and prioritizes the backlog items and then breaks them down into a series of sprints/iterations. In general, there are two types of release planning − Tactical release planning is done at the backlog level. It schedules individual backlog items, defects or test sets for incorporation in a release. Strategic release planning is done at the feature level. It schedules the entire portfolio items which automatically brings along the lower level backlog items. To drive strategic plans, a team can use factors such as business value, risk, team velocity, and cost (swag at the portfolio item level or Estimate at the backlog item level). The Release Planner consists of Planning and Tracking activities. The planning activities group Release scheduling, Regression Planning and Team Scheduling while the tracking activities group Release Forecasting, Program Board and Delivery at a glance. The Release Planner and its activities can be accessed by clicking on the Release Planner as shown in the screenshot below − Release Scheduling Release scheduling is part of Release Planning. In this scheduling, release is scheduled for the project. A project can have multiple releases and in this stage, all releases are scheduled like when a release will go live and when all the release related works will be completed. The Lifecycle Release Scheduling feature is an optional release planning tool. It allows to build a release plan by scheduling stories/backlog items or portfolio items into releases. Release schedules an end date of release as well. To access Release Scheduling, from the main menu, select Release Planner → Release Scheduling. The following screenshot displays the Release Scheduling page − The items in the backlog grid on the left are “unscheduled”. In other words, they have not been added to a project/release. Note that once “scheduled”, the work item is removed and no longer displays in the backlog grid on the right. To add a backlog item into release, a user can drag and drop into Child Projects → <Release Name> at the left side as shown in the screenshot below − Team Scheduling Time Scheduling defines the timeline of the releases and completion as well as the start date of other backlog items. Timeline is the standard reference to re-distribute work items and resource allocation in the project. Team Scheduling allows the user to allocate and view workload across assigned teams working on selected projects/releases. In Agile, backlog is assigned to the team, not to individual team members. Team Scheduling displays how workload is distributed across teams and the capability to redistribute the work based on needs. The following screenshot displays the Team Scheduling page − Note − The Team Scheduling feature is being deprecated in favor of new Iteration/Sprint Scheduling page. Release Forecasting Release Forecasting provides analyzed data based on the end dates. It also provides analyzed velocity of the team to achieve targets at various ends dates. It is basically forecasting of the entire project from high level to the granular level with respect to different target dates. Following are a few important features of Release Forecasting − Release forecasting report simultaneously shows the forecasted end dates. This is based on optimistic, pessimistic and average velocity. These velocity values are calculated from the visible historical data. It also indicates the end date of the selected project; with this, a user can compare the forecasted dates to the planned end date. In addition, a user can forecast the end dates based on total estimate or workitems count. Release Forecasting can be accessed by navigating Release Planner → Release Forecasting. After the selection of report fields, click on Go. It displays the forecasting report. The following screenshot displays Release Forecasting − Print Page Previous Next Advertisements ”;