Ok, time for something light. This is funny stuff. Forget the phases or iterations – THIS is how the development lifecycle really plays out… Right?
Breaking out of analysis paralysis doesn’t require you to lower your standards, or to aim lower than you would otherwise. It just requires some prioritization. What you have to do is identify those things you have to get right from the get-go, those items that do need analysis, and what can be fixed later.
You’ve poured your heart and soul into drafting the perfect requirements specification. You’ve checked, doubled checked, and triple checked every syllable of the document for clarity, spelling, testability. You have full traceability to every business requirement. You’ve been extra, extra careful not to tread in the domain of design. Your spec is rock solid.
So, why, after 5 review sessions with project stakeholders and document consumers, are you still making edits?