Scrum Methodology & it’s Practical Use at CVCE

Services and tools developed by the Digital Humanities Lab for must cater to a variety of target audiences and their specific needs. More often than not, at the start of projects, these needs are not yet fully developed and are highly uncertain. So whilst we have a detailed overview of a product and a corresponding set of basic user requirements, it is not always possible to plan at the the inception of a project exactly what detailed form the end-product will take.  The user needs and knowledge become clearer and more established during the iterative process of technological development, which can stimulate creativity, discussion and facilitate the emergence of further user requirements. Therefore, for future projects starting between 2014 and 2017 we are looking to adopt a pragmatic methodology that enable us to efficiently move from an idea to a stable product.

We aim to use an empirical approach for developing projects and their associated products, through the adoption of the Scrum framework. The Scrum framework is a methodology for developing and sustaining complex products. It is suited to circumstances where solutions are required for complex adaptive problems requiring creative approaches (source? Mountain goat?). It is based on the following realisims:

  • You can’t plan your way out of uncertainty
  • The point in a project when you know the most is when it is complete

With a focus on highly user-centred development process that places user needs (and their uncertainty) at its heart, scrum affords transparency of the development cycle to our internal stakeholders (researchers in European integration studies) and will ensure best value to our external users (scientific communities, teaching and lifelong learning communities, society at large). It will allow inspection of products regularly, starting at an early development stage.  It also provides a framework to adapt products based on the users’ knowledge gained during the development process. Thus, it should help us deliver more robust, useful and usable solutions.

What is Scrum?

