Photo by FORTYTWO on Unsplash

3 reasons why requirements engineering is so essential

Emir Selimovic
2 min readNov 25, 2022


Maybe you’ve been in such a situation once. Great idea, everything seems super clear, you start working, and suddenly, after you put in weeks of work, you are miles away from the product you wanted to develop.

Requirements engineering before starting the development is key.

I’ll tell you 3 reasons why:

1- you have a clear vision of what problem your product should solve. By asking the right questions, you can define a very clear strategy.

2- you don’t over-engineer your MVP. This is such an important point. An MVP can be defined very well in a requirements engineering workshop.

3- you don’t lose time and money. By knowing where you want to go and what your MVP and further iterations should look like, you can prioritize resources clearly and focus on the essential things first.

Take your moment before getting going. Think about all the requirements, and pick the most important ones. Turn them into a great MVP, and validate your idea. Collect feedback, and iterate.

This will save you tons of time. And money.

I am writing articles about starting profitable and scalable businesses, bootstrapping, building high-performing SaaS products with smart business models, and leadership. Follow me for more or have a look at my LinkedIn and Twitter accounts or visit my website.



Emir Selimovic

CEO of Dotbite. Writing about scalable business models, SaaS products and leadership in bootstrapped companies.