AD0-E903 Adobe Workfront Project Manager Professional Questions and Answers

In Workfront, a "Portfolio" is a parent object that can contain multiple programs and projects. Each Portfolio can have a hierarchy of child objects such as programs, which further break down into projects. A project, while it contains tasks and issues, is considered a child within the larger hierarchy of a portfolio. Issues, on the other hand, are typically linked to tasks or projects but are not used as parent objects. This hierarchy enables Workfront users to organize and manage their work across various levels​​​.

In Adobe Workfront, to avoid sending unnecessary notifications when adjusting timelines, the Recalculate the project timeline option is used. This ensures that the timeline is updated appropriately based on the changes, but it prevents the system from sending notification alerts to the project team. Recalculation helps align task dependencies and timeline adjustments, preventing confusion among team members​​.

To meet the executive's request, the best approach is to create a Project Report in the Reports area. Adding a column for Actual Cost and sorting it in descending order ensures that the most expensive projects appear at the top. Additionally, by adding a prompt for Portfolio Name , the report can be filtered by the specific portfolio, allowing for tailored views across different portfolios​​.

Even though tasks may be marked as 100% complete, their Status may still be listed as incomplete in reports if the task's status has not been updated to "Completed." The Status column provides insight into the current state of the task, which helps identify if the task is still listed as "In Progress" or another incomplete status despite being marked as fully complete. Adding this column clarifies why the task appears in the Incomplete Tasks Report ​​.

The most comprehensive approach is to create two separate reports—one for tasks and one for issues —with filters set for "Pending Approval." Grouping the results by project name ensures that the project manager can see all relevant tasks and issues organized per project. Adding these reports to a dashboard consolidates the information into a single view, providing easy access for tracking pending approvals​​.

In Adobe Workfront, Planned Dates are the dates that project managers can manually modify. These dates represent the schedule that the project is expected to follow and can be adjusted based on project needs. Estimated and Projected Dates are automatically calculated by the system based on task progress and dependencies, and these cannot be manually modified directly by a project manager. The Projected date is influenced by changes in the actual completion rate of tasks, whereas the Planned Date is the baseline schedule​​.

In Workfront, when adjusting user access, it’s important to ensure that Program Manager A only has the necessary level of access to their own program. To rectify the over-access issue, the portfolio manager must share the relevant program with Program Manager A with the correct Manage access and remove their broader Manage access to the portfolio. This restricts their control to only their specific program​​.

In Workfront, when a task owner is unavailable due to time off, they can update the Commit Date to reflect when they are available to work on the task. This prevents delays and ensures the task is completed within a revised timeline. The Commit Date feature is designed to accommodate personal schedules and ensure tasks are accurately tracked without putting the task "At Risk" unnecessarily​​.

In Adobe Workfront, team members can be subscribed to a request so that they receive updates whenever changes or comments are made. This ensures they stay informed of any progress or issues. Adding a request to favorites only bookmarks it for easy access, but does not trigger automatic notifications. Making multiple primary contacts is not an efficient way to handle notifications​​.

In Workfront, a "Program" is used to group related projects that share a common objective or need to be tracked together, such as adherence to budget and timeline. Programs allow for collective reporting on these projects, making it easier for team leads to monitor progress, manage resources, and report on key performance indicators (KPIs) across multiple projects​​.

Groups in Adobe Workfront serve as organizational entities that can be associated with specific Companies or Projects to manage workflows or permissions more effectively. Additionally, each Group can have a Group Administrator assigned, who is responsible for managing the group's settings, permissions, and workflows. These roles and associations help in structuring how work and permissions are allocated across different teams or departments​​.

In Adobe Workfront, the "Assignments" field allows a project manager to see all the users assigned to a task. This field is useful for viewing multiple assignees on a single task, as tasks can have more than one person responsible. The "Assigned To" and "Assigned" fields are often used for single-user assignments and are not as comprehensive for viewing all task assignees​​.

In Adobe Workfront, when creating a Milestone Step within the Setup area, the Key field is essential as it serves as a unique identifier for each milestone step. It is used to define the specific step within a milestone path that can be associated with tasks in a project. The Status and Description fields are not used for creating the milestone step itself but are more relevant for defining attributes or metadata​​.

In Workfront, setting the correct task constraint and planned hours ensures that the task starts on the intended date (September 23) and allows the team to track the time allocated (10 hours) over a 2-week duration. "Must Start On" ensures the task begins exactly on the planned start date​​.

The best practice is to incorporate an approval process into the project template so that it is automatically triggered when a project reaches the completion stage. This ensures consistency and saves time by removing the need to manually set up approval processes for each new project. This approach also guarantees that the Project Sponsor's review is systematically included before the project is officially closed​​.

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​​.

The team lead should create a report in the Reports area to see all hours logged by the home team during the current month. By using filters for Home Team ID and Entry Date , and grouping the results by Project Name , the team lead can view hours logged in a project-based format for the entire home team during the selected time period​​.

In Workfront, Teams are operational entities that can be assigned to tasks, while Groups are organizational entities that are not assignable to tasks. Additionally, work requests can be routed to both Groups and Teams, depending on how the organization is structured and how the routing is set up​​.