How to hire a CMO
Dec 11, 2023 5:19:44 GMT
Post by account_disabled on Dec 11, 2023 5:19:44 GMT
Based on a conversation with a Customer, formulates answers to questions that allow to create User Story and enters them into the Product Backlog. However, User Stories reflect not C Level Executive List only customer needs. user stories User Story. Whose story is it? The Scrum Team creates a User Story to define the User’s needs, and that’s why it is put down in business language.
In other words, it indicates the benefits that its implementation will bring to the product user. However, in the Product Backlog, there can also be User Stories that describe the needs of the Development Team, for example improving the workflow between Developers, or describing the needs of the Product Owner, for example organizing the Product Backlog. In such cases, the User in the User Story is the Developer and the Product Owner. You can describe a User Story by answering the 3W questions: Who? Is doing What? Why? The User Story is then contained in a formula:
As a [user type], I want [to do what?] Because [why? why?]. Examples of User Stories about the functionality of an online store written in this form are illustrated in the table below: What are User Stories? - table This formula allows not only to formulate a User Story but also to relatively easily translate technical language into business and vice versa. As a result, both Developers and Stakeholders see clearly the Goal and stages of its progress. We will also cover creating good User Stories using the INVEST method in a separate article in the Scrum Guide series. How to use User Stories? Creating a schematic User Story is just the beginning. They are signals and starting points for discussions on problems and their solutions. Discussing User Stories takes place during Sprint Planning to sort out which technical issues the Development team will add to the Sprint Backlog.