Turning to this familiar question , I want to know how you can manage specifications in a Scrum process? I ran into this problem when assigning tasks to my team for sprinting. Needless to say, I'm new to Agile / Scrum.
We are currently using our own specification sheet to map StoryId to SpecId and vice versa. I get the cut-down that Scrum is more about project management [something done on time], and you need a separate process to manage specifications and requirements.
How do we manage specifications in the Scrum process?
The short answer is no.
, , - ? ?
. Scrum ( ) . (, ) , , , .
Agile- , , , .
, , . , , , .
BDD Cucumber. , , "//". , .
, ", , , ".
, . - , .
, . Scrum , , , , . - Scrum.
, , .
, - . ( ). , , .
, , , , , .
, , , ( BA, ) , . , . ( SharePoint), .
. , . - scrum, ( , ).
, , . , , , - [VersionOne] [1], [Rally] [2].
, .
SCRUM, . / . :).
Scrum dev . , :
agile , -, , , -. (, , .)
( , .)
, . , , . .
, , . , . , , scrum/agile / , .
, , - . , , . , 16 , , -. , " " ( " ", " " ..). doc " " , //, / , , , ( - ).