User Stories and Agile Methods provides a comprehensive and detailed description of user stories from the aspects of user role modeling, story collection, story writing, prioritization, story estimation, story sprint execution, story monitoring, and story acceptance. Through a complete example, readers have a deeper understanding of the writing, estimation, release, and acceptance testing of user stories.
Identify user roles through brainstorming, and then integrate and refine user roles to achieve user role modeling. With the completion of user persona modeling, the product roadmap has gradually become clear. The product roadmap shows the focus of the product, the development direction of the product, and the market positioning.
User interviews, surveys, observations, and story writing workshops are the most useful ways to create stories. With the development of the Internet, stories can also be collected by means of big data public opinion analysis, user experience, and industry product analysis.
User stories are both a method of managing requirements and a technical practice. User stories have the advantages of being easy to communicate, easy to understand, suitable for planning, iterative development, and support for adaptability; however, writing an excellent (INVEST) user story is not an easy task. For large and complex requirements, it needs to be segmented from different dimensions. How to find a suitable segmentation point varies depending on experience and understanding of the project. User stories must not only reflect user value, but also be appropriate and implementable. From this aspect, writing good user stories requires constant practice to improve the ability to write good stories.
If a good user story is written based on different user roles, and the project implements the Scrum process, is the organization an agile organization?
If a team uses Scrum to develop software, team members must be proficient in software development technical practices. But this doesn't mean hard-to-understand skills, but some basic skills that make or break Scrum , such as: test-driven development, refactoring, minimalist design, continuous integration, collective code ownership, coding standards, metaphors, and more.
Without emphasis on unit testing, the development team will quickly slow down and face increasing risks as technical debt accumulates. In fact, unit testing is not only a verification behavior but also a design behavior. Writing unit tests will allow us to observe and think from the caller, especially considering the test first, so that the program can be designed to be easy to call and testable. , and strive to reduce the coupling in the software, it can also make the coders produce pre-tests when coding, and reduce the defects of the program to a minimum; unit tests also have regression. Likewise, without automated integration testing, each iteration would require re-regression testing of previously developed features. If the team chooses not to run all the manual tests in each iteration, it will cause defects to pass forward and build up the technical debt of the system.
User stories start with user personas, and whether they can walk on the "high road" of agile depends on whether the team implements agile technical practices.