Portal:Social entrepreneurship/networking/Core Team Activities/Preparing for the Use Case Workshop 7 August 2008
Jump to navigation
Jump to search
Preparing for the Use Case Workshop 7 August 2008[edit | edit source]
PROPS[edit | edit source]
- Index Cards - +/- 200
- Felt tip pens (white board markers ok)
- Flipcharts x 2
- White board and markers
- Decent sized table we can cluster around with index cards spread across it
- Data projector (optional).
PRE-WORKSHOP ACTIVITIES[edit | edit source]
1. Prepare handouts (SNM)[edit | edit source]
Handout 1: Table of Use Cases[edit | edit source]
- use case number
- actor (student, educator, some other party or system)
- use case name
- use case description
- priority (blank - to be set by the educators and students)
- estimate (blank - to be set by developers)
- status (blank - to be set by the reviewers via demo)
This should be based on work already done.
The use cases may be derived from the Scope document.
Handout 2: Activity Diagrams for the system (SNM)[edit | edit source]
See example.
A clear and simple way to describe the system and activity flows from the user point of view.
Use this as a basis for the Conceptual Walk-through during the workshop (agenda below).
2. User Story cards[edit | edit source]
Write the id#, name and description of each use case on an index card. (SNM)
DRAFT AGENDA FOR 7 AUGUST[edit | edit source]
The following is the draft plan - a learning experience for us all.
We will play it by ear.
Time | Activity | Output |
---|---|---|
0830 | Arrival | ... |
0900 | Introductions and context (RH) - where we are | Participants updated. |
0915 | Today's Activities Overview (KT) | Roles explained: students, educators, reviewers, developers. |
0930 | Conceptual Walkthrough via use case list (SNM) | Common understanding - refer to handout |
1000 | Tea | ... |
1030 | WORKSHOP (KT) | Output |
1030 | Story cards will be spread on the table and clustered to match activity sets indicated in the walk-through. Educators and students to prioritise the cards (critical, important, nice to have) | Prioritised Clusters of cards. |
1130 | Developers estimate and comment on implementation feasibility. | Phased Implementation Plan for the straightforward use cases. |
1230 | Lunch | ... |
1330 | WORKSHOP | Output |
1330 | Plan how to handle the tricky use cases: discuss activities and whether to split/merge use cases, etc. | Set of tricky use cases still to be implemented. |
1430 | Brainstorm details for the tricky cases | Draft activity diagrams, more detailed use cases where needed, and possibly draft sequence diagrams from technical discussions. |
1530 | Tea | ... |
1545 | Wrapping up | Full set of use cases to be implemented for the pilot. |
1630 | Close |
background reading for developers[edit | edit source]
- Alistair Cockburn's web site - a wealth of really useful information on agile software development methodologies.
- Articles (general)
- For use cases specifically, see: