meetings_how_to
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| meetings_how_to [2020-06-01 15:09] – [Avoiding Bikeshedding] tkerby | meetings_how_to [2020-06-01 15:10] – [Think Problems] tkerby | ||
|---|---|---|---|
| Line 39: | Line 39: | ||
| Some general points on how to collaboratively solve problems. Key thing is to consider the problem fully before we all jump in with possible solutions. | Some general points on how to collaboratively solve problems. Key thing is to consider the problem fully before we all jump in with possible solutions. | ||
| - | ==== Think Problems | + | === Think Problems === |
| * Understand the problems in detail before considering solutions | * Understand the problems in detail before considering solutions | ||
| * Listen to all stakeholders, | * Listen to all stakeholders, | ||
| Line 51: | Line 51: | ||
| * Remember specifications describe solutions and requirements describe problems | * Remember specifications describe solutions and requirements describe problems | ||
| - | == Think Emergence == | + | === Think Emergence |
| * Understand how your solution works in the end application - how does it interface, what is its boundary? | * Understand how your solution works in the end application - how does it interface, what is its boundary? | ||
| * Consider the environment in which it is operating and how it may interact - what negative or positive behaviours or consequences may emerge? | * Consider the environment in which it is operating and how it may interact - what negative or positive behaviours or consequences may emerge? | ||
| * Identify how it may go wrong and mitigate those effects | * Identify how it may go wrong and mitigate those effects | ||
| - | == Think Analysis == | + | === Think Analysis |
| * Consider multiple possible solutions and analyse trade-offs against the requirements you have gathered | * Consider multiple possible solutions and analyse trade-offs against the requirements you have gathered | ||
| * Iterate - start with simple quick proof of concepts and use them to learn | * Iterate - start with simple quick proof of concepts and use them to learn | ||
| - | == Think Validation == | + | === Think Validation |
| * Validate early to identify changes and errors as soon as possible | * Validate early to identify changes and errors as soon as possible | ||
| * Constantly communicate with stakeholders in case their needs change | * Constantly communicate with stakeholders in case their needs change | ||
meetings_how_to.txt · Last modified: 2020-08-10 09:26 by river