Assignment
Plan a simulated support pilot with dependencies on identity access, document data, and an API sandbox. Add a late request for a consequential write action.
Build sequence
- Create deliverables with owners, dependencies, and evidence of completion.
- Identify the critical path and work that can proceed with fixtures.
- Write options for the late request, including deferral and a limited reviewed version.
- Separate reusable adapters from customer configuration and assign maintenance ownership.
Acceptance checks
- The plan exposes external blockers instead of hiding them in coding estimates.
- The change assessment identifies new permission and testing requirements.
- The handoff includes clear ownership of every custom component.
Evidence to keep
Submit the working artifact or decision document described above, the inputs used, and the observed results for every acceptance check. Include one failed attempt and the change you made after investigating it. Label fixture-based outcomes separately from live-system measurements. These artifacts become part of your final portfolio review.