User stories are written from the user's point of view to describe the purpose or value the user wants to achieve and the desired user behavior. A story has the following format: "As a , I want so that ."
The purpose of a user story is not just to write down the requirements in this format but to use this description as the starting point for the Product Owner and the team to have a clarifying dialogue. Looking back at the stories in the future, the members can recall the discussions, like seeing a trip photo together.
Titansoft teams compile product to-do items through user stories. Paper cards with the items are posted in the team's workspace and constantly updated to visualize the information for members to browse and collaborate. Titansoft is value-oriented and takes a purpose-first approach to user story cards. The cards are written in this format: "To as a , I want ."
In a Sprint planning meeting, members will discuss the acceptance criteria of user stories and agree on the expected output. The team will also estimate the work scale in accordance with the acceptance criteria. The estimation results help the team determine how many user stories could be completed in a Sprint and provide a reference for the Product Owner to prioritize the items.