Tooth Fairy

· 245 words · 2 minute read
Photo
Photo by Lisa Peh on Unsplash
Developing a service on OpenShift

Our client had a software which calculated the best available policy for health insurance of potential customers. A big part of the business logic was dedicated to calculate policies for teeth. This part was a C++ monolith developed and maintained by a single developer. Unfortunately, he perished before he could pass on his knowledge to other developers. The customer fruitlessly tried to decipher the ancient monolith, but gave up after a couple of months and decided to rewrite the whole thing from scratch instead. Alas, it was our responsibility now. The customer hired us, a whole team of our company, including a Product Owner, Scrum Master and three developers. Our task was, not only, to extract business logic from the insurance specialist department and pour it into code, but also to document it well, to prevent that the knowledge of tooth policy calculation would not again be lost to oblivion. We even spent a day at the call center to get insights on how the agents would use our software.

Challenges 🔗

  • Understand domain
  • Understand business use case
  • Talk to stakeholders

This was quite a challenging project, not technology wise, but process and social wise. Due to the regularities of the insurance industry everything took longer than expected. Also, we had to travel 12 to 16 hours in total every week in the beginning, and every two weeks later in the project.

My Contribution 🔗

  • Design and implement software solutions
  • Present solutions to the customer