Kuadriga uses Jira, Greenhopper and Zephyr for SCRUM testing
Kuadriga is a Danish-owned IT company with Scandinavian management style. It was founded in 2008 by Jesper Lindholt in cooperation with a group of Danish investors. Having started as a Microsoft-focused company, it gradually came to specialize in all areas of software development. Kuadriga provides outsourced development services from its development center in Kyiv, Ukraine.
Today I had the pleasure of speaking with Vladimir Prymakov, Kuadriga QA Manager who provided a very detailed analysis of how Jira, Greenhopper, and Zephyr for Jira allow his project teams to incorporate SCRUM testing into their Jira workflows.
Q: Can you tell us a little about Kuadriga?
Sure, the company started in 2008. We use a combination of industry expertise and technology to provide clients around the world with custom software development services.
Q: What type of products does Kuadriga develop?
We develop a wide range of products; web, desktop, mobile and other applications for financial, marketing, insurance, medical, and other industries. Technology choice is mostly justified by clients’ preferences and our suggestions. We take into account the value the technology can bring to the projects.
Q: Which Atlassian tools do you use and how did they make their way into Kuadriga?
Now we use Jira, Greenhopper, and other Atlassian tools. We have much experience with many other tools, such as Microsoft Project, Trac, Bugzila, Mantis, RedMine, Podio and more. We tried Jira and Greenhopper on recommendation of our new colleagues on one pilot project. The experience convinced us that these instruments solve most issues in agile development and management. Since then, Atlassian solutions, including Zephyr, became standard and default in Kuadriga.
Q: Before Zephyr for Jira, what tools were you using for testing?
We used TestRail and Excel for test management. Now for the projects maintained in Jira, we decided to use Zephyr add-on. It enables us to have everything in one place and tightly integrate testing in the development process. In addition, advantages of Zephyr are an easy way of tracking test coverage, monitoring testing results, storing cycle history, convenient and easy test case management, etc.
Q: Specifically, what challenges was the team wrestling with the previous approach?
Well, when we used Excel, the main challenge was that we had to provide concurrent web-based access to test matrices and the corresponding test cases, link them to requirements, bugs, etc. Also, a lot of time was spent on manual activities. With TestRail, we spent more time on switching between tools. None of the other tools provided us with such an easy way of linking tests, bugs, and requirements, as Zephyr for Jira.
Q: There are several test management solutions out there, why did you choose Zephyr for Jira?
Here are the main reasons:
Integration Inside Jira: This is huge. As testers, we live in Jira, as well as developers, business analysts, and designers. Using Zephyr for Jira, we don’t have to switch between tools to manage testing any more. Also, we can easily link tests to requirements, user stories, bugs, and vice versa, which increases traceability a lot.
No Learning Curve: We do a lot of collaboration with the development team in both test creation and test execution. Because developers already know and use Jira, transitioning to Zephyr is seamless for them. It goes the same way for the testing team using Jira.
Just Enough Metrics: We are intentionally light on the process, documentation, and reporting. We do just enough to get our jobs done efficiently. Here are the key metrics we get out of Zephyr for Jira:
- Test Coverage: By release, by test cycle, by component, by defect, etc. Using labels creatively, we can implement literally any coverage scenario we need. These views of coverage give us just enough information to communicate our level of testing coverage, and analyze risks based on the development changes.
- Test Status: Through the various gadgets and dashboards in Jira, we get just enough useful information: test execution status by cycle and user, top defects impacting testing, defect distribution by test, and test execution burndown.
- Test Cycles implementation within Zephyr for Jira is pretty simple, straightforward, and effective.
The Price: The price for Zephyr for Jira is much more affordable compared to other test management tools with similar functionality and quality.
Q: In terms of measuring the benefits, how do you quantify the impact Atlassian tools have on your project team?
Primarily through utilization. We do not spend a lot of time on analyzing the benefits after the fact, but rather we ask ourselves the following questions:
- Do people use this product/feature on a daily basis?
- Does it help them to do their job?
- What are the processes that do not work or need refinement?
Q: In terms of measuring the benefits, how do you quantify the impact Zephyr for Jira has on your project team?
Compared to our previous approaches, the scope of our testing and development effort with Zephyr for Jira dramatically decreased and the testing process became much more transparent and traceable. Also, our QA team is very happy to work with a professional tool that helps them do the job efficiently.