The story-telling process is usually conducted in the form of a demand seminar to ensure that all the people involved are present. Since it's a conference, we have to make sure the conference is efficient, so here's a 8-point guideline for Samsung's efficient meeting:
(1) Every meeting must have a theme;
(2) There must be an agenda for any subject;
(3) There shall be resolutions on the agenda;
(4) Any resolution, there will be tracking;
(5) Any trace shall have the result;
(6) The result shall be responsible;
(7) All responsibility shall be reward and punishment;
(8) All rewards and punishments must be transparent.
We need at least the following arrangements for demand-based seminars
- Meeting Subject: XXX Product Requirement Seminar, the purpose is to discuss XXX product XXX content within 4 hours
- Conference Agenda:
- Organizer: Product Manager xxx or project manager xxx
- Participants: Business parties or end users, product/project managers, Team Technicians (architecture, development, testing, etc.)
- Discussion content (List of stories sorted by priority)
- Conference Division:
- Moderator: Rotate the organization by Product manager and project manager
- Requirement Recorder: By a person in the technical team, responsible for the discussion process of user stories and the resulting function points in detail records, form a document or input system.
- Issue Recorder: By a person in the technical team, responsible for the discussion process will not be able to confirm the field to record, form a document or input management system.
- Conference Deliverables:
- documentation or management system records generated for each user story on the agenda
- List of issues recorded during the discussion or management system records
- Next steps for the user story document, such as: Developing a development plan, budgeting, etc.
- The problem is tracked in such a way that the status of the problem list is maintained by WHO, and each issue is resolved by who is responsible for the follow-up, each issue is expected to be resolved.
The process of requirement discussion is to discuss the story and analyze the story according to the above 3 steps, we can follow the following process
- Pre-Seminar Preparation
- It is possible to brainstorm a brainstorming session before conducting a formal demand discussion, inviting users and technology to participate in the process, in which you are free to discuss. The aim is to give you an idea of the general situation of the product.
- Seminar Process
- First, the moderator (Product Manager po/project manager scrummaster) lists the list of stories to be discussed by the team, which is not discussed in detail and is designed to let you know the content and goals of the meeting and to make it easier to control progress.
- According to the list of story priority, starting from the 1th story to comb the story line, decomposition function points, and by the person responsible for recording
- Repeat the process until all the stories in the list are discussed
- Precautions
- Be sure to follow the story list one by one, each discussion will be refined to the function point and complete the record, and then into the next story discussion; do not first discuss all the story lines, and decomposition function points together. The purpose of this is to allow the team to focus and avoid distractions caused by multiple threads.
- When discussing each story, do not discuss content that is not relevant to the current thread, especially if the technical team is prone to spread from one function point to the other, as this is the product perspective of the technical team, and this diffusion reduces efficiency. The moderator should stop when he sees this, telling the team that other functional points can be left to discuss in other stories, as long as the part of the product we are sure to cover in the following story.
- You can take a short break after completing the discussion of each story, ensuring that each participating member is focused and avoids the form of a group discussion during the discussion. It is recommended that the discussion of each story stand before the whiteboard.
- The host can be rotated by PO and scrummaster according to the story, the main responsibility of the host is to ensure the smooth process, the concentration of team effort.
- Pending confirmation
- It is recommended to open up an area on the whiteboard to record the problems that the team in the discussion can not identify on the spot, and to avoid having to dwell on these issues for too long and affect the efficiency of the meeting.
How to organize requirements seminars
