Software Standards
Avoid scope creep: What is Scope Creep? How Do You Prevent Scope Creep?
Don't solve problems that don't exist: Imaginary Problems Are the Root of Bad Software
MVP's should only include minimal features
Focusing on the complex, seldom used parts of an app means that the simple parts (that are used all the time) often suck
Focus first on high-impact, low-hanging fruit
Don't spend lots of time future-proofing: Stop future proofing software
Future proofing is often spending time to build support for something that may never happen
"Preparing for the future doesn’t involve tacking on complexity, but rather removing as much of it as possible. The simpler your codebase is, the easier it is to adjust to fulfill a different purpose. If you’ve designed something to work perfectly, you’ve made some sacrifices along the way. Those sacrifices are usually around flexibility."
"The challenges that may pop up next year, will have next year’s technology to solve them."
Focus first on meeting your goals. Cut features as needed to meet your goals. It is better to deliver on-time with fewer features, than it is to deliver late with many features.