Webinar Title: Common Best practices for Software Development Teams in GÉANT – how to identify, share and implement
Date of delivery: 17/07/2020
Duration: 1 hour 1h (30-40min for presentation and two short demonstrations of CBP examples + 30-20 min for discussion/questions)
Host: Irina Matthews (GLAD) Welcome, Introduction, Chat room (questions) management, closing remarks
Presenter(s)/Facilitator(s): Branko Marovic (UoB/AMRES), Bartosz Walter (PSNC)
Maciej Łabędzki and Alan Lewis - CBP examples - case presentation
Affiliation (WP/Task): WP9 T2
Authors (created by): Branko Marovic (UoB/AMRES), Bartosz Walter (PSNC), WP9T2
Who will attend (target audience): GÉANT Software development teams: developers, tech leaders, product managers
Aim: The aim is to present how the current processes and approaches used in several GÉANT Software teams could leverage the extraction and identification of best practices. They are directional recommendations aimed to support more effective software development, covering all areas and goals that are relevant in the GÉANT environment. We will show, on selected examples, how they could be interpreted, adopted and deployed.
Webinar Aims: (please edit)
- Promote best practices
- Facilitate the adoption and development of best practices in the area of software development such as understanding stakeholders needs and requirements as well as dealing with issues of IPR, sw reviews
- Encourage collaboration in creating the best practices
- The Catalogue of Best Practices is a live resource that facilitates improvements in teams, it is immanently open for extensions and improvements
- Best practices are based on teams' experiences, teams decide if and how to implement them and collaborate to increase the value and help others improve
- The Software Management team offers guidance and support on implementing best practices
- Teams should pay attention to requirements and both needs and stakeholders evolve - the corresponding best practices and experience may provide some guidance
- Managers, customers and GEANT are concerned regarding the IPR; software reviews and GEANT WhiteSource service can help with libraries IPR and vulnerabilities
Webinar is recorded: yes
Communication schedule:
Pre-webinar
Date notification to b sent out: w/c 29 July
Date registration is opened: 29/07/2020
Post webinar
Evaluations TBC
Follow-on communication (how to access resources, contacts, next steps) TBC
Date of rehearsal: 10 am CEST
07/07/2020 1:30 pm CEST
Resources available can be accessed after the webinar - location: TBC
Webinar evaluation/feedback (link): TBC
Webinar outline
Webinar outline
Webinar Section | Resources | Content (what will happen) | Duration | Facilitated by |
Reception (prior to the start of a webinar) | 5min | GLAD | ||
Welcome note | 2min | GLAD | ||
Introductions | 3min | GLAD | ||
GÉANT Common BPs in SW development | 15min | Branko and Bartek | ||
| Demonstration of CBP examples, sharing the experience | Requirements management; dealing with libraries vulnerabilities and IPR with WhiteSource | 20min | Maciej and Alan | |
Q & A | 14min | Branko and Bartek | ||
Closing (what next?) | 1min | GLAD | ||
AGENDA - Main Body of the webinar
1. GN Common Best Practices (CBPs) - what they are and how they could help
2. Collaboration on CBPs - how they were produced and how teams can help + mention of the GSMM
3. CBP descriptions
4. Practice change/CBP example #1
Alan Lewis with inputs from WiFiMon
5. Practice change/CBP example #2
Branko Marovic Bartosz Walter - Maybe about stakeholders management (identification + communication strategy)?
6. Feedback on needs and ideas; initiate getting the feedback, help people get involved; Further directioning of CBPs;
Common Best Practices related questions to be observed in examples
- The problem that we had and how it reflected on outcomes?
- What we have tried and how we eventually addressed the issue?
- Where the adopted practice and tools came from, particularly if that was from GN?
- Possible alternatives and, based on our experience, what did work and what did not work very well?
- What are the effects of this new practice and related tools on our work and outcomes?
- What can be applied directly and what should be customised or omitted?
- How other teams could make use of this and how we could help?