In Adobe Workfront, when a project ' s progress status is marked as Behind or At Risk , the project condition is set to At Risk . This indicates that the project may not meet its deadline or performance metrics, signaling to the project team and stakeholders that corrective action may be necessary. The " In Trouble " status is reserved for more severe cases, and " Late " is generally used for tasks or projects that have passed their planned completion dates without being finished.

The At Risk status allows proactive intervention to address potential issues before they escalate into bigger problems​​.

In Adobe Workfront, Scrum supports this hybrid approach because teams can keep structured project planning in Workfront while managing selected tasks as agile stories within iterations, commonly called sprints. Adobe documentation explains that Scrum teams use a backlog and then plan an iteration by selecting tasks or issues from that backlog. Adobe also notes that many organizations use the words sprint and iteration interchangeably, and that iteration planning occurs after the backlog has been groomed and prioritized. This allows planned project tasks to remain part of a Workfront project while the team manages execution through sprint-based agile practices. Waterfall is structured and sequential, but it does not provide sprint-based task management. Kanban provides flexible visual flow through a board, but it is not centered on fixed sprint or iteration planning. Therefore, the Workfront methodology that combines structured planning with sprint flexibility is A. Scrum .

=========

In Adobe Workfront, a request is managed as an issue, and the team that should work on the request is set in the request or issue Assignments area. Adobe documentation explains that issues can be assigned to users, job roles, or teams, and the Assignments field supports assigning users, job roles, or active teams. Adobe also states that project managers and issue requestors can assign work to teams when they do not know which individual resource should complete the work or when any team member can handle it. Once a request is assigned to a team, it appears in that team’s Team Requests area until a team member volunteers to work on it. Adobe notification documentation further confirms that team members can receive a “new work request” notification when their team receives a new work request. Request Details is for request information, and Updates is for comments or communication, not assigning responsibility. Therefore, the correct place is Request > Assignments .

In Workfront, to update the planned completion of a task, the assignee should modify the " Planned Completion Date. " This date is used for scheduling and planning purposes to track when the task is expected to be finished. Changing the " Planned Completion Date " adjusts the task ' s projected timeline and allows for a recalculation of project dependencies​​.

In Adobe Workfront, Planned date-based calendar reports are commonly used to visualize project timelines, milestones, and deadlines. They help teams plan and manage workloads based on dates and other time-related factors.

Filters with custom grouping allow users to customize their reports by organizing data in a meaningful way, tailored to specific project or team requirements. Custom groupings enhance the clarity of reports by categorizing data based on selected criteria.

The other options are not correct because Workfront does not support reports that reference multi-select custom fields in a chart format, nor does it allow object names longer than 500 characters​​.

In Workfront, billing rates can be customized for individual projects. To apply a negotiated rate for the Video Editor role within a specific initiative, the project manager can add a new billing rate at the project level. This ensures that the rate is applied only to tasks within the project and does not affect the default system-wide rate for other projects​​.

In Workfront, when the projected completion date exceeds the planned completion date and the task is only 50% complete by May 19, it is automatically flagged as " At Risk. " This alerts the project manager that the task is not progressing according to the original plan, potentially causing delays in the project timeline​​.