In essence Scrum is a methodology based on AGILE, where product requirements and solutions evolve as a consequence of collaborations between teams, product owners and their stakeholders. Scrum can be applied to many different types of projects but is commonly adopted by software development projects as it is highly suited for rapidly changing or emergent requirements, with the aim to create software delivers more value ( and can be summarised in the following high level, simple steps:

  • A Product Owner creates a prioritised, ordered list of items (akin to a wish list) known as a product backlog
    • Often the items are written as user stories
    • Items at the top of the list are written with more detail
    • The backlog is continuously evolving
  • Then in a sprint planning meeting, a subset of the items on the product backlog are selected  by the scrum team and placed into a sprint backlog.
  • The sprint backlog forms the tasks and activities of the a sprint
    • a 1 to 4 week period within which the items on the sprint backlog must be completed
  • During the 1-4 week sprint period a 15 minute daily fixed scrum meeting
    • Same time, same people, same place .
    • The aim is to understand:
      1. What work was completed yesterday?
      2. What is planned for today,
      3. Are you facing any problems?
  • The ScrumMaster helps resolve any impediments to progress during the sprint
  • Following the completion of a Sprint, there should be a potentially releasable iteration of product that can be shown to the product owner and stakeholders during a sprint review
    • If the sprint is two weeks long then it is suggested a sprint review meeting should last two hours.
  • A sprint retrospective is held to review the sprint
    • what went well?
    • What could have been improved?
    • What actions to take in the next sprint.
  • Repeat process for the next set of items ordered at the top of the backlog

    Scrum Methodology , source: click on image


How will we implement Scrum methodology at CVCE?

The first step is to identify a few projects which would really benefit from a Scrum approach and begin from here, then we will use a snowball effect to then adopt it for other projects after the benefits and business value are clearly visible to all our stakeholders. I have been on the Scrum Product Owner training course (which I enjoyed immensely) and my college has participated in the ScrumMaster training course.

At the CVCE there will be three main departments involved developing projects and products using Scrum

  1. European Integration  Studies (EIS)  – comprising of social science and humanities researchers
  2. Digital Humanities Lab (DH Lab) – comprising of digital humanist researchers who are the interface between EIS and DevOps.
  3. Development & Operations (DevOps) – comprising of computer scientists and media technologists

The project that we have selected to be our pilot for the adoption of Scrum is one where we are working on evolving and improving the interface, our data model and data enrichment process for the CVCE document object repository. As part of this evolution we are integrating a metadata zone within the interface and data model to enable EIS to easily provide metadata in line with the international standards of Dublin Core, for all the objects they create. This will be combined with a citation generation service to provide internal users (CVCE historians) of the repository and readers accessing the repository via the website with automatically generated citations for all resources, conforming to ISO 690 numeric French standards. To complement this, there is a need to develop a metadata quality control process to ensure consistency of the authority lists that are created as part of our metadata policy.  It is this project that we are implementing with Scrum.

citation user stories

Example of our organised user story descriptors for items associated with citations

A member of the DH Lab is the product owner ,EIS our stakeholders and various staff from DevOps and the DH Lab comprise the scrum team. The product backlog is emerging based on sets of user stories derived from interviews with users and observations of how they are currently working and the strategic objectives. We are working in 2 week sprints cycles and are currently half way through sprint 4.

To mange the scrum we are using JIRA, to both manage the backlog and organise and plan our sprints.

Thus far we are enjoying working in this way and our stakeholders appear happy. I will post further updates and details of our progress as they emerge.

Talk of Europe – Travelling CLARIN Campus

In October we will be participating in a one week creative camp, organised by the Talk of Europe – Travelling CLARIN Campus project (ToE-TCC). Funded by Dutch agencies NWO and OCW, the project follows up on the PoliMedia project, which linked entities in Dutch parliamentary records to corresponding media sources archived by the Netherlands Institute for Sound and Vision.

The CVCE was successful with two proposals submitted to ToE-TC, both focused on exploring social graphs.

  1. Visualising Co-occurrence networks of the plenary debates of the European Parliament
  2. Exploring the potential of multimodal graphs for modelling European Plenary Debates

We are excited to participate in travelling campus, as we are looking forward to finding new ways of structuring parliamentary data. We look forward to exploring how we can use such tools, techniques and data structures to shape future developments of the CVCE research infrastructure and develop new ways of exploring our collections.

There are three aims for the one week event, scheduled for 6-10 October 2014:

First Aim: “To translate the proceedings of the European Parliament debates (europarl) to CLARIN standards. In other words, the europarl data is curated to linked data so that it can be linked to and reused by other datasets and services. An interesting aspect of this dataset is that its available in 21 languages, enabling to link to other datasets in as many different languages. (…)

Second Aim: To research how this linked data can be exploited for use by humanities scholars. The combination of linked datasets with the base available in 21 languages should allow research questions not yet feasible. As such, interlingual comparative research through digital tools becomes possible. In comparison, where PoliMedia focused on how Dutch debates were covered in the Dutch media, the europarl data could be analysed to compare how European Parliament debates are covered in Dutch versus Polish media. Political scientists could analyse how subjects from EP debates relate to subjects in debates of national parliaments. In order to build tools helpful, we will investigate user requirements and possible research questions from humanities scholars. This second aim will be undertaken by Max Kemman, Martijn Kleppe and Henri Beunders from the History department of EUR.

Third Aim: To spark a transnational, European collaboration to create tools for scholars to analyse linked datasets. To this end, three meetings of a week will be organised in which teams from all CLARIN countries are invited to participate. Think hackathon, but a week long and with a European focus.”

The European parliamentary debates have been processed and are now available in RDF format. RDF, commonly associated with the buzz-word “Linked data“, “is based upon the idea of making statements about resources (in particular web resources) in the form of subject–predicate–object expressions. These expressions are known as triples in RDF terminology” (Wikipedia article on RDF). RDF is highly flexible and allows users to formulate very precise queries on their datasets.

A simple social network graph

The first proposal, in cooperation with Dr Fintan McGee of our neighbouring research centre CRP Lippmann, will explore the extent to which multimodal network analysis can be fruitfully applied to the study of the parliamentary debates. Where one-mode network visualisations can only represent one type of actor in a network (e.g. people), multimodal networks are capable of representing multiple types of actors, e.g. people, institutions, texts and places. This approach bears the potential to represent more closely the complexities of real-world networks.

An example of a geographic social network
(source: Nodegoat).

The second proposal was submitted with Lab1100, a Dutch company which develops Nodegoat. Nodegoat offers its users with simple yet powerful instruments to create relational databases online and visualise their data in form of maps and network graphs. Lab1100 will develop a way to link ToE-TCC data directly to Nodegoat using the formers SPARQL endpoint. This will ensure very quick and highly flexible data import and visualisations of the data.

CVCE researcher Marten Düring and Frédéric Allemand, Coordinator of the European Integration Studies Department at CVCE will participate in the project.

Digital Humanities LAB at CVCE – why we have a blog

The Digital Humanities lab at the CVCE is an interdisciplinary team, whose goal is to participate in the development of the CVCE’s innovative research infrastructure for European integration studies.

This blog will provide the DHLab with a forum for the exchange of information and ideas associated with our ongoing digital humanities projects. It will provide the opportunity to discuss the CVCE’s projects we are working on and the issues and challenges we face developing tools and techniques for multi-lingual digital  research environments using a wide variety of data types (pictures, text, video, maps cartoons etc) for developing novel enhanced publications.