Those are the three most valuable artifacts of a project. Requirements should drive most (if not all) activities in a project. A project should be architectural centric and requirements driven... We have all heard these cliches before but how exactly does one manage requirements in an iterative process? How do we make sure that all team members are rowing the same way?
Supporting Iterative Development Through Requirements Management gives a good insight on how effective requirements management can be accomplished in an iterative process - in this case using the Rational unified Process (RUP). Even if you are using another iterative process (like SCRUM or XP) the article should give some good ideas.
If you are not using an iterative process then forget about the article and read "Why should I be using an iterative process" instead.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment