In Scrum or other Agile processes - how do you handle requirements versions

Question

In Scrum and / or other Agile methods, how do you deal with requirements versions easily? I assume that there are many organizations that are Agile, but it is also necessary to track changes in requirements for regulatory purposes, etc.

You may have a requirement in version 1 that changes significantly in version 8. How do you track this change between releases?

Answer 1

The simple answer is: we don’t do this, because tracking changes usually doesn’t make much sense or it brings any benefits.

, - (, , "" - , ?), , , , , . , - . (, Scrum) , ( ), .

BTW - "" , ( ). , , , . , , ( ), . (, ..) , Scrum , , / .

Answer 2

... , , , , ( ) .

, , "agile" "scrum", .

Answer 3

, /, , .

Assembla . wiki, , ( ) .

, , .

, , , / , . , (, , ), , , ​​ .

Answer 4

( , ?). , ?

, . . -backlog .

. , , .

, Paddyslacker Wiki. . , .

Answer 5

SCRUM, . , , , SCRUM, SCRUM . - , backlog ( ), / / , ., " ".

( , , , - AUP Crystal Clear)

Answer 6

You did not indicate which platform you are running on, but if you are using TFS; it keeps track of all the changes in the lag elements, when they were changed and by whom.