E-Research Endeavours Workshop: Project Management

Here's a list of discussion points for the session on project management. Please feel free to add to this list:

Research proposals are sales documents, not recipes for running projects.
What models are there for managing the relationship between design and use and between 'designers' and 'users'?
What are the potential benefits and dangers of fostering strong end-user involvement in the design of e-Research technologies?
Just who do we wish to involve at any particular stage of development?
How can we ensure that involvement is seen as being worthwhile even if tangible benefits materialise only at a later stage?
On the other hand, how can we manage perhaps unrealistic expectations?
How can the often diverse requirements of different researchers be aligned sufficiently to make design feasible?
How can we assemble teams with the various required skills which may be necessary over the course of a project? How can we ensure that projects do not become critically dependent on a single person, esp. given the natural turnover in academic settings (short-term contracts, high upwards mobility)? How can we retain key members of staff over a longer period of time?
How to identify and manage the various risks involved in e-Research endeavours?
How to manage the relationship with the investigators to ensure that the project manager can act autonomously on a day-to-day basis but with their backing when needed?