Preventing architectural decisions from slowing us down
Architecture decisions have a direct influence on product velocity and can noticeably accelerate development.
Product Velocity is a new approach that enables companies to learn faster, make decisions more quickly, and deliver results.
Agility Requirements Attack security Architecture Automotive Barcamp Digital transformation Eclipse GfSE Hardware Innovation Integration Communication Complexity Conferences Artificial intelligence MBSE Modeling Traceability Openness PLM Product development Processes Quality ReConf Interface Semiant Security Software SpaceX Standards SysML SysML v2 Systems thinking Systems Engineering TdSE Tim Weilkiens Traceability Transformation Trends UML Video Christmas Further training Tools

Architecture decisions have a direct influence on product velocity and can noticeably accelerate development.

Semantic versioning has made component-based software development possible. Perhaps in systems engineering too?

One area of application for AI in product development that is often overlooked at present is change management

Compliance, i.e. adherence to guidelines, is an important topic in systems engineering. This is usually required where systems can potentially cause major damage. Compliance has always been important and is well established in many industries, such as aerospace, rail and automotive. However, more and more systems that can cause damage are...

It is becoming increasingly difficult to deal with change as we are confronted with more and more change. We therefore need a new paradigm for dealing with change. I recently presented the idea of a toolbox for dealing with change. Of course, dealing with change is nothing new, and many organizations have established processes to...

Acceleration in product development is a real challenge for systems engineering. Traditionally, stability has been emphasized there, not agility. However, increasing complexity and tougher competition make it vital to be able to handle change well. This was recognized as early as 2001 when the agile manifesto for software development was drawn up, and...

A single source of truth would be nice, but it's often not realistic. This post explores alternatives for distributed work.

I'm particularly pleased about this week's post because it's about a new event that took place for the first time. Today Goran Madzar reports on the first Systems Engineering Camps in Erlangen. This is an event that will now take place every 2-3 months. The event and results are presented below - peppered with lots of flipchart pictures...

Two years ago, I wrote here that agile system development has been practised for almost 50 years. Nevertheless, many people still find it difficult to put it into practice. There are many reasons for this: For example, many of the relevant standards are not necessarily written in an agile-friendly way. Furthermore, dealing with changes is still a challenge; however, changes are...

What is the difference between efficiency and effectiveness? Someone who is efficient has a high degree of effectiveness, i.e. achieves a lot per unit of time. Someone who is effective comes closer to the result. But what does this have to do with systems engineering? Quite simply: the complexity of systems engineering means that you can quickly become efficient without being effective....
Unfortunately this website uses cookies! The website also works without cookies, but then you won't be able to watch videos or leave comments. You can decide for yourself what you allow. Data protection comes first - we promise!