Company Portrait

Both every single FleetBoard employee and the teams of the company do their very best to ensure the success of our customers: starting with the product idea, specification, (further) development, quality assurance, testing via market introduction, implementation, personal customer and introductory talks up to competent after-sales support and assistance in the daily business routine. Here, the various departments of the company are given a face and are introduced with their employees, scope of functions, and tasks.

Innovation Management by FleetBoard

Each time you take a glance into the driver's cabin of your truck, you ask yourself: "How do they develop something like that?" And what you mean is the black, small FleetBoard TiiRec? Well, this is done by some clever brains in the development department of FleetBoard. This is where products are born which will support you later on in your daily business. As a matter of fact, the development department of FleetBoard no longer consists of a few clever persons by now, but has grown to a team of 30 developers, who fully commit themselves to the demands of their customers. They are supported by a complete team for testing and quality assurance. As it would be expected from an ISO-certified company, the development projects are carried out within a framework of professional processes and structures. The development process from the idea to the implementation is a very complex construct of requirements, road maps, release plans, etc. But it all starts with the idea, which triggers off the development process. First of all, each idea is documented in a database to make sure that nothing will be lost. The existing ideas will then be used to describe new products and product changes, which will be systematically evaluated and scheduled for implementation. This is where the job of the developer actually starts.

All relevant requirements are systematically evaluated in the FleetBoard product development process and are scheduled for implementation. At FleetBoard , the development procedures are performed in the so-called “Scrum” model. This is an iterative process management model, where the developers are working in interdisciplinary teams. This means that the team members control their scope of work themselves. From all project volumes planned for a release (product backlog), the developers select those volumes (sprint backlog) which they think can be processed in a 4-week cycle (sprint). At the end of four weeks of development work, there will be a product increment ready to be used, which can already be subjected to the first integration tests. This process makes it possible to identify deviations from the project plan and quality problems in good time and to counteract them. At the end of such a sum of iterations, there will be the product which will be introduced on the market after intensive quality assurance measures have been taken. As a rule, market introductions take place twice per year, while an introduction spans 6 to 8 months from the planning to the implementation phase. The basis of the development process is the "Scrum" process management model, which divides the process into small sections, so-called "sprints". This development method does not only offer benefits in terms of transparency and quality, but is also well accepted by the employees involved. Split up into four Scrum teams, developers coming from different technical departments cooperate in the implementation of a project – from the specification up to the run-capable product, which has very positive effects on the flexibility, motivation, and commitment of the persons involved.

“The advantage of the Scrum model consists in the fact that the development teams have an influence on the packages to be processed. This makes it possible to take customer requirements and wishes voiced during the process into account and integrate these demands into the procedure,” says Mehmet Arziman, IT Implementation / Scrum-Team Green.

If a release has been finished, the benefits of the innovations will not only be enjoyed by new customers and in new vehicles, but also – depending on the hardware used – by our existing customers and their vehicles.