Planning

In this podcast, Ricardo talks about the Work Breakdown Structure (WBS) Dictionary. He explains that this document may be called the work packages instruction manual and gives tips on how to plan well your dictionary.

In this podcast, Ricardo concludes the series on megaprojects, talking about communication, teams and some success factors. He comments especially the importance of forming the core team of the project as soon as possible and to be careful on planning the outsourcing of some roles.

In this podcast, Ricardo continues the series of three podcasts about the world of megaprojects. In this episode, he talks more about the concept of FEL (Front End Loading) and its great importance. In the next and final episode, Ricardo talk about teams, communications and how to engage the community in megaprojects.

In this podcast, Ricardo addresses the factors that matter when you're controlling a project. He describes the top 3 factors that every Project Manager should address to effectively control the project.

In this podcast, Ricardo explains that an Analysis of Feasibility of a Project should be seen as a project by itself, with all the characteristics of a project, having a Project Charter, a schedule, a WBS etc. The analysis may demonstrate that the project under study is not feasible, but that does not mean that the feasibility study was a failure. Understand the reason.

In this podcast, listen Ricardo's opinion on the level of detail of the project scope. How much detail we have to pursue? What is a good size for a work package?

In this podcast, Ricardo talks about the challenges of resource allocation and explains a technique based on the allocation of generic skills (or positions) needed for the project.

In this podcast, Ricardo explains that the project manager should seek to simplify the way he/she leads the projects. In the quest for perfection, many people often create methodologies which are too complex to be used and end up not being used at all. He mentions a methodology he once created, pinpointing ways that enable the simplification of the procedures necessary to manage projects.

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.