{"id":103123,"date":"2019-02-01T02:14:00","date_gmt":"2019-01-31T18:14:00","guid":{"rendered":"http:\/\/itteacheritfreelance.hk\/test\/wordpress\/?guid=0058e7a7acccad2aaacfc253de34361e"},"modified":"2019-02-01T02:14:00","modified_gmt":"2019-01-31T18:14:00","slug":"how-to-write-agile-user-stories-7-guidelines-4","status":"publish","type":"post","link":"https:\/\/itteacheritfreelance.hk\/test\/wordpress\/2019\/02\/01\/how-to-write-agile-user-stories-7-guidelines-4\/","title":{"rendered":"How to write agile user stories: 7 guidelines"},"content":{"rendered":"

Fundamentally, agile user stories are short, simple tools to document a single action or intention desired by the targeted user to achieve a goal. The simplest user stories have a format, \u201cAs a user type or role<\/em>, I want to action or intent\u00a0<\/em>so that reason or benefit<\/em>\u201d that answers at least three simple questions on who, what, and why the story is in the backlog queue.<\/p>\n

As teams mature and organizations use agile across multiple teams and initiatives, agile user stories often take on a lot more definition and structure to ensure there is a shared understanding of the intent and underlying requirements.<\/p>\n