“I write down exactly what I need. That’s the only way potential service providers can get a precise picture of my requirements and create reliable offers that I can then compare.”

Sounds plausible, right? It is, but unfortunately only for simple requirements.

Imagine that you want to build a garden shed. You know exactly how much space is available for it in your garden and what other requirements you have (material, color, sliding door). You look at suitable models online and finally order one. What are the chances that everything will go smoothly and that the garden shed will end…


Does budget estimation even go together with agile working?

Projects in agile environments accept that not all requirements are known at the time. Assumptions will change and new requirements will arise. Some requirements will become obsolete when we incorporate early user feedback.

Should we start our project without the slightest idea about how much it will cost and how long it will take? If we do this, then how can we make investment decisions like “Should I make or buy this software?” or “Will there be a return on investment?”? Might this be the reason why some large corporations still struggle to work “truly” agile?

There is no contradiction…


At Ambient Innovation we build most of the frontends as Single Page Javascript apps (SPA) using React, because we absolutely love the desktop-like user experience of this kind of website.

Photo by Caspar Camille Rubin on Unsplash

While this technology offers a great UI, it has major disadvantages compared to “classic” websites, where the whole website (or at least most of it, if Ajax is involved) is rendered by the server:

  • The first page load usually takes a lot longer for Single Page Javascript apps, since the Javascript assets have to be loaded first and only then the DOM is built and the website appears as it…


Photo by Jo Szczepanska on Unsplash

“User Stories” are a very popular format to describe requirements. While it is not the only available format and by far not the only way to work, this format has many advantages, which make it so popular. Let us dive directly into it. The template for a User Story is this:

As a <role or persona>, I want <some goal> so that <some reason>.

For example: “As the call center agent of a ticketing service, I want to be able to quickly find information about the calling user so that I can correctly say his/her name and talk about his/her…


The role of the Product Owner in an agile team is a tough one — possibly the toughest one. You will have to evaluate many feature requests, prioritize between great ideas and urgently required features. Most likely you will have stakeholders who ask you when their feature request will eventually be developed, or why their idea was deprioritized in favor of another feature or not even selected for implementation at all.

These discussions can be exhausting and frustrating, especially if the stakeholders take your decisions personally or are your superiors. …


This article discusses four ways of handling different environments (like an API endpoint for dev, stage and prod) in React apps using Docker (Bonus: and Kubernetes).

Photo by Artem Sapegin on Unsplash

I am a passionate react developer and devops-enthusiast. Many of the teams in our company use React in combination with Docker and Docker Compose for local development and Kubernetes for deploying the application.

In most of the projects we have several environments (production, staging and local development) and in some projects even one per feature or branch. …

Felix Schul

React, DevOps, and Agile enthusiast, working at https://ambient-innovation.com

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store