As a [ person ]Unfortunately, I don't believe that it creates the accountability that it attempts to show. For example, a story card could be:
I would like to [ action ]
so that [ reason for action ]
As a script authorThe above story card would be a valid story card; however, it doesn't tell me who introduced this story card. What if the card was introduced by a stakeholder who will actually never play the role of script author. Perhaps it was created in anticipation of an auditing requirement that has yet to be defined. In the end, the functionality may end up YAGNI.
I'd like to see a diff of current scripts against previous scripts
so that I can verify alterations
Ownership can be very important when stakeholders need to collaborate on determining scope. Therefore, I prefer explicitly naming the owner of the card.
Jay would like to see a diff of current scripts against previous scripts so that he can verify alterations.Using this format also ensures that only customers are creating requirements.
For more information on Story Cards check out the c2 wiki.