Project planning and management
The ability to break a project into stages, estimate resources and risks, build dependencies and deliver on time, budget and quality while managing change.
Definition
BT360 v2.0.0The ability to break a project into stages, estimate resources and risks, build dependencies and deliver on time, budget and quality while managing change.
What is it made up of?
3 INDICATORS- 01Project structure and a realistic plan
- 02Managing deadlines, resources and dependencies
- 03Managing change and risks
Behavior levels 0–5
MANAGER'S GOAL - 4| Lv. | Label | Descriptor |
|---|---|---|
| 0 | Absent | The project is unstructured; timelines and resources are not estimated; dependencies are invisible; changes are chaotic; the result is unpredictable. |
| 1 | Poorly developed | Makes a task list; estimates optimistically; ignores dependencies; the plan collapses when something changes; status is not transparent. |
| 2 | Underdeveloped | Builds a plan from a template; accounts for the main dependencies; handles changes with delay; records risks but does not manage them; the result often slips. |
| 3 | Normally developed | Structures the project, estimates resources and dependencies; maintains the plan and status; manages changes and key risks; delivers within the agreed scope. |
| 4 | Highly developed leader's goal | Runs complex projects with high uncertainty; manages a portfolio of dependencies; makes decisions on timeline and scope; keeps the team and stakeholders aligned; the result holds. |
| 5 | Overdeveloped | The project turns into a cult of the plan: endless approvals, detailed schedules, resistance to change; time goes into managing the plan rather than the result; flexibility is lost. |
How is it measured?
coating BSJT - BT360 situational test: provides a hypothesis about judgments in work situations and does not replace observation, 360 and interviews.
There is no direct test of project management; TMBS shows the organization of time, LPI shows practice. The level is confirmed by the project history and plan audit.
Development Actions
5 CATEGORIESTMBS and LPI; an audit of one project: structure, estimates, dependencies, risks, deviations.
Project Management course (2–3 days): frameworks, breakdown, estimates, dependencies, risks, changes.
Run one project using a single template: goal — stages — resources — risks — status — retro.
Review with an experienced PM: where the estimate was unrealistic and why.
Introduce a single project template in the team and a weekly status with escalation triggers.