As far as consultancy companies go, Acando is one of the leaders. With bases of operation in Sweden, the USA, South America and further afield and boasting business partners such as SAP and Microsoft, Acando tasks itself with confirming the integrity of clients’ operations and ensuring that each commitment provides a quick impact and measurable results.
Acando identifies and implements sustainable business improvements through information technology while providing a balance of high business value, short project times and low total cost. Acando create measurable improvements by developing processes, organization and IT to strengthen the client’s business.
Acando is graced by a hugely broad customer base which includes small and large companies and public organization, an annual revenue of approximately SEK 1.5 billion, and around 1,000 employees in five countries in Europe. The company is listed on the NASDAQ OMX Nordic.
Acando has been using ReQtest since September 2011, and at the moment has 55 employees who regularly use ReQtest in their day to day operations.
We spoke to Erik Ringqvist who is a project leader at Acando, about how ReQtest is used and perceived at Acando.
As project manager for various development projects at Acando, Erik has used ReQtest for several different projects during recent years. Erik is of the opinion that ReQtest is easy to learn and to start with, and as a user, it’s easy to be in control of ReQtest’s everyday use.
Acando’s journey with ReQtest started with a project a couple of years ago in which they only used the bug reporting module of ReQtest. The project was large and complex with distributed teams in several locations over Europe.
In the project that Erik is currently leading, development and requirements management is conducted in Sweden while requirements managers are located in the USA and South America. The tests are conducted in Finland and Sweden. ReQtest has infinitely helped this cross border collaboration and the general opinion within the project is that ReQtest is super easy to use.
Erik went on to say, “In a project this large there are obviously those that have experience of other tools. As a matter of fact, our customers had chosen HP’s Quality Center as their standard tool for bug reports. Given that I had such a positive experience of ReQtest from my previous projects, I made sure we got a waiver so that our project was allowed to use ReQtest. I remember one conversation with one of the senior testers who was highly experienced in QC and really liked the tool. Before trying our ReQtest she was really skeptical, but shortly thereafter she told me ”ReQtest is so easy to use, no further explanation is needed.” And when she compared ReQtest with QC she realized that QC is much messier and that you as a user lack the control you need.”
The system Acando are developing now is for one of their global customers. The project is run Agile and Acando handles the entire project in ReQtest.
The Acando team appreciates that ReQtest is so easy to perform regression tests in; essentially just putting together testing in test runs and distribute them to different testers. ReQtest is also much loved by the Acando team as it makes it easy to follow the progress, easily uncovering if the test case is passed with OK, failed, not applicable or not run.
As a parting shot, Erik had the following to say of the requirements module in ReQtest, “Even those who write requirements find it easy to work in ReQtest. They like the requirements tree and claim that it’s so easy to add new values to fields. We are extremely diligent in using the comments feature to post comments to requirements. The requirements module in ReQtest is extensively used by the business side in the project to great effect.”
We here at ReQtest are just overjoyed that in little over a year, a company as huge and diverse as Acando has managed to not only adopt, but adapt and effectively use ReQtest to the best of its abilities. This is exactly what we built ReQtest for!