Blog · Custom Engineering Notes
Managing Requirement Changes
Change is normal. Unmanaged change is what turns a fixed-price project into a dispute.
Overview
- One change log, one approver, one version of the scope — anything less and the baseline disappears.
- Assess every change for its effect on schedule, cost and risk before accepting it.
- Batch small changes where possible; each individually-assessed change has its own overhead.
- Record rejected changes too — the reason is often the most useful document in the project.
Related pages
- Scenario CustomizationView
- Platform and Payload CustomizationView
- Production StrengthView
- Intelligent Payloads and AccessoriesView
More in this area
- Writing a Customization Requirements DocumentRead
- Prototype vs Production ConfigurationRead
- Common Interface Issues in Integration ProjectsRead
- Why Payload Power Budget MattersRead
- Why Acceptance Criteria Come FirstRead
- Managing Requirement ChangesThis page
- Preparing for Field TestingRead
- Managing Hardware and Software VersionsRead
- What Makes Up a Custom Project CostRead
- Planning from Pilot to Volume DeliveryRead