One thing that I think we, as business analysts, occasionally forget is that the downstream delivery teams are our customers, too - and in a very real way. We need to make sure that they have an opportunity to develop a true sense of ownership for the project early on and that they understand what the requirements are all about.

Reuse, software methodology, use case driven development, methodology.org and more.

Ok, time for something light. This is funny stuff. Forget the phases or iterations - THIS is how the development lifecycle really plays out… Right?

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?