VersionOne – Story ”; Previous Next Story represents requirement, additional or change in existing functionality or new features. Stories are units of business values those can be estimated, tested and completed within a defined sprint. Stories consist of mainly two aspects − Acceptance criteria of the functionality to define acceptance tests. All the tasks are required to be completed by the team to deliver the story. Add a Story In this section, we will learn how to add a story. Story can be added by the Product Owner. Usually a team member cannot add a story until he has special roles like that of an admin, product owner, team lead, etc. There are many ways to add a story. We will discuss the ways as options below. After addition, a symbol in green color shows up. The symbol represents a Story. Option 1 Go to the Product Planner → Backlog. Click on the Add Backlog Item Inline button present at the top right. It will quickly add a top row where a user needs to enter the detail and click on the Save button. It adds the story into backlog items as top row. The following screenshot displays how to add a story inline − Option 2 Go to Product Planner → Backlog Click on arrow symbol of Add Backlog Item Inline button present at top right. Click on Add Backlog Item option. A new window opens along with different fields to enter details about story. Once the details are entered, a user clicks on the Save/Save & View/Save & New button. It adds the story into the backlog items and appears based on applied sorting methods. The following screenshot displays how to add a story detail − The following screenshot displays the Story Details page − Option 3 Click on the + icon at the sidebar menu. It opens the Add New options. Click on the Backlog Item option as shown in the following screenshot. A new window opens along with the different fields to enter the details about the story. Once the details are entered, a user clicks on the Save/Save & View/Save & New button to add the story into the backlog item. Access Story Details After the addition of story, details can be accessed by any team member having the project access. In this section, we will discuss how to view all the details of the story. To view the story details, click on Title or ID anywhere it appears in VersionOne. It opens the story details in a new pop up window. Conversations and Activity Stream are present at the left side of the page. At the top right, the Action Menu is present. Relationship Links are present at the top bar. The main page consists of the story details. The following screenshot shows the Story Details page − From the Story Details page, the following high-level tasks can be performed using the tabs at the top right of the grid − If a user wants to… Do this… View or update story details Click the Details tab. View the change history for a story Click the History tab. View a graphical representation of the story”s relationships to other workitems Click the Visualize tab. Edit story details Click on the dropdown to select the Edit tab and later open the Story Edit window. A user can also open this dropdown menu to perform other actions (Plan Story, Add Task, Add Test, Generate Parent Epic, Copy, Sign Me Up, Block, Split, Quick Close, Close and Convert to Defect, Delete, and Watch Story). Following screenshot shows the tab of high level tasks − Manage Story Details At the bottom of the Story Details page, a user can perform the following functions by clicking the Add or Assign buttons. To remove any items, a user can click Remove from the selected story. If a user wants to… Do this… Add a new task Go to Tasks and click Add Inline. Add a new test Go to Tests and click Add Inline. Assign upstream dependencies from available backlog Go to Upstream Dependencies and click Assign. Assign downstream dependencies from available backlog Go to Downstream Dependencies and click Assign. Identify (select) issue(s) have been resolved Go to Issues Resolved and click Assign. Select an existing issue to assign as a blocking issue Go to Blocking Issues and click Assign. Select existing Backlog items that are affected by the defect Go to Breaks Workitems and click Assign. Select an existing request Go to Requests and click Assign. Select an existing defect that breaks the selected story Go to Broken By Defects and click Assign. Designate the most current build(s) affected by the defect Go to Last Affected Build Runs and click Assign. Add a newlink remote documentation Go to Links and click Add.. Add a new fileattachement Go to Attachments and click Add.. The following screenshot displays how to manage story details − Print Page Previous Next Advertisements ”;
Category: versionone
VersionOne – Testboard
VersionOne – Testboard ”; Previous Next Testboard displays the list of acceptance tests for each backlog item and/or defect. It displays the current status of test as well; whether passed, failed or none. It is useful to view the status of each test to track the progress of individual tests during the testing cycle. To access Testboard, from the main menu, select Team Planner → Testboard as shown below − A user can select the Sprint from the top left side to see the details of the respective sprint. Test Cards appear in different status columns on the board (for example, None, Passed and Failed). It shows the test title, owner, and total work estimate. Test cards are color-coded by test type (i.e., Method, Type, Manual, Automated) to give a look at the testing across project work functions. Click the Legend button at the top right of the board to see the color representation and/or to customize the color-coding scheme by the test type. The following screenshot displays the Testboard view − Update Test Status In this section, we will discuss how to update test status. The Testboard has the following status columns – None, Passed and Failed. To update the status of a test from Testboard, go to Team Planner → Testboard. Drag and Drop each test horizontally to a status column to update it. Following screenshot displays how to update status − Reports on Testboard Reports on Testboard are data displayed in trend/charts to analyze the continuous progress. There are usually four types of reports available on Testboard. A user can access these reports by navigating to Testboard and clicking on Reports → Name of Report present at top right as shown in the screenshot below − Standup Dashboard Report − It displays a high-level view of team progress through its sprint workload. The dashboard displays continuous graph of the remaining work To Do and the cumulative flow by status where date is x-axis. It also displays the current view of the Testboard. The following screenshot displays the Standup Dashboard Report − Test Trend Report − It displays the bar graph to show how the status of the tests has changed over a period of time. It displays color-coded bars; this indicates the number of tests in specific status (not yet run, passed, failed, etc.) at specific milestone dates. The following screenshot displays the Test Trend report − Test Runs Report − It displays the bar graph showing project-level test results from an external testing system by test status (for example, not yet run, passed, failed). Burndown Report − It displays the progress of a team through its sprint workload. It displays the amount of work done and remaining to be done (To Do) versus the expected (ideal) schedule. Print Page Previous Next Advertisements ”;
VersionOne – Free Trial Access ”; Previous Next VersionOne provides free trial for 30 days to registered users. The free trial version of VersionOne comes with basic features. TestRail has other plans as well with different advanced features and add-ins. The cost depends on the products that come along. VersionOne has the following different products − Team Ultimate Catalyst Enterprise VersionOne Team is free for Single Team with basic features for other products VersionOne provides 30days trial period. By visiting https://www.versionone.com/product/lifecycle/pricing-and-editions/ a user can see the different available plans for trying purpose. Setup for Free Trials To use the free trial version, one time basic setup is required. It includes registering into VersionOne by providing basic details and getting personal URL at email to access the VersionOne. In the following steps, we will learn how to set up the VersionOne while accessing it for the first time − Visit https://www.versionone.com/ and click on Try Free at the top right as shown in the following screenshot − It opens a basic form to create a VersionOne account. Enter the details at following fields as shown in the following screenshots − Name, Organization, Designation, Number and Country. These are basic details of user and useful to set up profile after accessing the VersionOne. These details help to maintain unique user concept. A user cannot enter duplicate records to register. Email − Please note, it accepts gmail, yahoo, outlook. It can be business email as well. After entering all the details, check the checkbox for Term & Services and click on “Start Your Free TRIAL”. It will display the next page where a user should create password and provide Project/Sprint name. Now, click on Set Up. Upon clicking Set Up, VersionOne creates the personal URL and account to access free trial and send the email, provided into the form at the 1st page. An Email will look like as in the following screenshot − By visiting the given URL, a user will get login page for VersionOne. Print Page Previous Next Advertisements ”;
VersionOne – Search
VersionOne – Search ”; Previous Next VersionOne supports the search functionality, it helps to find specific details within VersionOne as well as narrow down the displayed details. Search functionality is categorized into two − Quick Search − Search for open workitems, Conversations and Community Topics. Advanced Search − If a user wants to search Closed or Deleted Workitems, use Advanced Search. Quick Search Quick search is simply a wild card search where VersionOne tries to get all records that fulfil the text match. Follow these steps for quick search − Quick Search is located at utility bar, on the top of every page. It searches open workitems, conversations and community topics. A user can type 3 characters or ID into the search text box. If a user pauses after typing 3 characters, a preview of matching Open workitems displays. If a user keeps typing, the matching results become more refined. The following screenshot displays how to use quick search − Advance Search VersionOne supports the advance search functionality. It helps to provide specific data that a user wants to search. Follow these steps for advance search − In advance search, a user can search specific asset type, closed and deleted workitems as well. To open the Advanced Search page, click on Quick Search box and then press ENTER/RETURN key. Alternatively, a user can click on the Search icon present after the search text box as shown below − The Advanced Search page opens in a new window. A user can type a word that is to be searched and click on Search. Additionally, before/after clicking search, a user can narrow down the search further by selecting the Open/Closed/Delete checkboxes. Following screenshot displays how to do advance search − Additional Options In this section, we will discuss the additional options to search data. Change the sort order − Click on a column header to change the sort order. By default, the search results are sorted by the items most recently changed. View results by asset type − Click on a tab to filter the list by asset type. View item details − Click on an item to open the details page. Print Page Previous Next Advertisements ”;
VersionOne – Discussion
Discuss VersionOne ”; Previous Next VersionOne is a project management tool used to track and maintain records of all STLC phases in Agile from backlog to report creation. This is a brief tutorial that introduces the readers to the basic features and usages of VersionOne. The tutorial will guide the users on how to utilize the tool in reporting and maintain the testing activities. Print Page Previous Next Advertisements ”;
VersionOne – Home
VersionOne Tutorial PDF Version Quick Guide Resources Job Search Discussion VersionOne is a project management tool used to track and maintain records of all STLC phases in Agile from backlog to report creation. This is a brief tutorial that introduces the readers to the basic features and usages of VersionOne. The tutorial will guide the users on how to utilize the tool in reporting and maintain the testing activities. Audience This tutorial has been prepared for beginners to help them understand how to use the VersionOne tool. Prerequisites As a reader of this tutorial, you should have a basic understanding of bug and testing lifecycle. Print Page Previous Next Advertisements ”;
VersionOne – Dashboard
VersionOne – Dashboard ”; Previous Next After logging into VersionOne, a user can navigate to Dashboard where progress of work is summarized and a user can customize reports and matrices as well. A Dashboard is customized by Admin. Based on roles, admin can set the access of VersionOne. Dashboard is similar to homepage that displays all important details and provides links to access of other modules. In this chapter, we will see features and customization of Dashboard. Points to Note By default, the Dashboard provides important details about project and the progress. It displays the data for different modules like Project Hierarchy, number of Open Issues, Backlog Count, Defects at project level in the hierarchy. In the following section, we will discuss the important features of Dashboard − To navigate to the My Dashboard page, click on My Home → My Dashboard link as shown in the screenshot below. It displays the Dashboard page with the default set up. In the Dashboard page, My Project Summary is located at the top of the page. It shows different metrics to evaluate the state of a project. Filters are also available to search specific projects details. By default, the following fields display for each project − Project Title Owner End Date Projected End Date Progress Bars (hover to see Open and Closed Estimates) Open Stories/Backlog Items Open Defect Count Open Issue Count The navigation bar, present at the top of the page, will be same across all pages/screen of VersionOne – Project, Portfolio, Product, Release and Team. The navigation bar has many sub links under each of these links. At the right side of the same navigation bar, Report section is also available. By clicking on these links and sub links, a user can get access to different modules/features supported by VersionOne Dashboard has different links at the top right. These are same across all pages – Site Navigator, Settings, User Profile and Help. These are the static feature of the VersionOne HTML design. In the extreme left side, it displays few useful shortcut links as Add New Item for Backlog Item, Defect, Story, etc., My Recent Changes to view all recent changes, Rooms, Timesheet, Collaboration, Conversations, Topics and Deleted items. The following screenshot displays the Dashboard of VersionOne − Add Chart Dashboard can be customized by adding different available charts to track day to day progress of the project/sprint. A user can add any of the following charts to the My Dashboard page. These charts (displayed at the bottom of the page) help to track progress of the project, sprint/iteration, and team status. Project Burndown Sprint/Iteration Burndown Work item Trend Defect Priority Trend Defect Priority Trend Test Trend Work item cycle time Work item cumulative flow To add a chart, click on the Add Chart button present at the My Dashboard page and select one of the charts as shown in the screenshot below. It displays all available charts to add into the dashboard. After selection, the chart appears at the bottom of the page as shown below − User Profile A logged in user can view his profile in VersionOne. A user with admin role will have access to all users’ profiles and can edit/update as well. In this section, we will discuss how to view profile and update the details. By clicking on the Profile icon, a user can view the following options − My Details − user can view his personal profile as shown below − It opens the profile details with the edit button on the right side. A user can view History and type of application by clicking on corresponding tab. In details, a user can see Project Membership, Owned Projects, Link and Attachments as well. The following screenshot displays the user detail page − Edit the details on this page. Once a user clicks on the Edit button, the user details open in a new window in the edit mode. A user can change the details and click on Save to save the changes as shown below − Lifecycle Preferences − A user can select Navigation, Email forwarding options, Event Notifications and Report Settings as shown in the screenshot below − Change Password − Using this option, user can change the current password and set a new one. Push Notifications − It manages notification from third party applications. Applications − It manages keys and tokens from third party applications. Logout − By clicking on Logout, a user will be get back to the login page and will not be able to access project details without logging in back as shown in the screenshot below. Print Page Previous Next Advertisements ”;
VersionOne – Features
VersionOne – Features ”; Previous Next In this chapter, we will discuss the different features of VersionOne. The main feature of VersionOne is to attract QAs and other stakeholders for Agile management. VersionOne Core Features VersionOne provides a wide range of features that prove beneficial to the Agile Project team. It does not only support Project management but also how to do day to day activities in case team is not situated locally. It provides a software solution to implement agile within the globally situated team. Following table lists down the core features of VersionOne − Sr.No. Core Features Description 1 Testing Supports VersionOne supports the following test methodologies − Agile Testing − Full Life Cycle Black box testing Exploratory Testing Functional/Manual Testing Automation Testing 2 Centralize & organize VersionOne tool can create, centralize, organize and manage test cases very effectively and efficiently. It can easily import test cases from Excel and other management tool. It can create multiple versions of test cases for comparison and uses It can do planning of releases and sprints. 3 Manage & Track Progress It supports build out and re-run of test execution suites. It kicks off automation suite as well. It captures step-by-step progress of sprint/release with detailed explanation. It supports day-to-day progress and individual contribution. 4 Notification Email can be sent for a particular task/communication to users. Voting and watching features to keep an eye on progress for stakeholders. Use @mention to get attention of specific team member at Comments/Description. 5 Power Search VersionOne supports powerful search functionality with Hotkeys features. Supports free text search. Supports syntax search. 6 Reports VersionOne supports multiple reporting. It supports Burndown, Velocity and Test Trends report. Generate detailed summary report for projects, release and sprints. Track the workload of entire team as well as individual. It supports Cross Project Report as well. 7 Scale with Team Growth VersionOne supports any business team and any project irrespective of size and complexity. 8 Integration VersionOne supports more than 80 pre-built integration to connect with different software’s to make work easy. Wide range of add-ins makes it universal across the globe – JIRA, BugZilla, ALM, GitHub, Borland, CA, Hudson, Jenkins, Visual Studio etc. It also supports Salesforce, Microsoft, Zendesk. 9 Common Features It supports sticky sidebars. It supports rich text formatting. It helps in optimizing printing. It helps in scheduling and forecasting. 10 Recover Data It helps in generating and downloading full system backups. Migrate and import existing test cases from Excel and legacy data tool. Export data into CSV, XML and Excel files. Print Page Previous Next Advertisements ”;
VersionOne – Backlog
VersionOne – Backlog ”; Previous Next Backlog is the list of all work items. Stories, Defects, Test sets are part of work items. Stories are primary items in backlog. Work items categorize and define all works to be done for a project and iteration/sprint level. Access the Backlog Page In this section, we will learn how to access the Backlog Page. Backlog page can be accessed by navigating the Product Planner − Planning − Backlog as shown in the screenshot below. It opens the backlog page; the page consists of all available backlog items. Backlog Page provides a flexible, editable grid of workitems associated with a project and all of its subprojects. Here, a user can add new workitems, as well as edit, filter, sort, categorize, and prioritize existing items relative to one another. In the backlog page, a user can see the following fields for each workitem − Order − It shows priority of the workitems. Title − Name of each workitems. ID − It display unique id of workitems. Owner − The person who owns the workitem. Priority − It shows how prior the backlog item should consider. Estimate Pts − It provides the complexity of workitem. Project − It displays the associated project name. The following screenshot displays the Backlog page view − Add Backlog Item A user with proper role can add the Backlog Item into a project. Usually issues and defects can be added by all users having access of project. Stories can be added by the product owner. Now, we will discuss how to add a backlog item. Go to the Backlog page and click on the arrow sign of the Add Backlog Item Inline button. It provides 2 different options to add each backlog item or defect. One option is Add Backlog/Defect Inline and the other is Add Backlog Item/Defect as shown in the screenshot below − When a user selects the Inline option, a new row gets added as 1st row. Here, the mandatory details can be entered directly. After that, click on the Save button present at the right side to keep the record of entered details as shown in the following screenshot − Or, When a user clicks on Add Backlog Item/Defect, a new window opens along with the different fields to enter the details about workitem. Once the details are entered, a user clicks on the Save/Save & View/Save & New button. The following screenshot displays the Add Backlog Item/Defect page − Backlog Goals The Backlog Goal contains the group of stories or backlog items that provide the direction to the Project Team. It is usually the standard target (short and long term) to measure the direction of the project team. Consider the following important features of the backlog goal − A Backlog Goal contains group’s backlog workitems that display the progress of the project team. It is measurable and specifies the direction and priorities of the project team. It can have many-to-many relationship with workitems. It allows free association between stories, defects or even portfolio items to Backlog goals. To access the Backlog Goals, navigate to Product Planner → Planning → Backlog Goals. To add a Backlog Goal, click on the Add Backlog Goal button present at the top right as shown in the following screenshot − It opens a Backlog Goal form in new window. A user enters the details as Title, Project, Team, Planned Business Value, Actual Business Value, Target in Project, Description, Type and Priority. After that, click on the Save/Save & View/Save & New button as shown in the screenshot below. It saves the Backlog Goal. The goal can be viewed by a user at a later stage of the project to compare standard Vs actual. There is an option Summary by Project. When user clicks on this button, a new window opens and displays the progress of each project as % of Backlog Goal and % of Project. The following screenshot displays the Summary by project − Print Page Previous Next Advertisements ”;
VersionOne – Invite Users
VersionOne – Invite Users ”; Previous Next VersionOne supports the invitation functionality. A logged in user can invite any number of users to join VersionOne. A user with Admin role can directly add the user into VersionOne. In this chapter, we will see steps about how to invite the user. Follow these steps to invite new users into the VersionOne domain − Navigate to the Setting icon present at top right of each page and select Members as shown in the screenshot below. It opens the Member’s page with the user’s details. Login as System Admin is a prerequisite to view this option. The Members’ page that opens up displays a list of members having the domain access. At the right side, a user can view the Invite Member button where a user can select either Invite member or Add Member. Invite Member − A user gets email to join the VersionOne Add Member − The Admin provides Username and Password to add one of the team members who already has access to VersionOne for different domain. It is basically allowing access of the project to a team member The following screenshot displays the Invite Member option − The following screenshot displays the Invite Members form where the Admin enters email of the invited member, the project to assign and the role to offer. After selecton, click on the Invite Members button. The user will receive the email to join the VersionOne along with a link. Add Member An Admin User can directly add a user or group of users into VersionOne and can set up username and password on the user or the group’s behalf. It is useful when a team member needs quick access to specific project. Let us now see the steps to add a team member. The steps are as follows − To add a single user, click on the Add Member option. It will open a form wherein you have to enter full name, short name, username, password, email address, notification, admin privilege, description, etc. as shown in the screenshot below − Now, click on Save/Save & New/Save & View button to complete the add process. Save & New − It will add the user and open a new form to add another user. Save & View − It will add the user and open the details of the added user. Print Page Previous Next Advertisements ”;