Software Development - how it started vs. how it's going

At the beginning of IBORN’s story, the focus of the whole software development department and the whole company was on only one project, but in a sense of how things were organized and how releases were delivered to clients, there isn't a big difference since then. 


The big change happened in the culture and in the iborn standards. Namely, back then there was a lot of back and forth between developers and QA team members when it came to bugs and how certain projects and features were tested. This caused a lot of problems regarding the focus of both the developer and the QA engineer as they had to switch between tasks, bug fixing, and re-testing again. As a result, we've created the process of SBE documentation which now is one of the IBORN standards when doing software development.

And as the company grew and we learned new things and technologies, now the whole development process doesn't just contain the actual implementation of the code but also automates the testing and deployment phases, delivering a more stable software without having too much manual testing, as well as monitoring for issues once a certain feature is launched for the clients.

As we already mentioned, the whole team was working on only one project, a legacy system from the insurance industry that needed to expand and open new business opportunities for the company. Due to this success, our Danish partners tasked us with two additional projects, but this time in the healthcare industry. 

This was a huge opportunity for us, as we had the trust in building a platform from scratch, which required migrating the medical cases from WebForms to MVC. This project is an ongoing one, as we are in charge of nourishing and expanding the platform with new functionalities and modernizing it with new technologies. In addition, we have developed a mobile app that is being used by their end clients, and both of them are being maintained actively.

Since the technologies used are changing constantly, we started with ASP.NET MVC, WebForms, Jquery, HTML, AngularJS, Ionic, and SQL while today we are using more on each project, such as .NET, .NET 6, Java, Angular, React, Elastic Search, SQL, MySQL, Postgre, CosmosDB, etc.

At this moment, we are already doing a lot when it comes to gathering business requirements, delivering architecture design, developing solutions, and providing support and monitoring. But in the future, we are looking forward to defining the IBORN standards as a project checklist. The documentation should include a full set of procedures from different areas such as requirements, architecture, security, coding standards, automated testing, deployment, and monitoring. 

on May 26, 2022