News Feed
Forgot your password?
New user?
D11.8 Report on internal training
TAS3 Report on internal training
December 2009 version (v1.1) of deliverable D11.8 (Report on internal training) is open to public comments, feedback and review !
All feedback welcome !
You could download it and publish comment from here:
(you need to login first to put a comment)Executive Summary
This deliverable reports on internal training activity for the TAS³ project during the 12-month period from January-December 2009. The document is intended for reviewers and project team members and follows on from the D11.7 report delivered at PM12.
The main aim of this phase of activity has been to provide harmonised training to the consortium partners which reflects the current state of the project; key objectives have continued to be: ensuring that internal partners develop and explore a common understanding and application of the concepts and methods used, sharing of knowledge and results arising from the work, and training of technical staff in concepts and technologies to be used for building software components to be used in the demonstrators.
Specific training activity in the first half of the year was limited by the need to concentrate partners’ efforts on development of the draft project architecture and redrafting of key deliverables from Year 1. However increased activity and face-to-face meetings in the second half of the year, with a significant increase in both informal and formal training activities, have sought to address this. The systems to support training have now been stabilised with the establishment of new and improved tools, supported by a fresh, customisable online training environment.
The majority of planned training events, including a series of developer integration workshops, were successfully completed; some of these were delivered through more informal routes than originally anticipated. In addition the project conducted a range of short, ad hoc training type activities, including support for project administration tasks, training partners in the use of and protocols for the new project portal and related tools, setting up technical staff involved in production of technical components in use of systems for tracking and monitoring software development and use of the newly-established Pool system administered by WP12.
In addition communication regarding training requirements, activities and outcomes has been linked to regular project activities and communications (in particular the new TRAC project portal which also acts as a repository for key project documents). We have been able to streamline informal training and establish exchange of ideas using the RFC (Request For Comment) facility. For internal partners, this environment needs to be seen as acting in tandem with the more structured Moodle online training environment. We anticipate that this will be more heavily used in later stages of the project when training materials will be released first to pilot partners and then to the wider community.
Training in the second half of the project will need to focus on topics such as legal issues, trust and trust perception, users and usability and supporting delivery of pilots. Pilot training design will need to encompass further training needs analysis to meet the specific needs of particular pilot participants, as well as evaluation of end user perceptions. In anticipation of the final phase of the project, parallel materials on set up and integration of TAS³ modules with live systems will be developed and tested, and further set up training will be derived to support implementation of the project business plan.
