Find the missing stakeholder
kind: drill
A team builds a system that stores which student borrowed which piece of lab equipment. They list: students, the lab supervisor, themselves. Who is missing, and what can that person do to the project?
Solution
At least: whoever operates the server afterwards (can refuse to host it), the school’s data protection contact (personal data plus borrowing history), and the teacher who accepts the project. Any of them can stop the project at the end, which is the most expensive moment to be stopped.
Rewrite five wishes as goals
kind: drill
Rewrite: "easy to use", "secure", "modern", "reliable", "works on phones".
Solution
Each needs an observable action and a condition, for example "a first-time user completes a booking without instructions in under 90 seconds" or "the site is usable at a viewport width of 360 px without horizontal scrolling". If you cannot state how it would be checked, it stays a wish — and it belongs in the proposal as one, not in the goals table.
Write the goals and non-goals for your project
kind: project
Fill in the goals table and the non-goals section of your charter — at least three goals, each with the evidence that verifies it, and at least three non-goals.
Name the competition between two goals
kind: drill
A team writes two goals: "members can enrol in courses themselves" and "no personal data leaves the school network". Are these competing, complementary or neutral — and what has to be decided?
Solution
Competing. Self-service enrolment wants an account, a login from home and therefore a reachable server; the data goal wants the opposite. Neither is wrong, and averaging them produces a system that is half reachable and half protected.
The decision belongs in the charter, in one sentence: either enrolment happens only on the school network (the data goal wins, the convenience goal is reduced to a non-goal for this year), or the data is reachable from outside under stated conditions (consent, transport encryption, deletion on request) — in which case those conditions are themselves goals with their own checks.
Put a goal of your project through the four questions
kind: project
Take one goal from your charter and answer, in writing: Wozu? Für wen? Endergebnis? Erfolgskriterien? If question two has no named stakeholder, or question four no observable condition, rewrite the goal — or drop it.