Joinup development governance

Possible scenarios for collaboration

Meeting with delegation from Vietnam, Australia and New Zealand

22 October 2013

Szabolcs SzekacsSzabolcs.szekacs@ec.europa.eu

Click to edit Master title style

Governance of Joinup

Possibilities for collaboration

Q & A

2

Click to edit Master title styleJoinup – technical platform supporting many ISA actions

and other projects

3

Community building

IMM

EFIR EIRA SEMIC

NIFO

Click to edit Master title styleManagement of development and operation of Joinup in

the Commission

4

DIGIT.B2Business owner /

Governance

PWC (contractor) Functional specs,

testing, community building

DIGIT.A3 Solution provider

DIGIT.C hosting

FPIS team (intramuros)

deployment, technical helpdesk

Everis (contractor) development

Click to edit Master title styleGovernance of the Joinup development

5

DIGIT.B2chair

DIGIT.B2Business owner /

Governance

PWC (contractor) Functional specs,

testing, community building

DIGIT.A3 Solution provider

Everis (contractor) development

Community Building action (DIGIT.B2)

GOPA (contractor)

SEMIC (DIGIT.B2)

PWC (contractor)

EFIR (DIGIT.B2)

PWC (contractor)

EIA (DIGIT.B2)

Deloitte (contractor)

Click to edit Master title styleSteering committee meetings

6

• How often : based on sprints (4-6 weeks)• Participation: Steering committee members• Scope:

• Current status of development – report on decisions taken at last meetings

• Report on the Joinup platform• Metrics on the usage of Joinup

• Future developments in n+1 and n+2 sprints• Bug fixes• New development

Click to edit Master title styleFuture developments

7

• Sprint 6: ADMS.SW implementation (partial) + bug fixing

• Sprint 7: NIFO quick sprint (2 weeks)• Sprint 8: EFIR implementation (including finalizing

the ADMS.SW• Sprint 9 : small improvements + integration with

Nexus• Future:

• Machine translation integration (EU service)• Federated solutions• eLibrary items• Other content?

• Integration of the EIRA (Reference Architecture)

Click to edit Master title style

Possibilities for collaboration

Governance of Joinup

Q & A

8

Click to edit Master title stylePossibilities for collaboration

9

Getting the right information at the right time

Issue level Sprints level

- Pulling information using JIRA, confluence

- Reporting new bugs, improvement requests

- Pushing information: Once in every 4-6 weeks, minimum 3 working days before the internal meeting- Written feedback appreciated

Click to edit Master title stylePossibilities for collaboration

10

Contributing on many levels

Commission - Joinup

MOST - Vietnam- Functional specs- GUI design- Bug fixes- Development of new

functionalities- Testing- Modularisation- User help update

OTF – AU NZ

Click to edit Master title stylePossibilities for collaboration

11

Parallel development, conflict resolution

Commission - Joinup

MOST - Vietnam- Integration testing – quality

monitoring- Parametrisation- Modularisation- Each organisation is in

control for their development, but work together to avoid duplicate work / forking

OTF – AU NZ

Click to edit Master title style

12