You treat a festival as a temporary city: gates, power, crews, artists, and the streets around the site. The cases sit in Warsaw's festival calendar. You do not inherit a venue contract or a city's licence. Seminars run online, with a campus studio week when the cohort is in Warsaw. The year ends with a week plan, not a slogan about culture.
MSc Festival Operations is taught as one award, not a list of unrelated modules. The published length is 18 months, and the credit total is 36. Students move from Festival systems through Festival systems; Temporary power and crowd flow; Artists, tickets, and contracts; Crews and volunteers; Permits and neighbours; Festival week plan, and finish on Festival week plan.
Each course has a question, a method, and a submission. In this field, students find where time or cost is lost and recommend one operational change. Reading is a process map, a capacity note, and a disruption case. The artefact a marker expects is a recommendation for one lane, site, or service with the cost and the risk.
The award is built so that a graduate can do the following in practice: Write a run-of-show with a stop-admissions time Cost a volunteer and crew rota Map crowd flow at a gate
Teaching assumes the student can read a source, attempt a problem before the seminar, and revise after feedback. Attendance at live seminars is part of the design. The capstone or final course must use the methods of the earlier courses; a project that ignores them does not pass.
The pages for each course name the topics that are examined. Those topics are the syllabus. A brochure line is not a substitute for them.
The credit total on this page is the sum of the courses in the curriculum. Assessment is the work named on each course.
Rozpocznij aplikację
Kampus i miasto
Nasza historia od 1969
