Author name: Jens Paggel

API are not for software alone. They work for everything. They are a concept to be discovered.

Architecture documentation. That is what we do, when we are done. Well, that is possible. Just like in classical civil engineering, the architects rule. If you like it or not. In iterative software or system development, things are slightly different, but only slightly different.

Oh no, we cannot do that! Why? You can always challenge paradigms. Let us challenge configuration management.

Some illustrations that assessment models for processes shall not be mistaken as the process itself. The assessment model tells what should be achieved on the way in terms of documentation, tests, test coverage, process descriptions, maybe more. How you do that is described in the process.

The useless discussion Agile or not. Is Taylorism bad? Shall we do everything in agile now? How do I know what to do? Answers to all these questions.

Resource planning for the next 12 months? You must be kidding…

Agile scaling is more business than agile itself. The question is: What is it and why should I want it?

Curiosity killed the cat and complexity kills speed. Simple solutions can be simple, rugged, of high quality, and fast. On top of things, they can even be re-used and adapted or modified.

Design Thinking is really a great way to look at products and services. It focuses creative energy, sometimes even creates it, but: it does not always do magic. Here some — to me — interesting example that I would like to pull to your attention.

Many people are trained in getting started with a plan. Can be one. More successful is sometimes (most of the times actually) to get started with objectives and understanding the environment you are acting in. To change paradigms requires a leap of faith. A short introduction. 😉