Back to overview

Status

What puts this sprint's goal at risk?

If you plan in sprints, you do not need the calendar week but the sprint as the time frame. Merlin Project does not know the sprint as an object of its own, so the prompt has to say how to recognise it: cleanest is one task group per sprint, whose name you put in for {SPRINT}, because the group carries start, end, and progress. Without groups, name the date range directly. The last sentence is the difference from the weekly version: in a classic plan the point is to hold the end date, in a sprint it is to cut the scope. If your team works with the Kanban board, the addition "Name the column each task sits in" pays off.

Create the briefing for the current sprint instead of the calendar week. The sprint is the task group {SPRINT}, and the status date of the project applies. Name at most five tasks that put the sprint goal at risk, sorted by their effect on the end of the sprint. For each task: why it is at risk (critical path, missing slack, overloaded resource, late predecessor), the responsible resource, one concrete recommendation for today. At the end, name what has to drop out of the sprint if nothing is added.

Explained in the video

Further reading

Run projects that actually ship.

One app for your project plan, native on every Apple device.