Complicated case? Complex case? The digital summiteers at konzepthaus Web Solutions know what to do!

Complicated and complex - not quite the same thing!

The snow glistens in the sunshine on the Allgäu mountains. For konzepthaus employee and summiteer Georg, the situation is clear: this weekend, he's heading up high on touring skis. He has to plan everything in advance: Some things could be complicated, such as determining the time it takes to get there. There are guidelines, detailed maps and other specific information. Georg can also draw on his own experience. So everything is easy to plan and predict.

The next step is to check the current avalanche situation: the most accurate forecast possible is now required. But the matter is too complex for a one hundred percent forecast. Georg has to be prepared for surprises in this area at all times. This is because wind, clouds, old and new snow, among other things, are involved in numerous components that influence each other in unpredictable ways. The meteorological causalities are usually only roughly known. A one hundred percent forecast of how the interaction of all the factors involved will develop on a particular peak in a few days? There is no such thing. For Georg, this means that the risk of avalanches cannot be completely planned or controlled. He has to obtain the most accurate information possible, but remain flexible: Even at avalanche warning level 1, drift snow avalanches can occur. And then there ́s only one thing to do: spontaneously reschedule and take other routes.

What makes software development so complex?

For us digital summiteers at konzepthaus, some digitalization projects are very similar to planning a tour for the weekend: Some parts are "only" complicated, while others are complex or unknown. And depending on the situation, no clear and long-term valid schedule with clearly defined output can be created despite all the expertise. In software development in particular, it is simply impossible to predict which program will run smoothly straight away or where error analysis will be necessary . And work on the overall project can often only continue once individual parts are working perfectly and are complete in themselves. Projects are also dynamic per se: customer requirements change? Of course we respond to this. Software updates come onto the market? We welcome and implement quality improvements. Goals need to be expanded or redefined? We are open to this and develop customized (digital) solutions.

What does this mean for project planning?

We clarify the situation and find the best way forward! The Stacey Matrix, for example, helps us to do this. The Stacey Matrix relates the level of requirements of the upcoming (sub)project to the choice of solution approach.



Source: Stacey Matrix, HubSpot

This provides a simple and at the same time very effective basis for discussing how to proceed in individual cases. Will we achieve our goal better and faster if we take an agile approach to the project, for example on the basis of SCRUM? Or will a classic approach such as the "waterfall principle" be more effective in achieving the desired results? Are the two not one hundred percent consistent?

No problem for us, we also work hybrid and combine different elements and styles. And regardless of the chosen method or other tools, strong teamwork, efficient communication and a regular, open exchange are among the great strengths of konzepthaus. Because what counts for us is the result, and here we are very demanding! We adapt the strategy, the planning horizon and the necessary measures accordingly.

After all, we want to reach the digital summit - with optimal planning and preparation. But we are always flexible and agile enough to tread new paths if it means we can make better and more effective progress.