Some examples of "sprint 1" stories for an e-commerce site:
As a new customer I want the ability to sign-up for an account so that I can purchase
As a potential customer I want to browse a catalogue of products
Some examples for an HR application:
As an HR user I want the ability to login
As an HR user I want to retrieve an employee's details by ...
Don't get hung up on writing the perfect user story. Instead, if this is a new product that you are building from scratch, focus instead on:
defining a big picture of what the product should do;
split that vision into pieces, actions, and actors (you can use a technique called User Story Mapping for that, and create epics and user stories);
place these ...
One user story will not give you a releasable product
that represents some value to an end user
This clause is added to get over the mindset of previous Waterfall practices. Doing analysis alone or doing design alone is not a valid user story. The story must result in some shippable code, which is what represents value to the user.
can be delivered during ...
Apart from ashes999 great answer there is one more notable mention of how to introduce Agile into non-IT organization or team. I really like the part about not going with all the buzzwords and working mainly through Agile values perspective.
There is a 5 step method according to this post: https://teamhood.com/agile/agile-for-non-it/
Educate people about ...