meetings_how_to
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| meetings_how_to [2020-06-01 15:10] – tkerby | meetings_how_to [2020-06-01 20:15] – [Actual content follows] Simon | ||
|---|---|---|---|
| Line 24: | Line 24: | ||
| * Meetings should have a purpose. | * Meetings should have a purpose. | ||
| * Send out an agenda ahead of time, so that the purpose of the meeting is clear to all attendees and they can come prepared if necessary. Ideally this should include a quick background paragraph/ | * Send out an agenda ahead of time, so that the purpose of the meeting is clear to all attendees and they can come prepared if necessary. Ideally this should include a quick background paragraph/ | ||
| - | * After the meeting has finished, create | + | * Create |
| * Discuss this action list at the start of the next meeting if there is one. | * Discuss this action list at the start of the next meeting if there is one. | ||
| * Agree on a time limit in advance (eg an hour max) and try and stick to it: Better to have two shorter meetings with fresh people than one enormous mega-meeting that burns everyone out. | * Agree on a time limit in advance (eg an hour max) and try and stick to it: Better to have two shorter meetings with fresh people than one enormous mega-meeting that burns everyone out. | ||
| Line 44: | Line 44: | ||
| * Use techniques such as shadowing, brainstoming | * Use techniques such as shadowing, brainstoming | ||
| * Prioritise solving problems that are urgent, pervasive and valuable | * Prioritise solving problems that are urgent, pervasive and valuable | ||
| + | * Write don and communicate the problems - e.g. user stories, use cases, personas, problem statements | ||
| === Think Requirements === | === Think Requirements === | ||
meetings_how_to.txt · Last modified: 2020-08-10 09:26 by river