This article aims to discuss the costs and benefits of speed in developing a project plan and proposes a basic process that consists of 10 steps to plan and 10 steps to track a project in a short time. The process aims to simplify and prioritize critical documents to be developed in order to ensure the purpose, scope, deadlines and budgets, as well as direct restrictions of the project to be developed.
This article aims to discuss the costs and benefits of speed in developing a project plan and proposes a basic process that consists of 10 steps to plan and 10 steps to track a project in a short time. The process aims to simplify and prioritize critical documents to be developed in order to ensure the purpose, scope, deadlines and budgets, as well as direct restrictions of the project to be developed.
El artículo tiene por objetivo discutir los costos y beneficios de la velocidad en el desarrollo de un plan de proyecto y propone un proceso básico compuesto de 10 etapas para planear y 10 etapas para acompañar/controlar un proyecto en un corto espacio de tiempo. El proceso propone la priorización y simplificación de los documentos críticos a ser desarrollados de modo que aseguren el propósito, el alcance, los plazos y presupuestos, bien como las restricciones directas del proyecto a ser desarrollado.
In this podcast, Ricardo talks about the key information that must be produced by the project manager when receives a very urgent project and need understand the purpose, scope, budget, schedule and constraints of the project in a very short period. He explains that making a quick planning and not very detailed is not ideal and can not be a normal situation in the company.