A common software development mistake: Going too wide or too narrow
A common software development mistake: Going too wide or too narrow.
Too wide = “Let’s partially implement lots of features.”
Too narrow = “Let’s focus on one feature until it’s absolutely perfect.”
Projects can fail at either extreme.
The solution? Balance.
👇
Too wide: "We have 5 devs. We need to build 25 features. If each dev builds 1 feature a day, we'll be done in a week! We'll clean up later. 😬
Too narrow: "This feature is important, so it must be perfect. Let's focus on only this until it's flawless."😬
The solution? Balance.
So how do we find a balance?
Define "done".
A good definition of done balances these two extremes. It should set a sufficient quality bar before moving on. But it should also avoid over-engineering features.