This is why grownup software companies have milestones like “requirements freeze” and “feature freeze”, and strong project management leadership who enforce these things. Adding or changing requirements mid-project (or mid-sprint, if that’s how you roll) is very often harmful to a software program’s success.