In this episode, Ricardo starts speaking if the assumptions and constraints should be documented in the Scope Statement or the Project Charter. Then, he reflects about the real relevance of knowing in what “piece of paper” this information will be inserted and reinforce that relevant information is what drives the project to success. Ricardo used in this podcast the word Restriction as a synonym of Constraints (a PMBOK® term).
7 pages were found with this tag.
In this episode, Ricardo explains when it's a good idea to split a project into phases/stages. He also pointed out that nothing prevents us from using different methodologies to manage each of these stages, if that contributes to project success, of course.
In this podcast, Ricardo explains that, unlike what many people think, the assumptions and restrictions (or constraints) often need to be registered not only in one but in several documents throughout the progression of the project planning.
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, Ricardo talks about the project objectives and in which document it should be written. He explains that the Project Charter is the document where the project is born and the Scope Statement is a response to the Project Charter and is where the work being done is more detailed.
In this videocast Ricardo talks about the differences between assumptions and constraints in project environment.
In this presentation, Ricardo explains in detail the Project charter and the Scope Statement and shows the differences between these documents.