10 Pines Blog

presentación agiles 2010 - automatización del deployment

agiles-2010 automatizacion agile

Las metodologías ágiles son muy claras respecto al siguiente punto: todas las tareas repetitivas que se realizan en forma manual deben ser automatizadas! Existen actualmente excelentes herramientas que nos ayudan a automatizar el build, las ejecuciones de los tests y el deployment de aplicaciones, pero comenzar a utilizarlas no siempre es una tarea trivial. En esta sesión presentaremos Maven junto con un grupo de plugins y herramientas que nos ayudaran a automatizar las tareas rutinarias cuando trabajamos con una gran aplicación multi-módulo Java enterprise.

13 Oct 2010

Agile is clean code

agile scrum

But … Isn’t this a requirement for all approaches? Why do I have the impression that in Agile, the technical aspect is more important? When I was at University, I remember vividly having heard (and unfortunately later repeated) that the programmer had one of the less important tasks in the chain of producing software. The most important, more senior and smarter people are the architects/designers that analyse and design the application, giving the programmers some diagrams that they ‘just’ have to translate into code. That seemed like an easy task!!

22 Jun 2010

Benefits of agile software development

agile

Incremental deployment: minimize time-to-market

Since agile processes deliver working software at the end of each iteration (typically around 1-4 weeks) and requirements are prioritized by business value, the organization might choose to release a version of the product as soon as a Minimum Marketable Feature (MMF) has been completed. This way the organization may start to perceive real benefits from the new product far before the development is completed.

10 Jun 2009

Agile Myths: Shorter iterations are stressful

agile

One of the first steps a new agile team has to undertake is to choose their iteration length. My general advice is to start with 2 weeks iterations, although I let teams choose the length they feel comfortable with. I believe it is better if the team make their own decisions and learn with the experience. I’m gladly surprised when a team chooses a short iteration length, but sadly that doesn’t happen very frequently. Usually the main argument I’ve heard in favor of longer iterations is that shorter iterations are stressful and there is not enough time to finish all the work.

16 May 2009