Every project plan contains assumptions, or it should. We never know everything we need to know at the start of a project, and so we have to make a guess. These guesses we call assumptions. Different projects require different assumptions, as do different customers. The difference between assumptions and risks is not at all clear in the context of a project plan, since we can mitigate a risk by making an assumption. For instance, we might regard as a risk the possibility that our senior solution architect may get killed by a passing truck, so we mitigate this by making the assumption that it won't happen. If you prefer to use a risk register, then this section is still relevant.

Here are some assumptions ...

Get Designing a Data Warehouse: Supporting Customer Relationship Management now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.