Sprint 4 · Quality Metrics

Quality metrics

Targets for what the cameras cover, how close the counts are, how fresh the data is, and what the team does when a target is missed.

Targets and response

The plan is dated October 5, 2026. The Technical Lead measures the lot targets. The Project Manager measures spend at the end of each sprint.

  • Coverage. 90% of stalls in camera view, checked for each garage and lot. If a lot falls below 90%, pause new lots and fix camera angles first.
  • Accuracy. At least 90% of spots match a manual count, checked weekly. A miss gets a last-updated or stale-data warning, and expansion waits until it is fixed.
  • Freshness. The newest update for a lot stays under 2 minutes for 95% of the day, checked daily. The same stale-data warning applies.
  • Spend. Stay inside the $33,780 baseline, with no management reserve. Lot onboarding is not in the 538-hour estimate yet. The build-services allowance in the plan is $500.

Issue severity

  1. Severity 1. A filter, label, or layout glitch that does not block finding parking. Fix in the next sprint. Tell the instructor at sprint review.
  2. Severity 2. One lot's camera is down or stale, or the manager dashboard fails. Start within 1 business day. Include it in the next weekly update.
  3. Severity 3. The map or list is down, or availability is wrong for every lot. Start within the hour. Tell the instructor as soon as possible.

Document Quality Metrics

Damn Parking · Quality Metrics and Issue Management Plan

Sprint: 4 · Team: 1 · Date: October 5, 2026 · Purpose: Coverage, accuracy, freshness, spend, response policy, and issue severity.

Download PDF