Process models versus agility in theory and practice

In the system development, ways are always sought to simplify the complex processes and to give them a structure that is as intuitive as possible for structure that is as intuitive as possible for the user. Equivalent to traditional engineering and the control of company processes, process process models were already the approach many years ago to provide a better overview.

Nowadays, however, their significance seems to be changing more and more, especially in terms of their application in practice. Agile working methods are, despite their long history, particularly important again today.

Process models in system development

The complexity of systems is growing and growing, making it increasingly is becoming increasingly difficult during development. Nevertheless, in order to development phase and to achieve error-free systems with as few to achieve error-free systems with as few detours as possible, there are various models that standardize the developers' approach.

None of these fixed procedures has established itself as the definitive solution to the problems of system development. The familiar models, such as the waterfall model and the V-model or the phase model are all interesting approaches that both form a good basis for more modern models and are still used in practice.

But These models also have their weaknesses, which are not least due to the increasingly difficult to plan in the modern world. world. Smaller projects in particular, which seek new horizons, often elude any possibility of a clear structure, which makes it makes it pointless to subject them to traditional process models.

The importance of iterative models such as the spiral model already shows how the need for repeated adjustments in software development creates clear differences to traditional process management in analog industries.

Practical application today

Process models, that attempt to quantify the chaos of system development and divide it into clearly manageable, individual steps, are still of great importance in often emphasized problems, they are still very important in the software software industry.

Especially For large, stable projects with many contributors or even additional outsourcing, it is almost impossible to clearly structure the development phases so that everyone is on the same wavelength. wavelength.

In addition, well-known models still serve as the basis for newer approaches, which are adapted to current challenges with further insights. For example, the W model, which combines the original process phases of the V-model combined with more agile aspects.

So additional and earlier test phases are added in order to be able to to react earlier and faster to any necessary adjustments. and faster. The two visualized subcomponents of the model are extended are extended in such a way that various tests and simulations are various tests and simulations. These run in parallel and allow more flexible troubleshooting and adaptation of the product. product.

Furthermore Furthermore, the relevance of rigid models is becoming less and less not least because they do not allow programmers and system developers not leave as much leeway for programmers and system developers and are therefore less interesting. are less interesting.

So It is often the decision-makers in large companies who no longer are no longer in direct contact with the practice of development work who prescribe the adaptation of certain process models. This is done for reasons of economic security, which - at least at least apparently - is guaranteed by following systematic processes is guaranteed.

The relevance of teaching

In training of young system developers, knowledge of the process process models naturally still plays a major role. This will also continue to do so and is not just a relic of the fact that many industry giants enjoyed their own training at the enjoyed their own training at the height of these phase models.

The The modularization of system development processes is a complex that requires a better theoretical overview of the different situations different situations at each stage of the development process can be more easily understood.

Therefore It will therefore remain unavoidable that process models have their have their place in teaching. Breaking down the development development process into individual phases allows a more accessible to understand the respective challenges. On the On the other hand, it is generally not necessary to explicitly to know process models explicitly or have experience working with them to be able to apply agile methods.

Agility and modern practical relevance

To the To the detriment of classic process models, agile approaches have increasingly becoming the shooting star of systems engineering. developed. Although this trend has been in motion for almost 20 years and large parts of the industry have already adapted their approach adapted their approach accordingly.

In 2001 already the original manifesto published. The foundations on which this was based are still extremely relevant today and demonstrate well why it is by no means a short-term concept:

• Individuals and interactions are valued higher than processes and tools
• Functioning software is valued higher than comprehensive documentation
• Cooperation with the customer is valued higher than contract negotiation
• Reacting to change is valued higher than following a plan

The The principles are therefore based on thought patterns that do not have anything to do with software, but have arisen from practical experience in working with people. Instead of abstract concepts for the systematization of complicated processes, we take a step back processes, we take a step back and use individual, human and realistic realistic aspects as a maxim.

System development, that follows these recommendations is agile in the sense that it is capable of capable of much faster reactions to changes. Interestingly, this approach is now also increasingly being used in organizational management.

Tech start-ups understand this better

These changes, which affect the entire free market, can certainly be placed in the context of the widespread success of start-ups. In tech start-ups in particular, agile methods are preferred both in software development and in all other aspects of the company.

This is also quite natural, since a fundamental customer orientation is is often at the heart of operations in modern start-ups. operations. Both a dynamic response to new types of customer customers that go beyond the previous offering, as well as the basic basic offering of a product or service that addresses very specific market specific needs of the market express this. express this.

Also Focusing on functioning software from the early stages of development stages is extremely important for startups, as you quickly quickly as a trustworthy and capable business partner. business partner. So it's no wonder that Scrum and similar philosophies have prevailed in this sector.

An early prototype thus provides the perfect basis for negotiating for future cooperation and shows the customer that a functioning further consultation, a functioning desired product will be will emerge. The presentation as functioning software instead of a theoretical theoretical model is at the heart of this approach.

Something tangible will always have a more direct and effective effect on us, and even system development ultimately involves working with people. In analog product development, great importance has long been attached to creating a marketable-looking product, including high-quality packaging, in early pitches or presentations. for a finalized presentation to introduce.

This has a very positive effect on customers and partners and gives the impression that a market-ready product is only a stone's throw away. away. Furthermore, it also makes it easier for non-specialist and thus the provision of helpful feedback, when something tangible is available. In system development for customers running prototypes have the same effect.

Quality management and agility

The fact that comparatively little value is still placed on agility in larger, stable projects today is due to the complexity of the products and the need for intensive Quality management to do.

In order to guarantee the quality of huge software structures in the long term structures in the long term, traditional process-oriented approaches to quality management. But this is no longer the only option.

Tools and procedures that allow an agile form of QM, especially in the context of large agile form of QM, especially in the context of large projects, are popular not least for software intended for a broad user base. The project management software from Jira, for example, aims to the strengths of agile development teams for quality teams for quality management, regardless of project size.

In particular the ability to dynamically prioritize individual key points instead of a predefined, process-oriented approach, allows software development to react quickly and agilely to precisely exactly those problems that are relevant for an undisturbed project relevant for an undisturbed project - this means that a new version is version that has solved exactly the essential problems.

Author: Marvin Schubert

Marvin Schubert is a self-taught artist. Due to a variety of personal projects, he was able to get a place in various tech start-ups during the early 2010s. various tech start-ups during the early 2010s. Through working on economic projects, he became aware of the differences between individual and project-based development.

Cover: joyfotoliakid / stock.adobe.com
Picture 1: sakaidasan / stock.adobe.com
Picture 2: Trueffelpix / stock.adobe.com