Manager manual
- 01Three roles, one board
- 02Day one: becoming the Manager
- 03First configuration
- 04The list of people
- 05Access and roles
- 06Change, close, hand on
- 07Projects and the queue
- 08Planning board
- 09Score and phases
- 10Thresholds, units, window
- 11Profiles, panels, reset, save
- 12Reports and closing the month
- 13Project budget
- 14Routine
- 15Someone leaves
- 16A project changes team
- 17An estimate changes
- 18The go-live moves
- 19A project is put on hold
- 20Someone moves to another team
- 21Reading the board
- 22What each section answers
- 23The reliability score
- 24Quick reference
Nothing in this manual matches.
Three roles, one board
Everyone signs in with their Microsoft work account (Microsoft Entra ID), inside Microsoft Teams. The role decides which screen you work in and what you can change.
Day one: becoming the Manager
The Manager role is named, then confirmed by the person named. From then on it belongs to that work account until it is handed on.
With a partner licence BI Development names the first Manager. With a subscription bought in the Microsoft commercial marketplace, the person who activates it is named.
A Team Lead seat covers one delivery team. A Guest seat is for a reader: a steering committee member, an executive.
Account, in the header of the Management board, shows the plan and its seats. There is no serial number or key to enter: the plan is checked each time the app opens.
First configuration
Do it in this order. Each step needs the one before it: a project needs its team and its manager in the list of people, an allocation needs both.
The list of people
One list for everyone who carries capacity or manages a project. Open the People tab of the Management board: kept by each Team Lead · the Manager moves people between teams. Access to the app is given on the Account page, not here.
Access and roles
Team Leads and Guests get access from you, on the Account page: Account at the top of the Management board, section Access. Each uses one seat of your plan.
Change, close, hand on
Access ends is not the Last day on the People tab: a contract's last day closes capacity, never access.
Projects and the queue
You give each project its identity and its place in the queue. The delivery team fills in everything else. Open the Projects tab of the Management board.
A project not ready for a team yet: prepare it on the Planning board.
The execution order: one queue across all delivery teams; 1 is worked first. Delivered projects leave the queue.
Planning board
Projects you prepare before giving them to a team: only a code and a name. Open the Planning tab of the Management board. Only you see them: not on the board, in the Team Lead Workspace or in the export.
Parameters: score and phases
Open the Parameters tab. Changes are kept only when you select Save; a value that breaks a rule is refused.
Weights must total 100%. Bands: green from 100%, amber from 90%, red below; green must stay above amber. Line to clear on the dial: 90%.
Statuses outside the scale: by default Not Started and Canceled are left out of the phase check.
Parameters: thresholds, units, window
Each threshold is a management decision, not a calculation. The board applies it everywhere the figure appears.
Profiles, panels, reset and save
A display profile changes what the board shows, never how it counts. Keep one for the steering committee, one for the weekly review.
Settings that change the numbers stay common, so reports remain comparable over time.
Board panels, in Parameters: untick a panel to hide it, and choose the columns of the project register. The reliability score and the register's Order, ID, Project and Status are always shown, so missing data and delays stay visible.
Client logo, in Parameters: a PNG, JPEG or WebP file up to 150 KB. Kept at once; Remove, asked twice, takes it out. It shows on the board, under Portfolio Control Center, for everyone who reads it.
Save refuses a value that breaks a rule, and says which: weights not totalling 100%, green not above amber, phase percentages that do not increase, duplicate phase codes.
Reports and closing the month
A report you publish and the photo of each closed month keep the board as it was. Neither changes afterwards.
Project budget, month by month
Only the projects’ costs: the invoices the Team Leads book, against each project’s approved budget. Licences, subscriptions and the overall budget stay outside.
In Parameters, Annual budget panel sets how many years before and after the reporting year the board opens.
Board › 03 Budget › Per month. The approved budget spread evenly from start to go-live: 100k over five months, 20k a month. Red: a month above its baseline. Under the name, the balance: “Invoiced €92,000 of €100,000 · €8,000 left”.
Export project costs next to Publish report downloads Project costs - <date>.csv: one row per invoice, every project and year. Columns: Project code, Project, Location, Team, Month, Invoice date, Invoice, Supplier, Description, Amount. The separators are the ones set for the effort import. The same section sets the absence code (default ABSENCE): hours booked with it lower the month’s capacity and count as reported, never as BAU or project work.
The Manager's routine
Once set up, the Manager's work is short and regular. The board tells you where to look.
Someone leaves in the middle of a project
The last day closes the person’s capacity. What they were still planned for after it is nobody’s work until the Team Lead gives it to someone else. Until then, the board shows the gap.
A project taken over from another team
The Manager moves the project; its history stays where it was booked and keeps counting. The team that runs it now starts from what the other team kept, and the team that ran it decides what it still plans on it.
The estimate changes along the way
A change request raises the effort estimate or the approved budget of a running project. The board does not rewrite the past: what was expected before the change stays, and what the new figure leaves is spread over the time left.
The go-live moves
The project needs more time, or less. The new date takes over from the month you save it; the moves stay on the board, so a slip is never hidden by the new date.
A project is put on hold
The project stops for a while and will resume. The board stops expecting effort and money from the month you save it, and spreads what is left when it resumes.
Someone moves to another team
The person stays in the company and keeps one row. Each team keeps the days the person was in it, and a day both teams report counts once.
Reading the board
The board opens on the latest report. Everything at the top of the page is a way in; nothing you click changes the data. Beside each chart, ? shows how it is worked out, step by step, and the speaker reads it out; presenting in a Teams meeting, share with Include sound so the others hear it. Under the title, your organisation's logo, if the Manager has set one.
What each section answers
The reliability score, worked
The score says how far the data under the board can be trusted. It is about the data, not about how well the projects are going.
83% is below the amber band (90% by default), so the dial is red. The biggest loss is the weekly effort: one person in six has not reported.