How to approach writing requirements

My name is Konstantin.
Most of my professional life I was in charge of making new apps happen related to web development:
– Make a new website
– Make a new app
– Make a new feature for an app
– Make something that will solve the problem of a client.
In the beginning, my inner developer wanted to jump straight to creating a new piece of software and ask questions later.

Over time I’ve learned that there are requirements for a piece of software and it is a good idea to collect them first and write the app according to those requirements.

At some point, I’ve figured out that collected requirements often don’t reflect the real needs of users, even if you ask them directly.

Continue reading “How to approach writing requirements”