Although various companies and their agile teams might use their own “agile” format of story writing, a very popular and common way of agile story card writing is to follow three lines that mentions who is the user, what the user wants to do and what is the business value of doing that action or achieving that goal.
This is in sharp contrast to most of the waterfall model requirements writing where most of the time the requirements are written with System of Application in view rather the users in the view. It’s not uncommon to see those waterfall model requirements to be documented as “System shall…”.
One of the reasons behind the success of the agile model of programming is the care for the user role and the business value more than the waterfall one (despite the pros and cons of each type).
The diagram above shows a typical format of a agile story card.