Hello Everyone,
I’m writing user stories for an analysis tool that includes multiple pre-populated fields as we as fields with calculated values. Instead of describing requirements for each data field in the user story itseld (data source, default value, user edited/not user edited, required/not required, calculated/not calculated, calculation formula, inputs and outputs for formula) I created a matrix with all the data fields and their requirements and would like to give references to this matrix from user stories. Is this a common practice to give references from user stories to different kinds of spreadsheets with detailed req-ts? If there are changes to user stories later on and consequently to field requirements what would be the best way to reflect these changes in the matrix so it’s clear where the change was and what the new and original requirement is. I would appreciate your feedback a lot!
Yes. I would categorize them though - example: Mandatory fields, Optional fields, etc.
I would keep this spreadsheet in a sharepoint with version. And user story would reflect the version on which it was built.
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: