IAF Methods

Quality Assurance Storyboard

by for . Last edit was almost 2 years ago
any 1 - 25

A 'Storyboard'  is used as a tool during a project, meeting or discussion in order to capture  comments, achievements, problems etc.

0
1
Share
Embed
Use
Edit
View
Delete
DRAFT Pending Declined
Submit for approval
Decline
Approve

Additional info

Goal

The intent of this tool is to create a visual piece of work that combines all the important information of a meeting, a project, or a discussion.

Attachments

You will be able to upload attachments once after you create the method.

Materials

  • a big board or large flipchart on the wall for the story board

Instructions

Before

Setting: Needed is a a big board (2m x 1.5m) on which the group or the facilitator can write on.

Number of participants: 1-25, The group can be of any size, but should not be too big, so as the facilitator can still follow what has been said by each individual.

Types of participants: Any types of participants can be involved in this process.

Time needed: The process needs as much time as the normal group process as it is only an addition.

Ideal conditions: The room should have a wall big enough to place the storyboard upon, and it would be helpful, if it was accessible and can be seen by anyone at all times.

Pre-Work Required: The facilitator needs to prepare the storyboard (see Procedures).

Type of Facilitator-Client Relationship: A special Facilitator-Client Relationship is not neccessary.

Facilitator personality fit: The facilitator does not need any particular characteristics.

During

1. The facilitator places a poster board of at least 1.5m high and 2m length on the wall, which will be the Storyboard.

2. On this board, different areas have to be marked off and labeled, displaying the team's progress during each of the steps. Other areas that have to be defined are the problem statement, names of team members, work plan, activities undertaken during problem analysis, results, solution(s) selected, solution implemented, results and any other information that seems of relevance to the facilitator.

3. The facilitator should write down the initial problem statement and the names (or a picture) of the team members. The facilitator needs to assure that these facts stay up-to-date, in case the team members change, or the initial statement is refined.

4. A copy of the team's work plan and schedule needs to be posted, and again might need changes during the problem-solving process.

5. As work progresses, the facilitator displays the progression in analyzing the problem. Provided that any analytical tools were used (flow-charts, cause-and-effect diagrams), these should be added to the storyboard. Anything that could be of relevance for the solving of the initiated problem can be added to the storyboard. Furthermore the findings of the problem analysis and the proposed and for implementation selected solutions then need to be posted on the board. Again, any other facts and aspects of importance (selection criteria or method) can be displayed as well. Throughout the whole process the facilitator has to maintain the display of the progress. Depending on what is considered helpful, show as much (or as little) detail as needed, depending whether the group wants to focus on their own work, or on communicating this work to others.

6. The last step is to post the results, being a solution that has been implemented and evaluated, for everyone to see.

After

Follow-Up Required: There is no follow-up requiered, a reflection is of course possible, and the results should be posted somewhere where everyone who needs/wants to see them can do so.

Usual or Expected Outcomes: The outcome should be a storyboard that documents the various steps and the focus of the group, with problems, successes and anything else that is of relevance.

Potential pitfalls: If the facilitator fails to keep the structure on the storyboard, or too much information is placed upon it, the danger of "chaos" occurs.

How success is evaluated: The process is successful, when the facilitator managed to post all important information on the storyboard.

Background

Comments (2) ( 1.0  avg / 1 ratings)

Please Log in or Register for FREE SessionLab account to be able to comment or rate.
  • I changed the header to call the storyboard a tool that can be used in various processes for projects and meetings, workshops.

    Delete
    about 2 years ago
  • Just a paper copy of electronic kanban board

    Delete
    almost 2 years ago