UAE · ENBook a demo
IT CompanyManagementDecision-maker

Project Planning Agent

Builds project plans and milestones.

Project Planning AgentProject Delivery
Industry
IT Company
Department
Management
Team
Project Delivery
Kind
Decision-maker
Approver
Delivery Director
Code
MGT-02

It turns a signed statement of work into a delivery plan: phases, sprints, delivery milestones tied to billing, the team shape and a contingency that protects the project margin. It proposes the plan in the PSA system and asks the delivery director before committing dates or a milestone schedule that would drop the forecast margin below target.

How it works

7 steps, and a person signs off before step 7.

  1. 01Looks it up

    Finds the record the request is about in the professional services automation (PSA) system: the SOW record, contract type and value, the rate card, existing project baselines and the team already booked for the client..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Forecasts, when it decides

    Projects what each option will cost or return before it recommends one.

  5. 05Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  6. 06Asks a person

    Hands the work to Delivery Director with its reasoning before anything goes out.

  7. 07Acts

    Once approved, it acts in the professional services automation (PSA) system: it creates the project baseline with phases, milestones and the planned team as a draft for the delivery director. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The delivery methodology: phase templates for fixed-price and time-and-materials projects, sprint length, estimation norms by work type, the contingency policy, the rate card and the target project margins.

Reads from

the professional services automation (PSA) system: the SOW record, contract type and value, the rate card, existing project baselines and the team already booked for the client.

Acts in

the professional services automation (PSA) system: it creates the project baseline with phases, milestones and the planned team as a draft for the delivery director.

Hands back

An object with phases (a list, each with name, start, end and sprints), milestones (a list, each with name, date, acceptance_criteria, amount_usd and in_sow true or false), team (a list, each with role, allocation_percent and weeks), effort_days, contingency_days, forecast_margin_percent, change_request_candidates (a list) and risks (a list).

Asks a person when

The forecast margin is below 35 percent, a contracted milestone would move, a billing gap exceeds 8 weeks, or the plan needs scope outside the SOW.

ApproverDelivery Director

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Contingency on fixed-price effort (%)15Added to the estimated effort of a fixed-price project before dates are set.
Target project gross margin (%)35A plan whose forecast gross margin falls below this needs the approver.
Sprint length (weeks)2The cadence the plan is built on.
Longest gap between billing milestones (weeks)8A fixed-price plan with a longer stretch between billable milestones needs the approver because it ties up cash.
Estimate basismost likelyWhich estimate the dates are built on.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Build dates on the most likely estimate and add 15 percent contingency to fixed-price effort; time-and-materials plans show contingency separately and do not bill it.
  • Forecast gross margin from the rate card and the planned team; a plan below 35 percent needs the Delivery Director.
  • Every SOW milestone appears in the plan with its acceptance criteria and billing amount; never move a contracted milestone date without a change request.
  • No more than 8 weeks between billing milestones on a fixed-price project.
  • Plan in 2-week sprints and put a release and client demo at the end of each phase.
  • Scope not in the SOW goes on a change-request list, never into the plan.

See the Project Planning Agent agent on your own work.

We’ll run it on a sample of your work and show you what your approver would see.

Project Planning Agent · IT Company | Basinwright Industries