Assumptions and Constraints

In this week's episode, Ricardo talks about the exponential growth of problems in the project. He explains with several examples what exponential growth is, such as the behaviour of social networks when a post is shared with ten people and that each one will share with another ten people. So on, the number of views has a massive growth. We often rely on intuition to make a future prediction, imagining linearity.

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).

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 why we should separate Assumptions from Constraints in the project management and do not consider them as similar. You'll learn why the approach strategies should be distinct.

In this podcast Ricardo talks about the importance of project change management. He assert that the relevant is not to avoid the change, but manage it in a proper and assertive way, aiming the global benefit for the project.