we (at PayPal) are starting a project (fairly important) and we are
in the initial stages (concept) to do initial planning.
More and more I learn on User Stories, I feel more comfortable to
use this model for each Sprint. they are not as structured as Use
Cases, hence conversation could be started ASAP with the team.
my problem is once we use the user stories, and develop, (and unlike
Use Cases which would exist post go live, and hence pass the
audit/SOX requirements), how does one document user stories (not
just in cards) and still follow the compliance regulations?
We are thinking of the following approach:
1. the product team member would use User Stories to start the
conversation in the beginning of a Sprint, dev and QA to go through
the process using this user story
2. Once we move to the next Sprint, the product team member to
document the user story (from the previous sprint) in a standard
document (to satisfy SOX/audit compliance).
I see some down side, that in step 2 above, the product manager
would not involve the team to document (hence some changes could
happen) - which is done post-facto.
Any recommendations? I am reading "User Stories" by Mike Cohn,
meanwhile looking at best practice methods.