| What | Probability | Impact (L/M/H) | Mitigation |
| Elewijt Center is not available (e.g. burns down) | <1% | H | Cancellation policy |
| Not all payments have been received in time | 99% | M | Agile Systems provides financial buffer |
| Webserver crash | 5% | M | Oy! |
| Participants arrive late for the OpeningSession | 99% | H | Start OpeningSession not too early (e.g. at 10:00am) |
| Participant gets (physically) hurt during conference | 1% | M | Insurance, Elewijt has medication available. Do they have a first-aid person? |
| Too little registrations or none at all (<20) | 10% | H | Minimum number of participants = 20; Cancellation policy --> correct nr of participants, workshop rooms and hotel rooms : 1 week before conference date |
| Too many registrations (>60-75) | 10% | L | Close registration; try booking additional room in Elewijt? |
| PayPal problems | | | People pay later -> have some financial buffer
In case of severe problems, people can pay cash at the conference? |
| Too many payments through PayPal (=delay in receiving money) | 50% | M | Financial buffer |
| Unpaid registrations | 50% | L | Require payment in advance + financial buffer |
| More participants than will fit in the Elewijt hotel rooms | 10-20% | M | Hunt and select 3 alternative hotels, possibly through Elewijt |
| Traffic problems (eg train or plane strikes) --> a lot of participants simply can't get there | | | Start the (official) OpeningSession later; let the participants that are present self-organise; do an OpeningSession each morning |
| Not enough session proposals/Too many session proposals | | | Not a problem - this will sort itself out during the OpeningSession |
| A princess is scheduled to arrive at the conference centre | 50% (it happened in one of two xp days) | M | possible change of rooms, time needed to re-negotiate with elewijt |
