Topics for discussion as follow up from the 2013 structural review

Please add your topics for discussion :-

  1. there was a common concern, that whilst shared offices and pandemic planning have helped, there is still a degree of SILO culture (between the units).
  2. USU, in particular, had concerns that they weren't always informed of imminent user facing changes.
  3. there have been occasions when USU haven't been able to contact anybody in a particular unit (by chat/email/phone/in-person).
  4. we need to formalise and resource our support for self-managed platforms
  5. small devolved budgets for units
  6. Formal time reporting: This seems an unnecessary burden, and anyway, the results don't seem to be used. Do we want to continue with this?
  7. Possibly unhelpful emphasis - 'Development good; Operational bad': I don't agree with the philosophy (and, anyway, the demarcation often isn't as easy to make as one might think) but it seems to drive some things here - not least the time reporting above. It might be better to concentrate on the more general aim of providing good-quality systems which serve the current/future purposes of the School, and to judge our success in that by looking at what is (or is not) actually produced.
  8. Sometimes, what seems like the uncritical transmission of instructions from higher up: An example from a couple of years ago was the proposal for 'continual appraisal'. Where did that come from? (And where did it go?) Another example might be the suggestion that computing staff 'want' to be more involved with teaching. More sensitivity (at least) to those of us not in the direct chain of command might help. This might just be a matter of more communication/explanation.

Summary of discussion (28/10/14)

-- AlastairScobie - 15 Oct 2014

Topic revision: r8 - 03 Dec 2014 - 16:34:42 - AlastairScobie
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
This Wiki uses Cookies