When you've got 10 spots, some stuff on a topic like this will get left out.

Let's just say I could do a second article just like this, with no overlap...
That said... if requirements change so much that you're "back to square one", there isn't much you can do about it. Either the initial requirement discovery was badly botched, or the business needs have changed so much that the original requirements are irrelevant. That's when "requirements management" can become code for "finishing a project that will be useless when it is finished, regardless of how well it was executed"...

J.Ja