Summary: See your projects, or one project, and your people's workload as a scenario without the buffers, and compare it with the plan, without changing anything.
Applies to
| Property | Value |
|---|---|
| Product | LYNX-X |
| Version | 28.10.9877.0 |
| Required permissions | Access to Portfolio > Project list |
| Last updated | 2026-11-13 |
| Owner | Support |
Before you start
- Close the projects you have open. A project that is already open when you switch does not show the change properly.
What Debuffered shows
Debuffered is a calculated scenario of your portfolio. It takes the buffers out of your projects and spreads their time back over the tasks. Tasks take longer, the forecast moves later, and your people carry more work.
For example, with durations shortened by 50 % and buffers of 50 %, a task estimated at 10 days is planned at 5 days. In Debuffered it takes 7,5 days: its 5 days plus its share of the buffer.
Tasks with Fixed duration ticked, for work that takes a set time such as procurement, are the exception. They are never shortened, and Debuffered leaves them as they are.
Use it to answer two questions:
- When would the project finish? The project's statistics show both forecasts.
- Can my people carry the work? Resource load shows how much more work each skill gets.
Nothing is saved, and only your own view changes.
Procedure
Switching the portfolio to Debuffered
- Go to Portfolio > Project list.
- In the left rail, select Debuffered.
If the rail shows icons without names, select the menu button at the top of the rail to show them.
A green Scenario: Debuffered banner appears at the top. The Performance column shows no buffer bars, and the projects' dates in the list stay the same.
Seeing your people's workload
- With Debuffered on, select Res. load in the left rail.
- Compare Total work and each skill's Unallocated with the normal view.
Here the same three projects need 5551,5h instead of 4041h. Designer goes from 51h unallocated to -/-33h: more work than the skill can take. While Debuffered is on, Resource load shows the whole portfolio: the single-project selection is greyed.
For how to read the graph, see Reading multi-project resource load.
Seeing a project debuffered
- With Debuffered on, select the project's ID in the list, then select Open project.
The project opens with the same green banner. The tasks show longer durations in Prj. duration, and Schedule in the left rail is greyed.
A task with Fixed duration keeps its duration. Here Sourcing Materials stays at 7 days.
- Select Project at the top right, then the Statistics tab.
Below Scheduled finish, Expected finish, Current chain length, Resource hours and Remaining, a debuffered row gives the scenario's value.
For what each line means, see Reading project statistics.
Switching back
- Close the projects you opened.
- In Portfolio > Project list, select Debuffered again.
The banner disappears and the buffer bars come back.
Debuffering one project
To see a single project without its buffers, leave the portfolio as it is and debuffer the project from inside it. Debuffered must be off in the Project list: while it is on, Schedule is greyed in the project.
- Open the project.
- In the left rail, select Schedule, then Reschedule project, debuffered.
The tasks that have not started take their debuffered durations, as in the portfolio scenario. Started tasks and Fixed duration tasks keep theirs. Save stays grey: nothing is stored.
- Select Project at the top right, then the Statistics tab.
The debuffered rows give the scenario's forecast for this project.
There is no green banner for one project. Instead, Schedule in the left rail is shown highlighted: a scheduling option other than the standard one is on for this project. The longer durations and the debuffered forecast show the scenario.
To go back to the plan, close the project and open it again. It opens with its normal durations.
If you change a task while the project is debuffered and save, your change is saved and the project goes back to its normal plan. The debuffered durations are not stored. As with the portfolio, the scenario is only in your own view, for your analysis.
Additional information
How much longer the tasks get depends on how your projects shorten durations and size their buffers. Many teams shorten durations by 33 % and add buffers of 50 %, so that a project keeps its original length. With those settings, Debuffered shows the tasks at about their original durations. Fixed duration tasks were never shortened, so they show their own duration in both.
Note
Expected buffer consumption (%), on the Critical chain tab of the project's Properties, is usually left at 100 %. If it is set lower, each task gets back only that share of its buffer time: at 50 %, the 5-day task in the example takes about 6,3 days instead of 7,5.
Expected outcome
With Debuffered on, the portfolio, Resource load and the projects you open show the scenario, under a green Scenario: Debuffered banner. Switched off, everything is as before. A project you debuffer on its own shows the scenario until you close it or save. Debuffered itself never changes your projects.
Troubleshooting
| Problem | Resolution |
|---|---|
| A project shows its normal durations, or only some tasks changed. | The project was open when you switched. Close it and open it again. |
| The buffer bars are missing from the Project list. | Debuffered is on: the green banner says so. Select Debuffered again to switch it off. |
| Schedule is greyed in a project. | Debuffered is on. Switch it off, then close and reopen the project. |
| A task keeps the same duration in the scenario as in the plan. | If it has not started, check Fixed duration on the task's General tab. Fixed duration tasks are not debuffered. |
| A project stays debuffered after Reschedule project (F9). | Close the project and open it again. |
See also
Revision history
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | 2026-10-13 | Support | New article. |
| 1.1 | 2026-11-13 | Support | Added Fixed duration tasks, debuffering one project, saving a debuffered project, and Expected buffer consumption. |
Comments
0 comments
Please sign in to leave a comment.