Development Management checklists (11)-agile development-collect stories

Note: The Development Management Checklists-series of articles are transplanted from my iteye blog. The Development Management checklists column will be updated directly in the future.

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

 

The following four are the most effective methods to collect stories:

 

I. user interviews

1. It is the default method for many team users to obtain user stories. The key to successful interviews is to access the correct respondents.

2. Don't just ask "What Do You Need". Most users are not very good at understanding, making it hard to express their real needs.

3. It is best to ask questions that are irrelevant to the background so that you can get more diverse answers from the customer.

For example, "what are you willing to discard to make our products run in a browser? "

Users may have many kinds of answers. No matter which answers, they will have a great significance for us.

Ii. Questionnaire Survey

1. Questionnaire survey is an effective way to collect information about existing stories. If you have a large user group, it is a good way to prioritize stories on mobile phones during the questionnaire. The questionnaire is very useful when you need to obtain specific answers from a large number of users.

2. Questionnaires are not suitable for capturing new stories. Static questionnaires are not easy to follow based on subsequent questions.

3. Observation

1. Observe the actual use of software. Generally, only internal projects have the opportunity to observe the user's usage. Most commercial programs speculate on the user's needs.

2. Observation allows you to quickly obtain feedback from users and release software earlier and more frequently.

4. Story Writing Workshop

1. Memories of the participation of developers, users, product customers, and others who write stories. During the workshop, participants try to write user stories as much as possible

2. If you organize a company to write workshops correctly, you can quickly get a large number of stories.

 

Summary:

1. Once a requirement is captured, do not change

2. The technical agile process supports the emergence of demand in the later stage. We still need to look forward to its release and begin to write the story of the velvet discovery.

3. We can return user stories through user interviews, user observation, questionnaire surveys, and stories compiling workshops.

Responsibilities of developers

1. Understanding and using multiple techniques to capture user stories

2. Responsible for asking questions about how to use the development style and irrelevant background

Customer Responsibilities

1. Understanding and using multiple techniques to capture stories

2. Write more user stories as soon as possible

3. As the main representative of software users, responsible for communicating with developers

4. arranges and organizes one or more story writing workshops.

5. All user roles are considered during the capture of user stories.

<Development Management checklists> by dylove98 @ Development Management checklists