Statistics: (513 Views) (0 Comments) Posted by: Adrian Marchis on Friday, January 18, 2008 Categories: Requirements Analysis (BABOK KA), SDLC, Process, and Methodologies, Agile Methods

The main benefit of today’s Agile development methodologies such as Scrum or XP is the promise of delivering more in a shorter period of time and the value derived from having the flexibility to adjust your course mid-way through a development effort. But does this type of approach allow for requirements management? Is RM necessary given the shorter development windows – sprints, milestones, stories, whatever you call them?

Well -- does the need to deliver what the requirement originally requested go away? Does the desire to control change to the requirement go away? Of course not, and neither does the need for requirements management under these newer methodologies. The nature of RM will change, certainly, but the fundamental principles will not. 

Author: Doug Akers