1 / 8

Caveat 1…

Projects for the “Real World” - some things to bear in mind Prof Mark Stiles - Staffordshire University. These are reflections from the Staffordshire Team working on the SUNIWE DeL Pilot Project. They should not be taken as criticism of any partner in the project

naida
Télécharger la présentation

Caveat 1…

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Projects for the “Real World” - some things to bear in mindProf Mark Stiles - Staffordshire University

  2. These are reflections from the Staffordshire Team working on the SUNIWE DeL Pilot Project. They should not be taken as criticism of any partner in the project The project is going very well but much more slowly that we planned! Caveat 1…

  3. This is all about project for REAL implementation - not “proof of pudding” Caveat 2…

  4. Communicating project aims, scope and development processes can be very hard without face to face meetings. The flip side is that... Time taken to arrange meetings that most project members can attend increases exponentially with the size and geographical spread of the project team Meeting with NON-project members will delay things. Talking takes time…

  5. You can never be too explicit about roles and responsibilities in the project team. You can never be too explicit about the aims, scope and development process for the project Be VERY clear…

  6. Prior to a bid - ensure scope and main aims are realistic. Ask questions like: does the data exist in all partners? does sufficient commonality exist to implement the same approach at disparate partners? are current systems capable of integrating with the project? what is the impact on the processes and procedures of the institution? Doesn’t have to be long-winded or detailed but should identify any project-killers Bidding requires more work…

  7. Be aware of skills required for the work and if those skills exist in the project partners. If not, need a plan for developing the team members or buying skills in. Implementation and handover has to be bulletproof. Extra effort is required to run project outputs in parallel with existing systems to allow testing and then seamless switch over or integration. Don’t forget the legal stuff!!! DP in particular is a problem, ask you will get conflicting information from the “experts” Skills & Implementation

  8. Impact on processes and procedures within partners needs to be assessed and integration with processes planned Sufficient weight needs to be behind the project to drive modification of processes and procedures required by the project Extra effort needed to to ensure the solution is designed to facilitate reuse, use appropriate standards, build on existing solutions, scale well, etc. Styling and presentation and branding - can look clunky/default/bespoke during proof of concept BUT need to be correct for production implementation. Do NOT underestimate the work required for this! The Real World…

More Related