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] – [Think Problems] tkerby | meetings_how_to [2020-06-01 15:11] – [Avoiding Bikeshedding] tkerby | ||
|---|---|---|---|
| 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 === | ||
| * Remember there are multiple stakeholders - anyone with an interest has a voice (e.g. suppliers, potential users, others with opportunity cost) | * Remember there are multiple stakeholders - anyone with an interest has a voice (e.g. suppliers, potential users, others with opportunity cost) | ||
| * Document the problems as requirements that can be validated against when considering solutions | * Document the problems as requirements that can be validated against when considering solutions | ||
| - | Consider implicit requirements that are not communicated – and check them with stakeholders (e.g. tea must be in a mug) | + | * Consider implicit requirements that are not communicated – and check them with stakeholders (e.g. tea must be in a mug) |
| * Remember specifications describe solutions and requirements describe problems | * Remember specifications describe solutions and requirements describe problems | ||
meetings_how_to.txt · Last modified: 2020-08-10 09:26 by river