1. Purpose and scope
Most of what an assessor needs to see for level two is created or decided in the first weeks of a project. Plans with a basis for their estimates, a risk register with treatments, a quality assurance plan with an escalation path outside the project, configuration items and baseline points, and change and problem workflows: if these exist from the start, the project generates evidence as it works. If they are created later to prepare for an assessment, the history they should show is missing, and baselines that were never taken cannot be recreated.
The project begins by tailoring the standard process within the guideline, so it is clear which work products it owes. It then builds a plan where each item links to the work product it produces, records risks with owners and treatments, agrees with quality assurance how process and work products will be checked, and sets up configuration management with naming, branching, baseline and release rules. Where suppliers contribute, the supplier agreement states what process evidence and work products each must provide and how they will be reviewed.
In scope: the tailored project process, the project plan, the risk register, the quality assurance plan, the configuration management plan, the change request and problem report logs, the verification strategy draft and supplier agreements. Out of scope: the engineering work itself, which starts in Stakeholder, System, Software & Hardware Requirements.
14 more sections for registered members.