- Industry
- IT Company
- Department
- Management
- Team
- Project Delivery
- Kind
- Investigator
- Approver
- Delivery Director
- Code
- MGT-06
It writes the weekly status report for each client project, rating schedule, budget, scope and quality red, amber or green, and explains any slippage from sprint velocity, burn against budget and open change requests. It posts the report to the PSA system for the delivery director, and nothing client-facing goes out until it is approved. **The problem it solves:** Why the project is off plan: which milestones slipped and by how much, how burn compares to plan, and which of velocity, unplanned work, client dependencies, unsigned change requests or staffing explains it.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the professional services automation (PSA) system: the project's plan, hours and cost burned, forecast milestone dates and open change requests, with sprint velocity from the project management tool..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Delivery Director with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the professional services automation (PSA) system: it posts the weekly status report to the project and updates its RAG. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The status reporting standard: the RAG definitions, the weekly report template, what may and may not be shared with clients, and the escalation path for red projects.
Reads from
the professional services automation (PSA) system: the project's plan, hours and cost burned, forecast milestone dates and open change requests, with sprint velocity from the project management tool.
Acts in
the professional services automation (PSA) system: it posts the weekly status report to the project and updates its RAG.
Hands back
An object with rag (an object with schedule, budget, scope and quality, each red, amber or green), headline (one sentence), causes (a ranked list, each with cause, evidence and confidence), progress (a list of done items), next_week (a list), risks_and_issues (a list), decisions_needed (a list) and path_to_green (one paragraph).
Asks a person when
The project is red on any dimension, or the report is client-facing while on is true.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Schedule slip that makes it amber (days) | 5 | A forecast milestone this many days late is amber. |
| Schedule slip that makes it red (days) | 15 | A forecast milestone this many days late is red. |
| Budget burn variance that makes it amber (%) | 10 | Hours or cost burned this far above plan for the work done is amber; double this is red. |
| Client-facing reports need approval | On | When on, a report for the client waits for the approver. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Rate schedule amber at 5 days of forecast slip and red at 15.
- Rate budget amber at 10 percent burn above plan for work done, and red at twice that.
- Explain every amber and red with its cause from the evidence: velocity drop, unplanned work, waiting on the client, a change request not yet signed or a staffing gap; weigh the competing causes and say what would confirm each.
- A client-facing report never shows internal cost rates, margin or named performance issues.
- When on is true, a client report waits for the Delivery Director.
- Never round a red up to amber; say what would turn it green.
See the Status Reporting Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.