Sign in

Use of PRINCE2® by Scheidt & Bachmann GmbH

Case Study

Use of PRINCE2® by Scheidt & Bachmann GmbH

Case Study

  • Case Study
  • Project management
  • Project planning
  • Project progress
  • Processes

September 29, 2015 |

 15 min read

  • Case Study
  • Project management
  • Project planning
  • Project progress
  • Processes

All of our White Papers and Case Studies are subject to the following Terms of Use.

In this case study, German systems development business Scheidt & Bachmann GmbH describes how PRINCE2® helped them deliver a project to develop hardware and software for rail ticket vending machines for rail company Bayerische Oberlandbahn.

The case study is also available in German (PDF, 1.6MB).


Scheidt & Bachmann GmbH describes how PRINCE2® helped them deliver a project to develop new hardware and software to install 64 ticket vending machines for the rail company Bayerische Oberlandbahn. Among the benefits of using PRINCE2 they found that applying PRINCE2 principles and processes increased common understanding and simplified decision-making where differing priorities were involved. The use of PRINCE2 improved delivery and customer satisfaction in a project that, from the start, had challenging and immoveable deadline dates while introducing technical innovation.

Scheidt & Bachmann was established in 1872 and remains a family-owned company under Dr.-Ing. Norbert Miller, fifth generation of the founding family. With 24 subsidiaries, and more than 2,600 employees worldwide, Scheidt & Bachmann’s continuous growth and innovation is a testament to the stability of the firm throughout the years. Initially a mechanical engineering company, the organization has developed to become a global solutions provider.

The fare collection systems division was created in 1978 and is a global leader in fare collection technology. It is a highly skilled organization, backed by a state-of-the-art product range and technological innovation, allowing the company to deliver reliable and effective solutions to meet its clients’ specific needs.

Bayerische Oberlandbahn is a modern, forward-thinking, customer friendly rail operator and part of the Transdev group, formerly known in Germany, as Veolia Verkehr. The railway division of Transdev provides regional transport services throughout Germany making 40.3 million train kilometres available in 2013. The operational centre for the railway companies in Schleswig-Holstein, Saxony-Anhalt, Saxony and Bavaria is located in Görlitz.

The ‘Meridian’ railway, which opened in December 2013, operates on routes between Munich and Salzburg Rosenheim / Kufstein in South Germany and Austria. Meridian wished to provide state-of-the-art ticketing; offering added value to their customers, including a new generation of Ticket Vending Machines (TVMs).

What was the project?

2.1 Background

Bayerische Oberlandbahn wanted to create an advantage over their competitors, attract customers, and provide demonstrable added value for passengers. They chose Scheidt & Bachmann as a key supplier for the fare collection system because of our capability to produce a device tailored to their specific requirements in a challenging timescale.

New rail lines were to be operated by Bayerische Oberlandbahn and would open to the public in December 2013.

Scheidt & Bachmann received an order in March 2013 to supply and install new TVMs for the Meridian railway by 14 December 2013, the non-negotiable date for new stations to be operational. This posed a challenge to deliver a customer-specific new generation of TVM in time. The project required new design work and the production of a prototype device for customer approval, as well as significant software development.

2.2 Challenges faced

The project needed to deliver a solution which:

  • Met the European hardware certification (TSI PRM1) requirement to provide a rail system that offers disabled people the same access and opportunities to travel as other people.
  • Added a display showing customer real time information (RTI), such as train times, to the normal/previous standard TVM. This required redesigning the TVM to include a glass front.
  • Incorporated a bank note recycler.
  • Required new software to interface with the regional RTI system (DEFAS2) and also the tariff database provided by Systemtechnik GmbH.
  • Operated a complex tariff structure with eight tariffs including cross border tariffs.
  • Provided new features in the application and back office software to:
    Provide passengers with the ability to make seat reservations
    Incorporate the ability for the rail operator to define and offer vouchers
    Incorporate a customer loyalty scheme.

It was necessary to build productive and cooperative relationships with the third party suppliers providing real time train information and tariffs in order to produce an effective specification and to carry out integrated acceptance testing. Suppliers also needed to be sourced for the new glass front for the main display and the addition of a second display for the new generation TVM.

Image 1.1 TVM ticket machine

Image 1.1 TVM ticket machine

2.3 Project objectives

It was clear from the start that the main driver was delivery to acceptable quality to the fixed deadline for the opening of the new lines.

Scheidt & Bachmann saw this project as an opportunity to design a new standard TVM (model FareGo Sales ST|40) which could be offered to other customers. It was also important to demonstrate our capability to deliver a working solution to time, delighting the customer.

In the short term, the objective was to run a successful project and maintain customer satisfaction. The long term objective for Scheidt & Bachmann was to achieve additional sales of FareGo Sales ST|40, using Bayerische Oberlandbahn as a reference site.

Both short and long term objectives have been achieved: subsequent new contracts and projects have been won in the difficult and highly competitive German TVM market as a result of our ability to deliver to Bayerische Oberlandbahn.

2.4 Project Approach

At the start of the project the project manager undertook product based planning involving all teams who would contribute (design, production, development and quality assurance) to identify what outputs were needed to achieve the final deliverables. The project was subsequently split into 11 stages.

A project organization structure was agreed, with six separate teams working concurrently, see Figure 2.1.

Figure 2.1 Project Organization

Figure 2.1 Project Organization

2.5 Key milestones

See Figure 3.1 for the timeframe for the project stages. The project milestones were:

  • Order received March 2013
  • Functional specifications produced and agreed by the end of April
  • Approval of hardware prototype – beginning of September
  • Installation start beginning of November
  • Final software approval – end of November
  • Go live for all TVMs on 14 December 2013.

2.6 Why PRINCE2?

The operations management of the Fare Collection Systems business division started a process to professionalize project management in March 2010. The aim was to strengthen project management to benefit ourselves and our customers.

Increasing the number and the complexity of projects posed significant challenges for the project managers. The company chose PRINCE2 as it provides a standardized guidance and process framework. It was also evident that following PRINCE2 would encourage a controlled environment with clear responsibilities, focus on controllable stages, coherent standards, and a homogeneous project language.

The anticipated advantages included:

  • Assurance that projects are managed according to an internationally recognized framework
  • Structured responsibilities and roles for the management of projects
  • The division of a project into management stages with board meetings, leading to a higher transparency about the project status and current challenges
  • Provision of a set of tools and standardized documentation to ensure all aspects of management are covered
  • Focus is maintained on the customer’s interests and the business case for Scheidt & Bachmann via the project board.

2.7 PRINCE2 implementation

After completion of the development project for the integration of the method, the Scheidt & Bachmann internal Centre of Excellence (CoE) was set up to take over from our specialist consultancy, Copargo. The CoE was appointed to provide specific support, to monitor the performance, to set standards and to institute continuous improvements.

It was decided to manage the Bayerische Oberlandbahn project according to PRINCE2 with management by stages and utilizing standard documentation which is well established internally. Some of the project specific PRINCE2 adaptations included:

  • The governance of the project was comprised of an internal project board holding very senior posts in the organization, monthly reporting, customer reporting, bi-monthly customer meetings including customer representatives from group level as well as Bayerische Oberlandbahn project management and technical representatives.
  • In addition to formal end stage reviews, which included approval of the plan for the next stage, we adhered to established ISO processes for hardware development and internally devised software quality assurance processes which follow best practice including quality assurance (QA) gateways.
  • During the testing phases, QA reports were produced showing the priority, severity and acceptable levels of occurrence of errors. The tolerances were agreed with the development teams, QA and the customer during the design and specification stage. This ensured prior approval for acceptability from each party and minimized dispute at crucial points during the project.
  • Risk assessment and management were covered by general meetings with the customer and internal reviews. The project manager operated as risk manager, and risks were documented and assigned owners and actions. The biggest risk was to the delivery deadline because of the amount of new development needed on the hardware and software. A risk management meeting was held early in the project, which included the customer and sales representatives, where it was agreed that the risk should be mitigated by reducing the scope of the deliverable by December and splitting the delivery into two main phases.
  • Change control was necessarily tight, ensuring that all changes from the stated requirement were identified and discussed, the impact assessed and action agreed. All changes were registered irrespective of their impact on the project deliverables, timescale or cost. 13 changes were identified in the project timeline. Focus on the business case ensured a win/win with the customer: a collaborative approach ensured that their priority objective was met.
  • Our customer had established their own internal communications strategy for their stakeholders and our communication throughout the project was constructed to assist this.
  • A regular fixed meeting date was established with team members and maintained through the software development phase to assess progress and identify issues enabling fast provision of information to the customer and rapid decisions.

2.8 Quality control measures

Because a clear and comprehensive specification was signed off during the first delivery stage, only one significant change was identified, which was agreed through the change control process.

Clearly defined acceptance criteria were included in work packages so the team managers/members were clear on what the end result needed to be. Test scripts were agreed for development testing as well as QA testing with established feedback reporting. These were also used for software acceptance testing with the customer.

Hardware acceptance testing was performed on a prototype TVM.

Within our project schedule, several ‘Super Milestones’ were identified, which recognized significant goals to indicate progress towards the final deliverables. These included bill of materials handover to production, hardware and software acceptance testing, delivery of TVMs, and installation acceptance.

Monthly reporting kept focus on milestone achievement, budget versus actual spend and customer satisfaction. Our standard reporting gave specific measurements for Red/Amber/Green (RAG) assessment and any item categorized as red required a separate issue report to be issued to the board.

To ensure adherence to the PRINCE2 processes, the project published measurements that showed availability and currency of key products. This was auditable by Project Assurance.

2.9 Challenges faced during the project

Software development was carried out in Slovakia, but managed from Germany. This required on-site visits, many telephone conferences and weekly progress reports to the project manager (PM).

Having sourced a supplier for the glass front for the TVM, there was a production failure at the prototype stage which took time to resolve; we communicated with the supplier to understand technical challenges and timescales. The project manager was able to alert the project board to a potential delay and having such senior people involved meant that Scheidt & Bachmann were able to adjust our production schedule to allow more time for the glass fronts delivery. We also reserved a second installation team and sanctioned additional cost to work overtime in production so we could still meet the desired go live date. As part of the risk management, we also identified a fall back position to have a steel front installed, and instituted a daily delivery report which we shared with the customer to track production of hardware. It included a daily review of risk and a go/no-go on the fall back plan. This ensured that the customer and internal board were kept abreast of the issue and that focus was maintained throughout the organization.

2.10 Capturing lessons

Lessons learned were recorded throughout the project and 33 were documented with recommendations for future projects to avoid or reproduce. Here are some examples:

  • For complex projects, the initiation stage requires involvement from the sales person who has been working with the customer, to build on that existing relationship and to introduce the PM with time to build trust.
  • Writing good specifications means change management is easier and less divisive which maintains a good relationship with the customer.
  • There was initially poor transparency about the planned delivery date for the first TVMs, and this information was necessary for the customer to prepare for their operation (resourcing, training, marketing). The team manager for the production area initiated delivery reporting after the PM raised an issue with the executive who held discussions with department heads. In future, we would ensure that the production team are aware of the customer preparation needs and publish the communication strategy to all team managers.
  • The customer was naturally sensitive to press coverage. To ensure that we demonstrated our support in projecting a positive message for the implementation, there was a sizeable Scheidt & Bachmann team on site to allow rapid assessment and resolution of any final minor issues that arose.


3.1 What contributed to this being a successful project

The initiation phase allowed everyone involved in the project to plan what was needed, and to understand priorities, scope, time schedule and milestones. The product initiation documentation (PID) was available in a shared location and was invaluable in keeping the project on track when questions were raised regarding priorities.

A communication strategy that stipulated monthly reporting was important for keeping the whole team informed and involved, even when their part had not yet started or had been completed.

Formalizing work packages and ensuring that they were agreed with the team managers (for content, effort and delivery timing) ensured that teams understood exactly what was needed, when and how it would be judged.

Maintaining a risk register and reviewing it with the team ensured that potential hazards were identified as early as possible, and not forgotten. Where appropriate to the level of risk and impact, actions were clearly allocated and followed up on.

We used configuration management and created configuration item records specifically for documents requiring formal approval. This proved vital to see instantly whether a particular specification had been produced, reviewed and approved, as well as who was responsible for it. It allowed the PM to monitor this critical phase of the project very easily and helped to ensure that the key milestone of specification agreement was reached in the extremely challenging timescale needed.

A project scorecard, providing a simple snapshot, was designed to maintain corporate level interest. This one page update used RAG indicators combined with a short narrative to inform the corporate board of progress.

Maintenance of a formal issue register simplified prioritization and ascribed clear responsibilities for actions with expected time-frames. This register along with all other project documentation was centrally available and accessible to all internally. Splitting the work into clearly defined stages, (see Figure 3.1) with good understanding on all sides of what was being produced, meant that it was easier for us and our customer to confirm that we were on target to deliver, or to identify work streams that were starting to slip.

Figure 3.1 Meridian project stages

Figure 3.1 Meridian project stages

3.2 Benefits from this PRINCE2 project for Scheidt & Bachmann

Within Scheidt & Bachmann the project has set a good example for other projects with the
demonstrated benefits from establishing:

  • Consistent use of PRINCE2
  • A strong project team
  • Transparency between the customer, supplier and sub-contractors
  • Good customer communication
  • Cooperative relationships with the customer and suppliers
  • Good project documentation for internal and external use.

Other benefits for Scheidt & Bachmann have been:

  • Our new generation TVM is available and has been sold to other customers
  • We have gained another satisfied customer who is willing to do reference site visits (helpful in the German market)
  • We won the PRINCE2 Best Practice award for the best German PRINCE2 project 2014 - presented by BPUG

Image 3.1 Best practice award for German PRINCE2 project 2014 by BPUG

Image 3.1 PRINCE2 Best Practice award for the best German PRINCE2 project 2014 - presented by BPUG.

3.3 Benefits for the customer

For Bayerische Oberlandbahn, the benefits have included:

  • Very successful go live transition into business as usual. The devices were installed and operational in time for the line opening.
  • This helped to generate a positive message about Bayerische Oberlandbahn in the press.
  • Bayerische Oberlandbahn exceeded expected revenue in the first month; indicating widespread passenger acceptance of the new technology.

3.4 And for the future?

As a consequence of this project it is anticipated that the German market for ticket vending machines will be further opened up to Scheidt & Bachmann as more people hear about our successful project with Bayerische Oberlandbahn. This may lead to opportunities to generate service revenue from an extended client base.

3.5 What lessons would you pass on to others?

From this project we learnt some important lessons that are applicable to all projects:

  • Use the strengths of PRINCE2 to understand what the customer requires and also to handle the inevitable changes along the way
  • Work closely with your customer to obtain feedback especially where this information is useful for future improvements to quality which, in our case, was especially important around the ease of maintenance
  • Having a CoE that reviews star projects and can implement those lessons applicable to other projects has helped to disseminate what has been successful.


The project was very successful and delivered TVMs that were installed:

  • On time
  • With the agreed functionality
  • With the ability to introduce further updates and add on functions later.

Our customer feels that they can trust us because we communicated problems openly, managed risk well, and were flexible in responses. Although they initially were disappointed in the suggestion to split the scope, they accepted the principle of de-risking the prime deliverable of selling tickets on opening day, and with hindsight have confirmed that it was the appropriate action. They have declared the project a success.

Jürgen Kindler, project manager for Bayerische Oberlandbahn, said: “Due to Scheidt & Bachmann’s effort and determination we were able to complete the project successfully within the time-frame. Problems were communicated openly and solved quickly, which has greatly contributed to its success.”

Daniel Weber, Head of Technical Project Management at Scheidt & Bachmann, adds “I am especially delighted with the team that implemented the project successfully to meet the customer’s satisfaction.”

End notes

  1. EUROPEAN UNION RAIL SYSTEM: Technical Specification for Interoperability “PERSONS WITH REDUCED MOBILITY”
  2. Durchgängiges Elektronisches Fahrgastinformations- und Anschlusssicherungs- System (DEFAS) Bayern is an online travel information system for local and regional public transport in Bavaria.

Use of PRINCE2® by Scheidt & Bachmann GmbH