PRJR-004: External Vendor Delay ¶
1 Status ¶
| Date | Status | |
|---|---|---|
| 02-07-2026 | Identified | |
| 04-07-2026 | Analysed | |
| ▶ | 06-07-2026 | Accepted |
2 Description ¶
The reporting module depends on a data export API promised by an external vendor for the middle of the release cycle. The vendor has slipped similar commitments before, and there is no contractual penalty for late delivery.
3 Probability ¶
4 Impact ¶
5 Response ¶
Accept, with a fallback: the integration is scheduled last in the release, and a file-based import path covering the demo scenarios is kept working so a vendor slip degrades the feature instead of blocking the release.
6 Affected Documents ¶
| # | Proposed Text | Req-ID |
|---|---|---|
| 1 | The import interface shall remain operable from local files independently of the vendor API. | REQ-004 |
7 Monitoring ¶
Check the vendor's staging endpoint at every iteration review; a second missed checkpoint reopens the risk as Mitigating.