FAQs:

What is the use for paused and aborted statuses for a project?

In Lynx, managing the lifecycle of projects, including pausing or aborting them, is a critical aspect of maintaining project portfolio health and alignment with business objectives.

Pausing: Projects may need to be paused due to various reasons such as resource reallocation, prioritization changes, or external dependencies. To pause a project, you would change its status to 'Paused.' This indicates that the project is temporarily on hold but intended to resume in the future. During this period, the project's tasks are not active, helping to reallocate focus and resources to other priorities.

Aborting: If a project is no longer viable or aligned with strategic goals, it may be aborted. Changing a project's status to 'Aborted' signifies that the project has been terminated and will not continue. This action helps in clearing the project pipeline and focusing on projects that contribute to strategic goals.

When changing a project's status, it's important to communicate with stakeholders and team members about the decision and its implications. Documentation and analysis of the reasons for pausing or aborting projects can provide valuable insights for future project planning and execution.

How does the project status being changed to paused or aborted impact the planning?

What is the use for paused task status and how does it impact the planning?

When the task cannot be worked on currently, but will be continued at a later date, you can set the status of the task to paused. This will communicate between the team members and the project managers that the task is on hold and is not being worked on. It is recommended to have a rule (as a procedure) to enter a "Note" for the task explaining the reason for the status change.

The behavior of paused tasks is:

• The task is still counted for the calculation of the Current Longest Chain. The resource load and the remaining duration will also remain the same and are not impacted.
• The paused task will appear and remain at the top of the task list (My activities).
• If it is required, you can change the ETTC of the task.

What is the use for aborted task status and how does it impact the planning?

When the task will no longer ever be worked on, you can set the status of the task to aborted. This will communicate between the team members and the project managers that the task is not relevant anymore and working on it has been stopped without the intention to start the task again. It is recommended to have a rule (as a procedure) to enter a "Note" for the task explaining the reason for the status change.

The behavior of paused tasks is:

• The task is no longer counts for the calculation of the Current Longest Chain. The resource load and the remaining duration will no longer include the task and its resources.
• The progress of the project will be reported similar to a completed task
• The aborted task will no longer appear on the task list (My activities) and its predecessor tasks will have a "Ready to Start" flag.
• The task with status "Aborted" will have similar behavior as "Completed" tasks except for in case of when the task would be followed by dependency with a lag.