Knowledge Application and Reuse in Project Delivery
This domain tests reuse in delivery: pulling knowledge at the right decision point and adapting it to context. Reuse is not copying; it is assessing applicability, adjusting assumptions, and recording the outcome.
Rules
- Reuse at planning (estimates, risk registers, schedules), execution (checklists, design patterns), and closure (lessons, benefits).
- Assess context: scope, scale, technology, team maturity, constraints, regulatory setting.
- Prefer validated, owned knowledge with provenance over anonymous templates.
- Use analogies and parametric models with adjustment factors; document deviations.
- Close the loop: record what was reused, what changed, and whether it worked.
- Counter not-invented-here by pairing reuse with local validation and credit.
Worked example
A team reuses a prior estimate of 1,200 hours for a similar module. The new module is 20% larger and uses an unfamiliar platform. Adjust scope (+20%) and add a 15% learning and risk allowance; validate with a bottom-up check. Reasoning: reuse provides a baseline, but context changes must be explicit. Blind copy-paste would understate uncertainty.
Traps
- Copy-paste templates without assumptions.
- Reusing a lesson outside its validity context.
- No feedback on reuse outcomes.
- Rejecting external knowledge due to source bias.
- Treating reuse as a one-time search.