TA is an IT application supporting cross-functional case management. The goal for TA for Scania was to have a solution for planning, case management and visualisation.
Scania needed a practical handling of information and document sharing, but also a visualisation of work and progress. Since Scania is a large organisation, with a lot of teams onboard, TA was crucial to handle operational value systems and making sure that everyone worked in the same manner, now they can work in a more structured and agile way. There is a great overview and the search functionality for work items is fast and used a lot. Users can also create their dashboard easily. More responsibilities are now directly on the user, and they can plan their time accordingly.
What brings you back to Taipuva Polarion Days?
– It’s interesting to meet the different people working with the same support issues or how to set up different configurations, and you learn a lot. Here you’ll get personal contacts and general knowledge.
What was your presentation about?
– I talked about our implementation and the use of Polarion at Scania. We have 5 000 users more or less, and that’s a very special challenge. The key benefits so far have been that it has been easy to configure it and we have had more or less no downtime, Polarion has been very robust. There have been challenges also, for example, our maintenance organisation has been a problem, but that has nothing to do with Polarion.
What’s your vision of Polarion within your organisation?
– I think that we would like to start to apply more of the out-of-the-box features that Polarion has, but to do that we need more resources. I appreciate trying to implement the out-of-the-box features because they are easy to implement, you don’t need to develop them on your own. So if we just get the resources, then we can do it quite quickly.
In what areas do you use Polarion?
– We use it within R&D, not in production, and it’s mainly case management. We also use Polarion when it comes to tests and requirements. I think we use more or less all of the features in Polarion, but not all over in R&D.
What are the key benefits?
– In general, if you compare it to 20 years back, web applications today are much easier than the software 20-30 years ago. It’s much easier to handle and easier to work with, and I think that emphasises the benefits. To change or to dare to go forward and apply for example Polarion.
How do you see Polarion being a part of your organisation in the future?
– Since we are growing, we would like to take Polarion to all our new stakeholders, which are international stakeholders in the US and China mostly now. I guess that will be a large challenge coming up, let’s say for maybe two or two or three years to come.
What’s the purpose of Taipuva Polarion Days?
– I hope from Taipuva’s point of view that you could inspire people and that it will of course lead to business in the long run. I think it’s a really good idea and it’s a lot of goodwill as well to be invited and have this possibility.
Are there any key learnings you would like to share for more recent user organisations?
– I think you need to have a maintenance organisation and, and be careful with the way you set it up and take that seriously because that’s needed in the long run.
What is your relation to Taipuva and what has been the importance of the knowledge capability from them?
– They took quite a large part of the configuration and information when we started up and since it’s been like four years now, we’ve had some personal contacts and relations and I think that’s great.