…Or how to deal with code quality through Game of Thrones On 11th July we congregated to enjoy the last talk of the summer, from the BADG (Barcelona Android Developer Group) meetup in our eDreams ODIGEO canteen. Even though this Meetup group is Android-oriented, our last talk was more about how to deal with code
Some of us Java-users within eDO had the chance to attend to the latest edition of BCN Java Conf and now it’s time to reflect on our experience. The event was divided into three key areas: Methodologies and processes Cloud and microservices Java world novelties I have to admit straight up – after several years
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.
“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.
The main goal of the OneCMS team in Alicante is to migrate the existing OdigeO CMS called ONECMS, which is developed using #NET, to the IT common, that means using Java and the jBoss platform. We call it jCMS. I would like to share the OneCMS team’s experience with Specification by example (SBE). After assisting
