Reuse Environment

Reuse Environment

Reuse Environment - An environment and culture that promotes reuse can offer tremendous value to your company.

Most developers think of reuse in terms of code reuse. In fact, that is usually the logical place to start.

The major benefit to reusing code is that applications will be faster and less expensive to build

There should be no question that applications can be assembled from reusable objects faster than they can be built from scratch, so faster development time is a major benefit.

The second major benefit is improved quality

This results from the use of pre-tested objects. Reusable objects are more stable, deliver more predictable results, and are less prone to errors in production. Faster development time and higher quality from the start should also result in less expensive solutions.

This is true on a project-by-project basis. For instance, each project will use less development time and money and there is less testing required because you are using components that have been tested already.

However, there are increased costs for the entire organization because of the new processes and tools required to support the reuse environment.

In fact, it is these overall environmental costs that typically spell doom for most reuse efforts. To really be successful in creating a reuse environment, you need to establish some rules on sharing, have a place to store the reusable components, have processes to help people find and use the components, etc.

You will also find that components that are built for reuse take more time and effort to create, so although there is increasing value with each reuse, the original development time may, in fact, be longer and more costly.

One overall point to remember is that there are two basic aspects of the reuse culture

  • First, in almost every activity you do, you first think about whether there may be something already available that you can use. If you cannot use it entirely, can you at least use it as a starting point?

  • Secondly, for every piece of work that you create from scratch (there will still be a lot), always ask yourself whether this work is something that someone else may be able to reuse later.

    Of course, if you ask those questions today, they won’t do nearly as much good because you do not have an infrastructure in place to handle the reusable components.

    However, that is the whole purpose of putting the environment in place.

Risk


Libro El Director de Proyectos Práctico -

Un Método probado de 28 Pasos para completar tu Proyecto Exitosamente

EL DIRECTOR DE PROYECTOS PRACTICO -

Por fin ─ un libro sencillo con un método paso a paso para completar tu proyecto.

¡Y sin tener conocimiento previo sobre administración de proyectos!

Toda la "paja" de la metodología de dirección de proyectos fue eliminada, dejando solo lo que es absolutamente útil para completar la tarea.

El Director de Proyectos Práctico, Project Management for Small Projects. 

Un libro pensado en el líder de proyectos empírico que salió ganador de la rifa del tigre. Pues ya tiene la responsabilidad de un proyecto, pero que no sabe ni por donde empezar. Necesita una receta ABC para seguir.

Contiene 260 páginas perfectamente detalladas con ejemplos e ilustraciones, que te llevan de la mano hasta completar tu proyecto.

Pruébalo, síguelo, ten éxito. O sigue haciendo lo mismo... :(

Disponible en Amazon

Compra aquí El Director de Proyectos Práctico en su versión electrónica─

Entrega inmediata.

BONO ADICIONAL:  El libro incluye todos los templates─plantillas─que necesitas, listos para ser usadas. No necesitas comprar nada mas.


COPYRIGHT © 2007-2012 por Hector Olvera Padilla 1853071. Reproduction in whole or in part, or translation without written permission is prohibited. "PMP®", "PMBOK®", and "PMI®" are registered marks of the Project Management Institute, Inc.