I could not agree more. You usually see the requirements of of a project only grow and it is often difficult to exclude things. However by excluding you can keep the scope clear if avoid confusion with the user. This starts with defining a clear goal for the product and indeed also the goals which are not to be met! This also gives you the opportunity to define new products which meet the excluded goals.
In the time the engine of a power tool was the most expensive part you had one machine which could do drilling, sanding, saw, … They have all disappeared because it is not user friendly (just wallet friendly) I think this has to be the same for SW but you often see it differently.
I could not agree more as the Germans say:
In der Beschränkung zeigt sich erst der Meister.
Or if you can limit your self to the minimal you mostly have a better product.
I could not agree more. You usually see the requirements of of a project only grow and it is often difficult to exclude things. However by excluding you can keep the scope clear if avoid confusion with the user. This starts with defining a clear goal for the product and indeed also the goals which are not to be met! This also gives you the opportunity to define new products which meet the excluded goals.
In the time the engine of a power tool was the most expensive part you had one machine which could do drilling, sanding, saw, … They have all disappeared because it is not user friendly (just wallet friendly) I think this has to be the same for SW but you often see it differently.
I could not agree more as the Germans say:
In der Beschränkung zeigt sich erst der Meister.
Or if you can limit your self to the minimal you mostly have a better product.