VersionOne Tutorial: All-in-one Agile Project Management Tool Guide

Why and How to do Software Testing with VersionOne: All-in-one Agile Management Tool

At current epic of technology exponential development across various domains, the demand for software testing is in its highest state. To proactively respond to the process of iterative delivery of the world-class software applications needs, different companies have been introducing the variety of test management tools to the market.

So, this hands-on will give you an overview of why and how to use VersionOne, one of the many software project management tools available in the industry. 

VersionOne review tutorial

What we will cover in this tutorial

We will look at VersionOne Team Edition V.17.0.1.164 major features with an emphasis on software testing by covering the aspects below:

  • Introduction to VersionOne – all-in-one Agile Management Tool
  • Installation and setup
  • Adding stories and tests in the backlog
  • Planning Sprints/iteration
  • Log defects as tests get executed
  • Tracking Sprints for artifacts status, and
  • Wrap up

VersionOne Introduction

VersionOne is an all-in-one agile management tool that can quickly adapt to any agile software development methodology.

Indeed, it is an instrument that offers a sound planning and tracking platform to support agile development as a bottom-up approach. VersionOne has embedded Quality Assurance as an essential part of the whole software development process.

VersionOne Team Edition

Benefits

  • VersionOne facilitates an end-to-end agile platform to plan and track all of your stories, defects, tasks and tests.
  • It gives you easy access and visibility to work with several teams and many projects at the same time.
  • It has unified the software development, the delivery, and the workflow setting in a single package for its users.
  • Also, it supports the integration with many different programs such as Bugzilla, Cruise Control, Eclipse, HP QuickTestPro, JIRA, Microsoft Project, and Microsoft Visual Studio.

Also read: Using JIRA for Agile project management

All Editions

You can use any of the four VersionOne Editions that suit your software project management and testing style and the needs.

The significant and specific features of each of the four editions are consolidated below figure.

  • Team: The maximum of 10 members can work on one project.
  • Catalyst: A team of up to 20 users can work on several projects.
  • Enterprise: Many users and teams can work on different on-going projects.
  • Ultimate: It has full access that an enterprise level organization might need.

VersionOne All Four Editions:

(Note: Click on any image for an enlarged view)

versionone four edition

As far as acceptance and regression tests are concerned, the Ultimate Edition of VersionOne is designed to integrate them. VersionOne tracks the acceptance tests by their status, time and result. And you can use the regression tests as the templates for acceptance tests.

VersionOne Installation/Setup

You have cloud set up of all four editions for trial. To sign up, click on Team edition from here

When you submit your sign up information, you will be given the URL for signing into VersionOne Team Edition. You can follow the same process to gain access to the other three editions- Catalyst, Enterprise, and the Ultimate.

Login

After installation/setup, you would need to enter your ID and Password.

Login page

versionone login

Getting Stated

The first tab you see in VersionOne is Getting Started. It gives you an overview of the major features of product planning, release planning, sprint planning, and sprint tracking.

Specifically, it highlights what you would do as you go through the execution of the test. You add stories, create and plan release, sprint planning, and track your daily progress.

Administration setting is on the right side of the application for easy reach of the users (the administrators and the team members). Besides, there are many standard Agile reporting metrics such as Release Burndown, Sprint Burndown, Velocity Trend and Test Trend.

Getting Started Screen

Versionone getting started screen

Admin

As you are at the beginning of your project/test setup, you can add additional members/users as you need to the member’s list by clicking on the Add Member tab. The new member gets added, who you can assign to any specific task later as you work with sprints on the stories and defects.

Add Members

VersionOne Add Members

Project Settings

Once you insert the members, click on the project for creating a new one. You can give a Title for the project, specify the Level of the project by adding Description, Begin Date, End Date, Owner, Total Estimate Points and any other information as you may need at this stage.

New Project Creation Page:

VersionOne Add New Project

Member Name

You would see your name as a member on the right side of the application. When you click on your name, you see below functions

  • Member Details: It has all the details about your stories, cases and the projects on which application you are currently working on it.
  • Password: You can change your access password to VersionOne
  • Applications: This function offers you the facility to add any application that you want to have access via VersionOne. Once you add the application, the system gives you the Access Token for it
  • Logout: Normally, this is for you to log out from the application

When you complete the preparation and setup, you are ready to get into the core testing activities by clicking on the product planning page.

Core Project Management Activities

#1) Product Planning

It is your first practical step towards organizing your backlogs and ranking the stories as you need for executing tests.

You can build your backlog by managing the stories, test sets, and the defects as you keep updating your work items. Product planning gives you helpful resources such as estimation, associating your work to an Epic, ranking backlog when there are numerous such stories, defects, and tests.

You can add stories and defects as many as you need or access them from any project or sprint. Filtering allows you to drag and drop any item from the backlog for prioritization purpose.  Stories can be imported from excel sheets or created directly from the Add Story Inline menu situated on the right side of the Product Planning page.

The picture below shows the main page of the backlog where you can organize the stories by title, ID, Priority, Estimation point and project.

Product Planning Screen– Backlog

v1 product planning

Backlog Importing Page:

Download the Excel Template by clicking Import from Product Planning tab. You can fill it out with your test scenarios, test cases, test data, and other relevant columns based on the needs of each module of the Application under Test (AUT).

You can go through the same steps for Defects and Issues. If there are any issues during upload your excel sheet, VersionOne tells you what particular column or row have to be corrected to complete the upload process.


v1 backlog import

When you click on Add Story Inline, you will see a drop down menu that has the functions for add story and defect.

After you click on Add a defect, the below window will pop up for logging the defect where you can add the title, sprint, description, estimate points, owner, status, priority, and type.

Add New Defect Page

VersionOne Add New Defect

