Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Overview of Virtual Team projects"

From EGIWiki
Jump to navigation Jump to search
 
(313 intermediate revisions by 18 users not shown)
Line 1: Line 1:
{{TOC_right}}
{{EGI_Activity_groups_menubar}}
{{Menubar_VT}}
{{TOC_right}}
[[Category:Virtual_Teams]]


This page provides information about the "Virtual Team framework" and the "NGI International Liaisons" that have been established within EGI-InSPIRE, and about the Virtual Teams that exist within the EGI Community to engage with new user communities.  
<br> The following is a list '''Virtual team projects''', that have been initiated and run by EGI.  


*For background information please read the '''[[Virtual teams|introduction to the Virtual teamframework]]'''.
*For the list of NGI International Liaisons please go to http://www.egi.eu/about/ngis/NILs.html.


== Documentation  ==


== Context ==
Starting and finishing a project can be daunting tasks and they certainly depend on a sound understanding of what is to be achieved, by whom, for whom and by when. Defining the achievable aims and objectives of the project and the resources (human and material) that are realistically available are essential at the very start for any chance of success. At the end of the project, the output needs to be delivered to whoever commissioned the project - this needs to be backed by a Final Project Report that confirms (or otherwise) that what was promised at the beginning is being delivered at the end. A [https://documents.egi.eu/document/1991 Project Initiation Document and a Final Project Report] are available in template form as a source of guidance for all those starting new Virtual Team projects. These are not obligatory formats for VTs but all VT leaders should read the guidance. <!--


In 2011 the EGI-InSPIRE project revised its user engagement activities and defined a new structure for the NA2 work package within an updated Description of Work. The purpose of the restructuring is to improve the efficiency and flexibility of the interaction between the NGIs, EGI.eu and other organisations to achieve common goals in the field of "Engaging with New User Communities" (NA2 is titled Engaging with New User Communities).
== Reporting & management ==


The new structure consists of two key elements:
# '''Virtual Team framework''': The Virtual Team framework enables NGI and EGI.eu persons to initiate and participate in short living projects (Virtual Team projects) that focus on well defined, non-operational activities around the production infrastructure. These activities cover areas such as Marketing & Communication; Strategic Planning and Policy Support; Community outreach and events for new users; Technical outreach and support to new communities. Virtual Team projects focus around new communities and/or sustainability. The framework allows the EGI community to plan all related activities in conjunction and collaboration with the NGIs. The VT project framework was developed within the NA2 activity of the EGI-InSPIRE project, but it is open for NGIs, countries and regions that are not involved in NA2 or in EGI-InSPIRE. These entities can join existing Virtual Teams or propose new Virtual Teams.
# '''NGI International Liaisons''': The interaction between the NGI teams and EGI.eu on non-operational activities is undertaken through an "NGI International Liasions"(NILs in short), who are responsible within the NGIs for the delivery and interaction of non-operational tasks. Non-operational activities cover areas such as Marketing & Communication; Strategic Planning and Policy Support; Community outreach and events for new users; Technical outreach and support to new communities. The role of the NGI International Liaison recognises the complexity and diversity of each NGIs yet the need for these NGIs to be involved in pan-European, coordinated, non-technical activities of EGI. It is not necessarily the NGI International Liaison who undertake any of the non-technical activities, but instead they make sure the appropriate individuals or teams within the NGIs respond to any particular activity or issue that arises. These activities and issues arise within the Virtual Team framework, typically as requests to join a new Virtual Team or to react to some issue identified by a Virtual Team.


== What is a Virtual Team? ==
When reporting, please indicate:
* VT Project name
* Reporting period (start date and end date), e.g. "Mon 1 Apr - Tue 23 Apr".
* Work achieved over the period
* Work planned (for next weeks)
* Significant Issues/Additional support needed.
* Please also provide your assessment of how much remains to be done till completion.


The skills needed for EGI to successfully engage as a community with new users exist in many different organisations within EGI-InSPIRE and in the broader EGI ecosystem. It is foreseen that different members of EGI want to participate in different types of targeted activities that directly or indirectly relate to engagement with new users. The individuals needed to carry out such a targeted activity can be brought together by a Virtual Team in EGI. Virtual Teams provide a flexible and dynamic means to rapidly bring together certain members of the community for a well defined series of tasks to meet a specific goal that needs to be achieved in a relatively short period of time (on the order of weeks or months) before being disbanded. The focus of these Virtual Teams will be to either directly increase the number of EGI users (e.g. through integrating a new application) or indirectly (e.g. by raising the profile of EGI and an NGI through a NGI hosted event for its users). Virtual Teams have members from multiple NGIs and carry out a targeted action within the following activity domains:
==== Effort reporting ====
* Marketing & Communication
* Strategic Planning and Policy Support
* Community outreach and events for new users
* Technical outreach and support to new communities


Virtual Teams can be established and used to enable the development of a strategy for the long-term evolution of EGI, or to significantly increase both the diversity and quantity of users and communities exploiting the infrastructure for world class research. The application of the framework is limited only by the scope and imagination of the NGIs to commit resources to any particular goal. EGI-InSPIRE NA2 members can and should use their NA2 project effort through Virtual Teams in order to efficiently contribute to the coordinated, pan-European activities carried out by EGI in engaging with new users.
These projects are conducted via un-funded VT project teams and there is thus no formal mechanism for recording or reporting the level of effort expended in progressing each project.  Nevertheless, every good project manager should recognise the level of effort (time and other resources) required to progress tasks to completion, particularly when others are assigned to the work.


== Who are the NGI International Liaisons? ==
-->


{| cellspacing="0" cellpadding="5" border="1"
=== Active Virtual Team projects  ===
 
'''Projects are asked to use [[VT Template Wiki page]]'''
 
{| border="1" cellspacing="0" cellpadding="5" class="wikitable sortable"
|-
|-
! Country (NGI)
! width="300" | Project
! International Liaison's name
! width="100" | Area
! Deputy's name (if any)
! width="100" | Project status
|-
! width="250" | Project leader
| aa
! width="80" | Start date
yyyy-mm-dd <!--! Project website--> <!--|-
|[[VT Template Wiki page]] 
<b>Projects are asked to use this where possible</b>
|
|
|
|  
| yyyy-mm-dd--> <!--| [[VT Template Wiki page]]                  '''''All Projects are asked to use this where possible.'''''-->
|-
|-
| aa
| [[VT Life Science Data Integration|Integrating life science reference datasets in EGI]]
|  
| Platform porting
|  
| Running
| Fotis E. Psomopoulos/AUTH
| 2014-12-01
|-
|-
| aa
| [[VT Federated Data| Scalable Access to Federated Data]]
|  
| Technology
|  
| Running
| Lukasz Dutka/CYFRONET
| 2015-04-01
|-
|-
| aa
|
|
|-
|}
|}


== Processes ==


=== Establishing a new Virtual Team ===


1. The request to form a Virtual Team can come from any NGI or EGI.eu. The request must use the [http://templatetoadd VirtualTeamProjectRequest template] and must be sent to the vtc@egi.eu email address. The request must describe:
<!-- === Proposed virtual team projects  ===
* the resources being requested (What skillset does the Virtual Team aim to gather from NGIs?)
* the potential value to EGI
* the expected duration and effort required
* dates for the final and any intermediate outputs


2. The request is reviewed by the NA2 taskleaders of EGI-InSPIRE based on clearity, completeness and achievability. The request is rejected if it is not clear, not complete or not achievable. The technical content is not reviewed at this stage. Rejected requests can be resubmitted after modification and/or improvement.
{| cellspacing="0" cellpadding="5" border="1" width="80%"
|-
! width="300" | Project title
! width="100" | Project status
! width="100" | Deadline to join
! width="180" | Project leader
! Project website
|-
| Top applications and their user communities
| PLANNED
| No deadline
| Not known yet
| [[VT Top Applications]]
|}


3. The accepted request is forwarded to the NGI International Liaisons. The NGI International Liaisons are making sure that the NGI as a whole or appropriate individuals or teams within the NGIs respond to the participation request. The NGI decision process is treated as a black box. Some NGI International Liaison may decide on their own on participation, others may need approval from NGI Coordinator or from NGI members. Note that because Virtual Teams have a relatively short lifetime (up to six month), the window of opportunity for NGIs to respond is expected to be short too.
<br>


4. The positive answer from at least two NGIs is enough to establish a Virtual Team. Virtual Teams with one NGI cannot be established. The leader of the Virtual Team must be an individual from an NGI or from EGI.eu. If the team is lead by an NGI member then an "EGI.eu buddy" is provided for the team to facilitate the integration into the EGI ecosystem.
=== Potential virtual team projects  ===


=== Running a Virtual Team ===
{| width="80%" border="1" cellspacing="0" cellpadding="5"
 
|-
* The Virtual Teams need to run themselves and can choose management and meeting structure, methods and tools that are most suitable for them.
! width="300" | Project title
* The leader of the Virtual Team must be an individual from an NGI or from EGI.eu with support from his/her hosting organisation. If the team is lead by an NGI member then an "EGI.eu buddy" is provided for the team to facilitate the integration into the EGI ecosystem.
! width="100" | Project status
* Each Virtual Team has an entry in the EGI Wiki where - following a pre-defined template - the team must provide information about its goals, members and progress.
! width="100" | Deadline to join
* Each Virtual Team is provided with an email list under the mailman.egi.eu domain.
! width="180" | Project leader
* Virtual Teams can use the EGI Requirements Tracker, Applications Database, Indico, Training Marketplace, Helpdesk and other user-facing services to track issues, applications, events, etc.
! Project website
* The Ibergrid consortium within EGI-InSPIRE will provide a CRM (Customer Relationship Manager) system for Virtual Teams and NGI International Liaisons.
|-
* The leader of each Virtual Team must send a weekly email report about "work achieved, work planned, overall progress, issues, additional support needed" to the inspire-na2-leaders@mailman.egi.eu address. The report should be succint (a few lines of text)
| Establish an EGI VRC for Sound and Music Grid Computing (SMGC)  
* Each Virtual Team is expected to write blog posts in the EGI Blog based on its weekly reports.
| NGIs CAN JOIN
* Virtual Teams will be reported in the NA2 section of EGI-InSPIRE Quarterly Reports by the activity management.
| N.A.  
* Virtual Teams are expected and will be invited to contribute to EGI Newsletters, Leaflets, Workshops or other dissemination and marketing marterials and events.
| To be decided
 
| [[VT SMGC VRC]]
== Virtual Teams ==
|-
=== Current Virtual Teams ===
| Establish an EGI VRC for GAIA-Space Grid Computing
 
| NGIs CAN JOIN
<PLACEHOLDER FOR CURRENT TEAMS - input from NIL kick-off meeting>
| N.A.
 
| To be decided
=== Finished Virtual Teams ===
| [[VT GAIA-Space VRC]]
 
|-
No Virtual Team finished yet.
| Application Porting How to guide
 
| On hold
=== Proposed Virtual Teams ===
| N.A.  
 
| To be decided
<PLACEHOLDER FOR PROPOSED TEAMS - input from kick-off meeting and NA2 Virtual Team Projects document>
| [[VT Application Porting Howto]]
 
| Gender Action Plan
=== Rejected Virtual Teams ===
| PLANNED
 
| No deadline
No Virtual Teams have been rejected.
| To be decided
 
| [[VT Gender Action Plan]]
 
|} -->
== Further information ==
 
* [https://www.egi.eu/indico/getFile.py/access?resId=0&materialId=paper&confId=659 The New NA2: Engaging with new user communities]
* [https://www.egi.eu/indico/conferenceDisplay.py?ovw=True&confId=659 NGI International Liaisons Kick Off meeting, 10/Nov/2011]

Latest revision as of 14:42, 8 September 2015

EGI Activity groups Special Interest groups Policy groups Virtual teams Distributed Competence Centres


EGI Virtual teams: Main Active Projects Closed Projects Guidelines


The following is a list Virtual team projects, that have been initiated and run by EGI.

Documentation

Starting and finishing a project can be daunting tasks and they certainly depend on a sound understanding of what is to be achieved, by whom, for whom and by when. Defining the achievable aims and objectives of the project and the resources (human and material) that are realistically available are essential at the very start for any chance of success. At the end of the project, the output needs to be delivered to whoever commissioned the project - this needs to be backed by a Final Project Report that confirms (or otherwise) that what was promised at the beginning is being delivered at the end. A Project Initiation Document and a Final Project Report are available in template form as a source of guidance for all those starting new Virtual Team projects. These are not obligatory formats for VTs but all VT leaders should read the guidance.

Active Virtual Team projects

Projects are asked to use VT Template Wiki page

Project Area Project status Project leader Start date

yyyy-mm-dd

Integrating life science reference datasets in EGI Platform porting Running Fotis E. Psomopoulos/AUTH 2014-12-01
Scalable Access to Federated Data Technology Running Lukasz Dutka/CYFRONET 2015-04-01