activities for Live-Trainings
Kombinationen for synchrone Trainings with Vor-/Afterbereitung in Moodle.
Quick overview
This page describes the working standard for activities for Live-Trainings – with a focus on concrete decisions rather than general guidance.
The main focus here is when which activity genutzt becomes and which einstellungen standardisiert are so that teams apply the same standard.
The standard only becomes traceable through linked evidence such as example courses / screenshots and through documented edge cases/exceptions.
When this page helps
Typical situations in which this page adds value as a working document, and where another document is more appropriate.
Typical use cases
- when activities for Live-Trainings as a reusable Moodle standard with clear requirements for activity goal and didaktischer einsatz should serve
- when authors or trainers work inconsistently on when which activity genutzt becomes
- when Quality assurance and approvals with example courses / screenshots should be documented in a traceable way
- when Support- or course feedback points to a typical pitfall (e.g. activity fits didaktisch not to the goal)
Less suitable when
- when activities for Live-Trainings only about a one-off individual case without need for standardization applies
- when a detailed project ticket or a technical step-by-step guide is the better fit
Recommended process
A pragmatic sequence that works in practice, from scope to review.
- Briefly describe the use case and target audience for activities for Live-Trainings briefly describe; from that scope and expected learning outcome derive the scope and expected learning outcome.
- standard setup/configuration define, especially when which activity genutzt becomes and which einstellungen standardisiert are.
- Use test users or a reference course to check whether activity goal and didaktischer einsatz work in practice.
- Quality assurance/approval carry out and link evidence such as example courses / screenshots link.
- After Livegang feedback auswerten and error patterns such as „activity fits didaktisch not to the goal“ as pitfall add.
Decision rules
activities for Live-Trainings is well documented, when rules, Edge cases and Evidence so clearly are, dass teams so that without additional coordination work can.
scope & Wirkung
For activities for Live-Trainings first define the scope clearly: Activitysziel and didaktischer Einsatz.
approvalregel
decisions about when which activity genutzt becomes and which einstellungen standardisiert are not implizit lassen, sondern roles and approvals explicitly benennen.
Exceptions cleanly halten
Allow exceptions only if they do not dilute the standard; especially relevant here are konfiguration, gruppen- and bewertungsoptionen.
Verifiablekeit
Verifiable is the rule only, when example courses / screenshots and konfig-evidence cleanly verlinkt are.
What should be documented
Here only the spezifischen Inhalte about activities for Live-Trainings maintain; general documentation rules remain in the centraln guideline. Central guideline.
The page is good when a substitute can apply or review the standard without first collecting tribal knowledge.
scope
terms, scope and boundaries about activities for Live-Trainings specify in concrete terms, including activity goal and didaktischer einsatz.
Concrete Parameter/rules
Den standard so record, dass when which activity genutzt becomes and approval-/testschritte primarily livegang eindeutig entschieden are.
evidence
Name and link evidence directly: Beispielcoursee / Screenshots, Konfig-Evidence, Quality assurance-/Pilotfeedback.
Versionierung
Aktive Exceptions, the latest change and the next review belong on the page—especially for topics with konfiguration, gruppen- and bewertungsoptionen.
Common pitfalls
This section captures real-world pitfalls from activities for Live-Trainings; general guidance belongs in the central guideline. Central guideline.
- scope driftet: activity fits didaktisch not to the goal.
- the rule is too abstract: Standardeinstellungen variieren je Trainer.
- evidence is missing: Technikcheck erfolgt only in the Admin-Konto.
- the exception gets out of control: Technikcheck erfolgt only in the Admin-Konto.
Moodle reference (official docs 5.1)
Kurze Verweise on the offizielle Moodle documentation for activities for Live-Trainings. So remains this Page AFANDI-spezifisch and vermeidet doppelte Grundlagen.
Official references
Documentation focus
- Live-Training-Mix with Interaktion and Afterbereitung (Feedback/Forum) document.
- UI path, role and test case record explicitly (not only the desired target state).
- Mark deviations from AFANDI standards separatelyely so that updates remain easier to review.
Review & maintenance
Check this Page gegen reale processes about activities for Live-Trainings – not only gegen the Wortlaut. Entscheidend is, ob standard, Exceptions and Evidence in the Alltag contribute.
- Passt the activity still to the Use case?
- Are Standards in the courses erkennbar?
- Gab it recurring Supportthemen?
- Are Evidence and decisions about activities for Live-Trainings weiterhin fully and auffindbar?
Review focus for „activities for Live-Trainings“: Moodle-Operations; check especially activity goal and didaktischer einsatz.
Useful metrics
A few metrics are enough – what matters is that they trigger decisions or improvements.
For „activities for Live-Trainings“ Kennzahlen directly an when which activity genutzt becomes and the most frequent Praxisrisiken koppeln.
Activitysnutzung
Einsatzhäufigkeit je Activitystyp
Interval: quarterly
Technikfehler
gemeldete Probleme for Nutzung/display
Interval: monthly
Pilotfeedback-Quote
Anteil neuer Setups with Pilotfeedback
Interval: quarterly
Next steps
Add jetzt the concrete Entscheidung about when which activity genutzt becomes incl. Verantwortlichen, Datum and Verweis on example courses / screenshots.
On „activities for Live-Trainings“ make especially clear as the next step: which activity goal and didaktischer einsatz apply in the standard case and which exceptions are time-limited.