For reporting purpose of the backlog items, there are various types of reporting templates you can generate, as you need.

Few of the main types of the metrics are as following:

  • Road Map
  • Portfolio level
  • Story Velocity
  • Work Items

#2) Release Planning

In this feature of VersionOne, you can move any backlog story to any of the releases. Release planning offers two approaches namely, Tactical and Strategic. In tactical release plan, you schedule each item, defect, and test individually at backlog level. While in strategic approach, you anticipate the backlog at the portfolio level.

Besides, this feature offers the possibility of regression planning that lets you describe and map out coordinated sets of testing activities for making sure your existing functionality continues to work.

It is always recommended to have your schedules short in duration by using as many sprints as you can. One of the primary rationales behind release plan is to be able to track the teams and the release deadlines via effective communication.

There are two methods you can move backlog items

  • Check the check boxes for multiple stories at a time from Move to project
  • Drag and drop them where you want

Simultaneously, you can add new releases to the project as you work on the current ones. The project Burndown shows the overall status of the release in terms of time.

Release Planning Page

v1 release planning

For Sprint release, you can view tests report metrics to measure your progress towards the completion of the sprint.

They are mentioned below:

  • Portfolio Item Dependencies Report
  • Release Forecasting Report
  • Standup Dashboard Report

#3) Sprint/Iteration Planning

Here is where you choose what items of the backlog are to be worked on for a particular sprint based on your priorities. Then, you break them into specific tests and estimate the efforts to get them completed.

An effective estimate is to look into the team’s past performance levels and progress and get an idea of the current work to be done. The primary functions in this stage are mentioned below

  • Activating and Deactivating a Sprint
  • Closing a Sprint
  • Creating/Adding a Sprint
  • Deleting a Sprint
  • Managing Sprint Relationships

After you scheduled your work by using Sprint/Iteration scheduling and the planning capacity, the team members get tasks assigned to them. The team can decide which item of the backlog should be worked on at first and schedule execution.

You can drag/drop each item you want, or you can do that by going through multiple selections of the item, and you move them together into a sprint or a project. You would see the details of the prioritized items under product backlog schedule as shown in the below screen.

Sprint Scheduling

v1 sprint scheduling

There are various types of the reporting metrics for sprint tracking, helpful for Scrum Masters, Team Leads, Team members, and the stakeholders. The major types consist of the following

  • Cumulative Flow by Status Report
  • Member Load Trend Report
  • Pipeline Run Contents Report
  • Quick list Reports
  • Sprint/Iteration Dashboard Report
  • Standup Dashboard Report
  • Test Runs Report
  • Velocity Trend Report
  • Work item Cycle Time Report.

By clicking on sprint tracking tab, we step into the execution of the tests.

#4) Sprint/Iteration Tracking

Once you create the tests, it is now time to execute your tests. You would see what you have to test and update stories, tests and the defects on a daily basis. You can go through dashboards to view status and progress. Key agile metrics, the status of each story and defect are available for viewing in the standard dashboard.

You can just drag and drop each of the stories and defects as you execute them.  It gives the overall picture of how a team is doing regarding running the tasks and the tests. Following describes what you can do in the Sprint Iteration section.

a) Detail Tracking

You would see all your open work in this selected sprint including updated time and the status.

b) Member Tracking

This page shows the list of all team members assigned to their specific sprint. It is a list that indicates the relationship between the testers and the assigned tasks.

Sprint Summary for Member Tracking:

v1 sprint summary

c) Storyboard

This page displays a visual view of all stories included in a sprint. It provides you a clear picture of the stories which have them in the columns of None, Future, In-progress, Done and Accepted.

Storyboard Page

v1 story page

d) Taskboard

It shows a visual status of the tasks grouped by defects and or by tasks. You can display the view below during the team’s daily meeting for giving a clear picture of the overall progress of the work.

v1 taskboard page

e) Test board

This page displays acceptance tests grouped by backlog item for e.g. defect or test status. It shows the individual test status during the testing cycle.

The reporting metrics for sprint tracking include the following:

  • Member Load Trend
  • Work item Cycle Time
  • Velocity Trend
  • Sprint/Iteration Burndown
  • Standup Dashboard
  • Test Trend
  • Test Runs
  • Cumulative Flow
  • Effort Quick list

Velocity Trend

It displays the status of two established sprints for testing. You can produce the reports by showing the Team, Feature Group, Start Sprint, End Sprint, Work-items and Aggregation type. Then, you can turn it into PDF, or you can print it.

v1 velocity trend

Wrap up

VersionOne is a single platform where you can plan and track all your testing work items with greater visibility across different teams, projects, portfolios, and stakeholders. It offers DevOps enabled Application Lifecycle Management Solution.

The figure below illustrates the overall workflow and the main features of VersionOne.

VersionOne Workflow at a Glimpse:

v1 workflow process

Conclusion

We do have many Agile Project Management Tool available in the market. VerisonOne is the one of the best among them.

By going through this article we will get a clear idea of VersionOne tool.

About the Authors: This is a guest post by Haroon and Noorullah, both having extensive experience working on Agile projects.

Please leave a comment if you experience any problems during this process.




Recommended reading

3 comments ↓

#1 Thota Raj Sekhar

Excellent work. I am working in VersionOne and i figured out it does not have twin filters like in JIRA. For example if i want to see tasks that are in In Progress and Done. I cannot do that. You can apply only one filter at a time.

#2 Machhindra Eknath Walhekar

Dear sir.
I am MCA 2015 passed out. i Know very well Networking and software developement. Pls kindly refer my name.

Thaks & Regards
Machhindra

#3 Kalpesh

nice detailed tutorial on VersioOne. It’s a good Agile team management tool you should try.

Leave a Comment