Software de Outsource

Ecosistema ágil del desarrollo del software

¿Cuál es un ecosistema ágil?

El ecosistema ágil es un concepto extendido de la metodología que tiene 3 características: estructura apenas suficiente, valores de colaboración, y perspectiva chaordic. Puesto que el nombre no dará cualquier pista a usted en cuál él realmente es. .we mirará cada uno de estas características detalladamente.

Es la cobertura más amplia que la metodología normal que le hace un ecosistema. La metodología no toca mucho en el factor humano del desarrollo tal como la estructura de organización que se cubre en “apenas suficiente”, y colaboración y trabajo en equipo.

Metodología apenas suficiente.

Esta característica es una reflexión de la característica chaordic - en este caso refiere a la estructura de organización, que es muy aerodinámica (lo suficiente, apenas suficiente) para ser flexible reaccionar a los cambios. En un ambiente ágil el control está más en cómo hacer a los diversos individuos para trabajar junto en equipo, en vez de hacer cada igual (a través de documentos de proceso rigurosos) de modo que (o asumido) sea convertido en automáticamente un equipo.

In programmer language - the old method of team is an ARRAY - something that hold similar type of element, while Agile team on the other hand is a RECORD - where each element in the RECORD is different, and each one serves its own function the best, but still overall they work together to construct the RECORD.

Collaborative values.

In the old development method, the processes are defined on stone - every one must follow the same process irregardless of individual talent and skills. Agile on the other hand promote customization of the process in order to tap the best out of individual developer.

Agile also promote face to face teamwork interaction. In the old system, team communicate through documentation - that is why the documents have to be very detail and big, hence very hard to maintain in volatile environment.

Chaordic perspective.

The word chaordic is actually a combination of chaos and order.

Early part of an Agile projects are based on rigorous exploration of concepts and technologies. Even during the whole development cycle the concept of exploration is actually still going. In this type of development environment the normal standard concept such as CMMI wont stand a chance.

You can see from the previous characteristics (barely sufficient, and collaborative) how the chotic part is included into Agile characteristic.

The question is how do you manage such an environement and organization?

The answer is to employs adaptive management style- macromanagement (instead of micromanagement). The leaders have to leave large room for innovation and creativity in order to address keep changing environment. In the mean while still have the eye on the final goal and what is the current state of the project.

The organization can react very fast base on the current state of the project compare to the final goal.

Conclusion

There you have it - simple description on the three characteristics of an Agile ecosystem. As you see Agile ecosystem requires more to the project leader and the management team compare to the old just follow the book type of software development. So if you are selling the Agile idea, the first group that have to buy it is the management people.

This entry was posted on Friday, December 1st, 2006 at 6:49 am and is filed under Implementation, Industry, Planning, SEI CMM. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.