Our long-term experience from digitalizing the passenger transport industry enables us to help our clients to take the maximum out of modern information technology. Before and during the implementation of our products, we constantly advise our clients with the use of the best business practices, according to the individual goals.
We mainly offer consultation in the following aspects:
How we work
We know that clients don’t always have time and resources to manage their digital transformation process themselves. This is why Turnit has developed its product suite as an off-the-shelf solution, delivered as a full service.
Business consultation
- Managing multiple online sales channels
- Inventory management
- Pricing and Yielding
- Distribution and agents
- Best practices in infotainment
- Technical consultation for integrations and data migration
- Driver on-board operations
- Maximizing value from reporting and BI
- Marketing and CRM
- After sales and passenger handling
- Building and managing route network logistics
Implementation
Our implementation method supports both small and large-scale implementation projects. A typical large-scale implementation period consists of:
The kick off session
The typical implementation of our products starts with a project kick off, where we determine the nature and order of tasks to be undertaken. Depending whether there are any gaps between desired business process and existing off-the-shelf capabilities, we prepare a project plan, including optional development iterations, training and roll-out procedures.
This is typically 1-2 day workshop where the whole project team and the key members of the project team will participate. Among other practical goals, the aim is also to introduce team members to each other in order to create a better starting point for future electronic communications between the team.
The analysis
The goal of the analysis workshops is to identify in detail the gap between the existing product functionality and the client requirements. The analysis is divided into several workshop sessions, based on the different functionality groups in the product.
Development iterations
The typical implementation of our products starts with a project kick off, where we determine the nature and order of tasks to be undertaken. Depending whether there are any gaps between desired business process and existing off-the-shelf capabilities, we prepare a project plan, including optional development iterations, training and roll-out procedures.
This is typically 1-2 day workshop where the whole project team and the key members of the project team will participate. Among other practical goals, the aim is also to introduce team members to each other in order to create a better starting point for future electronic communications between the team.
The roll-out phase
The roll-out phase includes setting up the production environments, setting up and migrating the data, training the users, approving and releasing the system to live production.
Software development
For product back-end developments, we are using weekly sprints to plan the development in an agile way. In every 8-12 weeks, depending on the backlog, there will be a more major release. Besides that, ad hoc or customer-specific releases may happen meanwhile:
-
Tasks are planned based on client’s order number (given by client’s project manager).
-
Each client gets a percentage of development hours for each sprint (agreed on beforehand with a business manager).
-
Scope is fixed three weeks before the cycle’s end at the latest.
-
Tasks are done in development environment that uses a continuous integration and deployment practice, i.e. task is ready for Q&A team as soon as the developer is finished with it.
-
Q&A team has different testing environments depending on where we are in a development cycle.
-
After two development sprints, Q&A team will start testing in pre-live environment that lasts for one week (task based testing, regression testing and general load testing).
-
After that, the client can start testing in pre-live environment, one week is for testing and the last week is for end user training.
-
Pre-live environment will get bug fixes as soon as possible, but no new requirements will be implemented.
-
Acceptance is needed from client’s project manager one week before the planned release at the latest.
-
Cycle ends with a release.
Quality assurance
Quality assurance is our top priority because of the mission-critical manner of our systems. The life cycle of the product testing and quality assurance process consists of static and dynamic testing activities. Testing comprises planning (period of negotiation and analysis), preparation and evaluation of the software, and other related works. Testing is used to verify and determine whether the software meets the specified requirements, the client’s intended purpose, and whether the software contains any errors or problems preventing work.
Turnit’s principles of software testing are based on general and most commonly used standards, and they characterize the testing process of the company as follows: testing is an investigation carried out in every phase of software development with the aim of achieving awareness and collecting information about the product’s quality, reliability, and its errors.
Testing is carried out by a separate team of testers led by the test team lead. In addition, the testing team includes a lead tester, a technical tester, and software testers who are focused on functional testing. The latter are also expected to have analytical prowess.
Turnit’s testing process includes pre-testing activities, starting the testing, ending the testing, and the testing phase in which the product is delivered/accepted to/by the client. Our QA team is responsible of testing the entire ecosystem in relation with the product’s system including end-to-end system testing activities, which also includes front-end channels created by MC team and integrations with 3rd party systems.
The types of testing we use are following:
- Specification-based testing
- Integration testing
- Exploratory testing
- Follow-up/changes testing
- System testing
- Usability testing
- Regression testing
- Structural testing
Non-functional testing
- Performance testing
- Reliability testing
- Usability testing
- Security testing
Support services
Because of the critical manner of mass transportation industry, we provide 24/7/365 availability of the systems with constant support, including dedicated service times and guaranteed SLAs to our clients. The availability and performance of our products are closely monitored. We save live monitoring data in our monitoring systems for detailed statistics, which is available for clients.
Turnit service delivery follows the ITIL framework and covering the entire cycle keeping the service running, ensuring the continuous improvement of the service, and the system as a whole. Additionally, our processes are ISO certified (read more).
Support services consist of: