Product Owner, Software-Development, Salesforce Specialist (Sales & Service Cloud, CPQ)

Goal

In the project "weePay Terminal" an independent new app is developed, which can be distributed on payment terminals of the manufacturer CCV. CCV is a well-known terminal provider, widely used in Europe. CCV Germany is located in Au in der Hallertau and can be reached from Munich in about 1 hour. The app will work on the new CCV A920 terminal, which is only available since mid-2020. The terminal is based on a specially hardened Android called "payDroid" as well as its own, non-public, app store.

With this approach, the development of the wee marketplace and the networking of retail, online trade as well as sports and event venues can be implemented according to the plug-and-play principle. The payment terminal and the app are compatible with the cash register protocol ZVT. This means that every modern electronic cash register can be easily equipped with weePay as a payment and cashback function.

The challenges were:

• as a business development manager I did the marketevaluation including a RFP. Based on the decision-matrix I selected the best partner for the client. I negotiated a general agreement with CCV to fix all the financial and procedural processes from order-form to delivery of the terminal including provisioning and pricing
• as a Product Owner to define all the necessary User Stories to pass them over wo the development team. Afterwards steering the team and keep the client upto-date regarding the current steps of the development, getting feedback on a weekly public-review basis and aligning with the management
• as a IT Architect I had to align the general approach of implementing the app (“ZVT-proxy”, Frameworks, deployment-assembly, Build & Release, Integration in the banking-platform of the client, Provisioning)

Goal

As product owner I supervise and coordinate the further development of the sports&entertainment concept (application in sports stadiums, event locations, etc.) on a technical basis. This includes in particular the further development of the functionalities in the areas of locations, web and app. These include ticketing, access control, payment systems, prepaid charges, MobilePayment etc.

In detail, I guided the further development from the closed to the open, cashless payment system of the WeeArena in Bad Tölz. This includes all customer-touchpoints where a Customer wants to to a transaction.

As a link between developers, specialist departments and external partners as well as service providers, i form the communication interface.

Im creating the task packages for the further development of the access and payment system, define and coordinate the processing of business requirements with internal and external stakeholders, taking into account the customer experience and the technical feasibility.

I lead training and workshops regarding requirements analysis and problem-solving approaches of departments, the development team and external partners.

For external partners, i create specifications and for the developer specifications.

Goal

In order to increase customer loyalty and customer interaction as well as promote targeted cross- & up-selling, a brand app should be created - using the example of Subaru, with which Subaru customers can access value-added services around mobility and vehicles at any time.

Scope and Approach

The goal of the first version is to provide and test as small a number of functions as possible to the first customers. Afterwards, the functions that the customer considers relevant can be expanded and unused features can be rejected or improved.

The complete Stack was developed in a cloud-native approach to ensure a quick Time-to-Market. The whole backend was based on PaaS-Services (AppEngine, CloudSQL) and deployed with an GitLab CICD Pipeline which was triggered by commits to the GIT-Repository (develop/master).

Technologies
React, Java, Spring, GitLab (SCM, Continous Build & Delivery), Google Cloud Platform (AppEngine, CloudSQL, Cloud Storage)

Goal

Only EF-internal pricing data currently used for the calculation of sales and trade-in prices. External factors and regional differences are not included in the pricing-calulators. Current pricing is above marked value (trade-in) or below market-value (sales).

Scope and Approach

Develop a solid, dynamic pricing model with suitable PaaS-Solutions from the public cloud and let machine learing do the hard work of predictions. Add public availible data and Build APIs on top of this Data-Stack to let new Business-Products consume this data easily. Project is scoped as a MVP, focus on the Markets Germany, and Switzerland, load EF-Data and get data from used-car-platforms (mobile, autoscout, autosphere etc)

Technologies
React, Java, Spring, Google Cloud Platform (AppEngine, Cloud SQL, Cloud Functions, Google DataFlow), GitLab

Problem
While building up new digital sales models with a variete of new technologies, the customer needs a layer, which decouples the rapid-development from the stable and performant IT. To not interfer the stability, it’s best practice to separate the different IT-speeds.

Solution:

Build a layer in the public cloud (Google Cloud Platform), connect legacy-systems (one-way-communication in first approach) and build proper APIs on top of this Layer.

Benefit:

New Products will not influence daily business, new apps can be developed pretty fast

Tasks and Responsibilities:

• Ramp up a enterpriseready Organization in the GCP (Projects, Service-users, IAM)
• Ramp up a Development Team onsite & nearshore
• Setup a GitLab Server for Code and CICD Pipelines
• Establish a cost allocation model and billing process
• Analysis of current ITArchitecture and development of a target-picture together with the Core-IT-Team
• Development of a cloudnative ETL-Stack from Legacy-Machines (IBM OS/400, Oracle) to the GCP consisting of GCP-PaaS-Services (Cloud Storage, Cloud Functions, Cloud DataFlow, CloudSQL, AppEngine)