Use story seminars to refine understanding and clearly define what the development team will develop. Workshop is a product-oriented dialogue, with many pictures and data to support and help the team to make decisions and confirm, that is, some acceptance criteria.

Before the workshop begins, let the team members know what story you want to tell in the workshop, post it on the wall or tell everyone, and let the team members choose whether to join.

The workshop should be small enough to be effective, preferably 3 to 5 people.

Get the right people involved (3-5 people).

In order to make the dialogue effective, we need to invite the following people to join us:

Other people and other roles may also be important, but please remember that in order to make the conversation effective, it is best not to exceed the "size of the table conversation".

You will find that a person may wear two hats. For example, a person is both a business analyst and a tester. However, if you don't fully consider the problem in the seminar, please try to find some team members who may see the missing problem.

Dig deeper and consider alternatives.

Use the dialogue to explore the following questions:

When discussing expensive or complex solutions, come back to discuss the problem we are really solving and see what other options are available.

Reach a * * * understanding of development decisions.

After enough dialogue to build knowledge, further answer the following questions:

Dialogues and documents.

Use whiteboard or flip chart to draw pictures, write cases and consider alternatives.

Don't let your decisions evaporate, write them down on a whiteboard or flip chart that everyone can see, and take photos for archiving.

Speak with cases.

Whenever possible, use concrete examples to illustrate what the user is doing, how the data is entered, what the user will see next, or any examples that can fully support the story.

Break down and lose weight.

When discussing the details and thinking about the development time, you will find that the current story is often bigger than the story you want to invest in development. We need the whole team to work together to break down the big story, or "simplify" our story by deleting unnecessary things.

When the following situations occur, the effect of the story workshop will become less good.