Technical Director. 2% SOCCER Producer 2%
Technical Director. PRESENTER shall designate a TECHNICAL DIRECTOR (TD) with decision making authority who will be present, responsible for, and accessible to ARTIST at all times during LOAD-IN, SET-UP, TECHNICAL REHEARSALS, PERFORMANCES, STRIKE AND LOAD-OUT. STAGE REQUIREMENTS
Technical Director. Additional Technical Directors may be required at the discretion of the Auditorium Supervisor. The TDs’ services will be charged by the MSDWC to the Lessee at the hourly fee set forth on the Fee Schedule (see Attachment #1) for the number of hours stipulated in the Agreement.
Technical Director. The TD will oversee all events that occur at the PPAC. The TD’s services will be charged by the MSDPT to the Lessee at the hourly fee set forth on the Fee Schedule (see Attachment #1) for the number of hours stipulated in the Agreement.
Technical Director. When staffed, the Technical Director is responsible for developing a logistics plan for the preparation and installation of the technical elements of a production • Oversees the installation of scenic, lighting, sound elements that require stage craft expertise or adult supervision Stage Manager: • When staffed, the Stage Manager is responsible for calling cues for the performance from tech/dress rehearsals through final performance (minor role). Directors may require a stage manager throughout the rehearsal/performance process to take blocking and production notes (major role) Faculty Advisor: • When staffed, the Faculty Advisor may be asked to perform a range of specific tasks, such as:
Technical Director. Provides Technical oversight and guidance on architecture and delivery of development. Project Process The project process is managed by a hybrid agile process. All tasks are estimated using story points which are then prioritised and organised into fortnightly sprints. Each week during development the Delivery Manager for the project prepares sprintly (fortnightly) reports including the below: • Project summary • Velocity • Stories completed • Outstanding risks, issues and dependencies • Recently resolved risks, issues and dependencies • Key milestones outlined/achieved At the end of each sprint a demo is held. The aim of the demo is to review the work completed, to walk through the functionality of the application and assess if any changes are required. Red Ant will provide the application as a release to install on the client devices for internal demos. At the start of each sprint the delivery team then re-prioritise the current workload, re-plan the sprints accordingly and place any de-prioritised items to the development backlog to be addressed in later sprint. The sprint before a milestone release is designated as a QA sprint. The app feature set is frozen, in- depth testing is carried out, and the remaining time is spent fixing any issues that would prevent release. The final release candidate application is released to the client for acceptance testing and validation.
Technical Director. The Technical Director is responsible for a technically acceptable television production as assigned and is in technical charge of the engineering crew during such production. When the production requires the assignment of a Director or Producer, the Technical Director will follow the instructions and lead of the responsible Director or Producer.
Technical Director. (a) The regular workweek will be thirty- five (35) hours Monday to Sunday. The hours will be set over the seven (7) day period and may include split shifts. This is a ten (10) month position.
Technical Director. The PRESENTER agrees to designate a Technical Director with decision making authority to be present, responsible to, and accessible for consultation with the COMPANY at all crew calls.
