A city agreed at kickoff on a report template with executive summary, findings, remediations, and appendices. What should the tester do at delivery time?
Select an answer to reveal the explanation.
Short Explanation
If you promised a standard menu—summary, findings, fixes, appendices—serve that meal. Clients navigate faster when the map matches kickoff.
Full Explanation
When a city agreed at kickoff on a report template with executive summary, findings, remediations, and appendices, delivery should follow that agreed section structure so stakeholders can consume the report as expected. Changing format unilaterally creates confusion and missed sections.
Inventing a novel free-form essay to showcase writing style breaks the contract of expectations. Delivering only chat logs is not a structured assessment report. Omitting remediations because structure was 'only a suggestion' undercuts the kickoff agreement.
Exam caveat: minor clarifications are fine; structural surprises are not without client approval.
Operational check: map content into the kickoff template before writing polish, run a completeness checklist against agreed sections, and deliver the city package in the expected order. In municipal operations, record the rationale in the engagement notes so future assessors know which control was chosen and which failure modes the rejected options would create for city services. Re-validate after the next maintenance window that the same finding class still applies under the estate's current patch and configuration baseline. In municipal operations, record the rationale in the engagement notes so future assessors know which control was chosen and which failure modes the rejected options would create for city services.