Although user stories were first utilized in software development to ensure the stakeholder or customer would get what they want, it is possible to use them on just about any Agile project.
Because the Agile Methodology uses iterations and sprints, user stories can aid project managers in deciphering quickly what “users" or stakeholders expect from the varying elements of a project.
User stories are brief and short, usually compiled on 3 x 5 inch cards; they are not meant to be lengthy or include long dialog. As Kelly Waters of Agile Software Development Made Easy states of user stories, they “should focus on the who, what, and why of a feature, not how." The “how" is up to the project manager and assigned teams.
Say your client is a marketing firm. They might write a user story that says:
As a marketing firm, we want to be able to search for product use by demographic to analyze markets.
The who is the “marketing firm"; the what is the “ability to search for product use by demographic"; and the why is so they can “analyze markets."
Based on your client’s user stories, you need to come up with the how. Of course the how represents your Agile project strategy to meet your client’s expectations.