Write a clear weekly project update

A sponsor needs to know what changed, what evidence exists and which decision could block progress. “70% complete” rarely answers those questions.

Check an outcome-led update

The delivery lab creates a fictional week-two record.

from delivery_cases import weekly_update_case

result = weekly_update_case()
assert result["complete"] is True
assert result["percent_complete_used"] is False
assert result["update"]["status"] == "amber"
assert result["update"]["decisions_needed"] == ["confirm 24-hour approval SLA"]
assert result["fictional"] is True

Lead with delivered outcome and link evidence: test report, demo or decision. State next outcome, decisions with owner/date, risks with mitigation/owner, scope changes and overall status. Explain why amber/red and what restores green.

Keep technical detail proportional to audience and link deeper artifacts. Preserve prior updates so forecasts and decisions remain traceable. Never hide a failure behind activity lists.

The FDE for Freshers course uses weekly mentor check-ins as simulated client standups.

Exercise

Write a 150-word update for your capstone with one evidence link, one decision and one risk. Ask a peer what action they would take after reading it.

Continue learning

This article is part of the FDE career entry and client-delivery practice sequence. Use the neighbouring tasks when you need the prerequisite or the next application.

• Review the prerequisite or neighbouring task in Handle a client request that changes the scope.
• Continue with Record an architecture decision and its trade-offs.

Reference: Scrum Guide.