When you look at any app store you might think that there is an app or software solution for everything. But this is not true. Not every problem has a solution just yet. Moreover, some solutions do not fit the individual needs of a company. This is why we develop customized software - for all the unsolved software problems out there.
Three common reasons why customers ask us to develop customized software solutions
-
Automation: The customer wants to drive automation processes in the company as efficiently as possible. For this he needs an individual software solution. The software should take into account the specifics of the company while not being expensive.
-
Business or product idea: The customer has an idea for a new business model or a new product. He also already knows that he needs software that will help him to achieve his corporate goals. We help him to avoid getting bogged down. To this end, we focus on what creates value in software development and leave out everything that does not bring any benefits but merely costs a lot.
-
Technology leadership: The customer plans to retain technology leadership in a new market or a new business area - or wants to become successful in a new territory. This requirement often calls for a customized software solution that is a perfect fit for the business field or market.
Individual software with established technology
We build software with modern architecture - and with suitable and proven architecture patterns
-
We build web apps: SPA, PWA or with Electron. We primarily rely on Angular, React or Vue. When speed is essential, SSR is the choice for us with the help of modern frameworks such as Gatsby or Next.js.
-
For the backend we often prefer a conventional approach with a mostly .NET- or Node.js-based backend and a classic API. Serverless functions allow us to implement lightweight and cost-effective backends.
-
The database within the product is either relational or document-based. We have a long history as an Oracle partner with the Oracle database. However, we now often use MSSQL or PostgreSQL. With respect to document-based databases, we work with NoSQL databases - such as Azure Cosmos DB solutions, CouchDB or MongoDB.
-
We operate on iOS or Android either via Cordova or natively.
-
Our infrastructure runs on Microsoft Azure. This enables us to implement any application technically. We have a wide range of deployments for various compliance needs in Germany and the rest of Europe.
We start off with extensive consulting - not just with software development
For us, a new project doesn't start with the first line of code but with one or several meetings with the customer and extensive and detailed consulting. We do this because we want to understand exactly what the project is about before we get started. Only when we know your problem are we able to advise you on the best approach in the light of your financial resources.
Why is extensive consulting on agile software development so important?
We could just take the easy way out and simply get started. But our experience over three decades shows that this is a bad idea. It is much better and also much more efficient if we only develop as much - and for as long - as is appropriate for the product. That is why we take a lot of time to get to the bottom of your core problem. We then develop possible solutions on this basis: the software you really need. This is what customized software development is all about.
"Sometimes our customers already have very specific ideas about what they want. Sometimes they just have an initial idea. And sometimes they already have software but are not satisfied with it. We want to get to the core of the matter through extensive consulting.“
IT pioneer Detlef Pahl - Head of Individual Software Development OHB Digital Services
Close to the customer: Why we rely on agile software development
After comprehensive consultation, the agile development process is an iterative cycle and not a linear process without any possibility of intervention. For companies that have to assert themselves in an increasingly digital environment, this is a real benefit. With short cycles, you always have an opportunity of performing a check on everything:
-
Is the project headed in the right direction?
-
Are the ideas emerging at the beginning of the project still viable?
-
Have there been any changes in the basic premises underlying the project?
-
Have we gained any new insights that will advance the product?
-
Has the desired success been achieved with the versions that are already in use? If so, are we done? If not, what do we need to change?
→ With these checks you can respond to uncertainties in agile software development - without having to start from scratch again.
In the past we have questioned the clear ideas of our customer in many agile software projects. We will certainly do the same with your project. This "challenging" is not a purpose unto itself but yields better results. Because sometimes the rock-solid basic assumptions are no longer that rock-solid when you talk about them. The upshot is that the software project is often much simpler than initially assumed.
Agile software makes change controllable
Of course, there are also projects or products in which software development is very linear - from the seed idea to the final rollout. But the phrase “this is how it has to be and no other way is accepted” is increasingly losing traction, especially in individual software development. We have been observing this for a couple of years now.
"In the case of customized software, the proportion of agile software development is increasing significantly. From my point of view, that does not come as any surprise given the rapid change in the world. Companies have to respond quickly to a new environment. That works very well in an agile process."
IT pioneer Dr. Arne Gausepohl - Managing Director OHB Digital Services
The pressure on companies is growing. If they fail to implement the strategic projects within a certain (and usually short) period of time, the project “dies” - or the company is left behind completely. The Covid-19 pandemic has shown that there is a lot of catching up to do when it comes to digitization. Furthermore, strategic development processes are often too cumbersome.
Our theory is that you will be successful as a company if you manage to consistently focus on the right priorities, the right methods and the right technology. The losers are the ones that cannot change their business model quickly enough - and they cannot survive the change.
We build intelligent and clear software
Software always plays a role in these changes. It drives change and also makes change controllable. Today, we no longer program applications that only carry out simple tasks. Instead, we build apps that allow users to solve complex problems quickly. You should not only be able to make decisions swiftly but also do your work with software that you love.
The agile development of individual software products has obvious advantages
-
Agile software development avoids risks: In agile projects, we avoid unnecessarily rigid technical and contractual frameworks. If the environment changes during implementation, we can react very flexibly and avoid risks for the customer.
-
Agile software development avoids wrong decisions: In agile projects, we work transparently for the customer. Everyone who is involved can make the best possible decisions.
-
Agile software development avoids misdevelopments: We have had good experience with short feedback loops between the customer and the development team. This is how we avoid unnecessary misdevelopments.
"With today's web technologies, pulling up a project is a breeze. We use technologies that have outgrown their infancy and use them to build solid applications with a modern architecture. The applications feature a clear separation of responsibilities, solid database design and good cuts in the services."
IT pioneer Renee Rickling - software developer at OHB Digital Services
Not only Scrum: We also use these methods for agile software development
Agile software development: Methods like Scrum and Kanban often come straight to the table. But which agile method is the right one? Opinions differ on this. For some it is Scrum, for others it is Kanban. And if so, then it has to be exactly the same as the Scrum Guide.
We don't agree with that and don't think in terms of a specific pattern. Of course, we also largely rely on Scrum: short cycles, iterative processes and small steps. But we have adapted Scrum in a way that fits our needs. Because it is crucial for success to see yourself as a team that develops products in close cooperation. This is much more important than merely the choice of method.
Our teams practise agile values rather than applying a strict development method. The team decisions form the basis of a project or a team:
-
Are all people we need to get the project started on board?
-
Do we have the necessary resources?
-
Do we have a team that deserves to be called a “team”?
