One of the main problems in the development work is the difficulty to maintain and publish documentation of a project. As any manual work, it tends to be delayed and eventually forgotten. In the User Service Team in eDreams ODIGEO, we started one year ago a process to automate as much as possible these steps.
So let’s talk about a sensitive subject… What’s the point of WIP (work in progress) limits? More precisely why do we have WIP limits on our Kanban boards? Surely we should be able to work on the tickets that are most important and be “flexible” enough to switch our focus should we need to.
Whether it’s the vibrant startup scene or the warm climate and cultural appeal, Barcelona is now being hailed as a go-to destination for the tech savvy. According to the latest technology industry trends, Barcelona is still among the top 5 startup and innovation hubs in Europe for 2017. So what makes Barcelona so good at
We all know that writing good software is tough and difficult, it’s not only about functional requirements, but also about robustness, maintainability, scalability and testability. In the android native team at eDreams ODIGEO, we researched about which architecture could be the best to solve our problems and to help us deliver quality software. Here is
Building top-tier software is a must at eDreams ODIGEO (eDO henceforth). Thus, in our strive to reach the highest quality for end-users, we try to apply top standards in our product. This effort is coal-and-ice in every single area of our development process, but there is a special section where it stands out even more,
“How long will this take?”. How many times have you been asked this question? In this article I will try to help you thinking on this from a different perspective.
The Kanban method has become a key part of eDreams ODIGEO because of its evolutionary change approach. Kanban manages change by following these three principles: “Start with what you do now”, “Agree to pursue improvement through evolutionary change” and “Encourage acts of leadership at every level”. In this article I’ll introduce how we are doing this at eDreams ODIGEO.
Tests are key to deliver good quality to the customer, which of course is one of our main focuses. But testing this by hand usually takes too much time, time in which the customer is not benefiting from your feature. In this article we explain how we automated most of our tests of the Front-end with the help of Selenium, Cucumber and NodeJS among other technologies, which gave us the ability to speed up a lot the number of releases and time to market.
We are excited to release TableViewKit 1.0 – an open source framework which is a core part of our apps: eDreams, Opodo, GO Voyages (and soon Travellink). The framework allowed the eDreams ODIGEO iOS mobile team to set up a complex layout easily, while improving the modularity of our codebase. History TableViewKit was developed to
Concepts like continuous delivery, time to market or innovation are very important at eDreams ODIGEO (eDO). Working on a product like ours makes us focus on the customer. This means that we want to bring the features to them as soon as we can. The present article covers how we manage each release in the front end team and the challenges we face to take decisions around it.