While creating the WBS, the customer states they require a proof of concept and will continue the project only if it succeeds. A key team member insists the team should plan the entire project because the customer usually continues. What should the project manager do?

The project charter defines the project's high-level scope and objectives, including any phases or conditions for continuation. The customer's requirement for a proof of concept and conditional continuation directly impacts the project's scope and planning. The project manager must refer to the charter to understand the agreed-upon project boundaries and communicate them to the team. Telling the team member to continue with current tasks ignores a critical scope constraint. Applying the 100% rule is a WBS best practice, but it doesn't address the fundamental issue of conditional project continuation. Building a WBS for the full project without addressing the customer's condition could lead to wasted effort if the proof of concept fails.