---
title: Measure and report performance
acode: E1
---

This is the first management activity in the *Weekly Closure* group. 

We rarely progress as planned, which is fine as long as we check to see what each deviation means to the project and what we have to do about it. 

2:: Are we getting closer to achieving the project goal?
3:: What's our guess about the way the rest of the project output will be created?
4:: What's our guess about the user aspects in the future?
4:: Are we satisfying the project requirements?
1:: What's our forecast for the completion of the project?

There's no simple, universal way of forecasting, and the person wearing the *Project Manager* hat should ensure that an appropriate method is used: one that is good enough for replanning or changing the targets in [C1](../../c/1/). New forecasts should be added to the "targets and forecasts" meta-card in the "project description" column of the *Integrated Project Board*.

1:: Does anyone outside the team need to be aware of our progress?

If necessary, you should communicate the project performance with people outside the team, such as the customer and higher organizational levels. The reports should be kept simple and straightforward, and reviewed to decide whether it's a good idea to send them every cycle, every two cycles, or in any other frequency.

