Project Management (11)-Agile development Gathering stories

How do you collect stories? This article tells you how to work with users, how to communicate with them to discover stories

The following four are some of the most effective ways to collect a story

First, user interviews

1, is the default method for many team users to obtain user stories, the key point of successful interview is to access the right respondents

2, don't just ask "what do you Need", most users are not very good at understanding, more difficult to express their real needs

3, it is best to start from the background irrelevant questions, so you can get more diverse answers from the customer

For example: "What are you willing to abandon in order for our products to run in the browser?" "

The user may have a lot of answers, no matter the kind of answer, it will make a lot of sense to us.

Second, the questionnaire survey

1. Surveys are an effective way to help collect information about existing stories. If you have a large user base, then the questionnaire is a good way to prioritize your stories. Questionnaires are useful when you need to get specific answers about a large number of users

2, the questionnaire is not suitable as a method to capture new stories, static questionnaires are not easy to follow the question

Third, observe

1, observe the actual use of the software situation, generally only in the case of internal projects to observe the user's use, most of the business process is to guess the needs of users.

2. Observation allows you to quickly and directly get feedback from users, so that the release of software earlier and more frequently

Four, the Story preparation workshop

1, developers, users, product customers and other people who write stories that help to participate in the memories. Participants write user stories as much as possible during the workshop

2, the right to hold the company's writing workshop can be very quick to get a lot of stories.

Story Writing Summary:

1, once the demand is captured, do not change

2, technical agile process support needs to emerge later, still need to look forward to its release and begin to write the story of Fleece discovery

3. We can return the user story through user interviews, observation users, questionnaires and workshops to prepare stories

Developer Responsibilities

1, responsible for understanding and use a variety of techniques to capture user stories

2, responsible for knowing how to use the development and background-independent questions

Customer Responsibilities

1, responsible for understanding and use a variety of techniques to capture the story

2, responsible for writing more user stories as early as possible

3, as the main representative of software users, responsible for and developers to communicate more

4. Responsible for arranging and organizing one or more story-writing workshops

5, responsible for the capture of user stories in the process of considering all user roles

Project Management (11)-Agile development Gathering stories