I need some example about how to break down epics or features to sprintable stories. Lets say I have an application for small shop. In user's perspective, the application will be divided into modules :
1. Purchasing (the shop must get goods from supplier, mostly in large quantities)
2. POS (selling the goods to individual customer)
3. Financial --> divided to two categories --> Expenses (paying the suppliers) and Revenues (receive payments from individual shop customers)
This is a web based application (run from a browser). As of now, this is the requirement for the initial release. For now, the user of this application are EDP employees of the shops (not public facing....yet, so no shopping cart yet).
Users are also required to log in before having access to the system.
Can anybody show me what the product backlog will look like? and how it will be broken down to sprint backlog? I'm still having trouble breaking down items.
Is this a team dev effort, or are you on your own? I ask because if you're on your own you can simplify things greatly by working what is called "personal kanban", which is to make a list of things you need to do and then do them one by one.
There are entire books devoted to the topic of user stories and agile estimation and planning. I suggest you look up Mike Cohn's books and articles on these subjects. There will be plenty examples of user stories and how to break down requirements into small manageable chunks to put in your product backlog and sprint backlog.