There have been many articles written about requirements development from many perspectives.  I happen to believe this is one of the hardest tasks of any project, and one of the key contributors to scope creep.  As the initial scope statement is defined, everyone believes they understand it.  But the devil is always in the details.  As detailed requirements are elaborated from the scope definition, the misunderstandings emerge and the estimates in time and resources get blown.  Now as project manager you are faced with the all too familiar triple constraint dance of getting permission to add more resources, or time, or reducing some of the requirements. › Continue reading…