AD0-E908: Adobe Workfront Core Developer Professional

When organizing projects using Portfolios and Programs in Adobe Workfront, two key considerations apply:

Portfolios are containers for Programs: This means that programs are organized within portfolios, and a portfolio can contain multiple programs. This hierarchical structure helps in managing and aligning various programs under broader strategic initiatives represented by portfolios.

Projects can be associated with only one Program or Portfolio: A project can be linked to a single program and, by extension, to the portfolio containing that program. This ensures clarity in project alignment and reporting within the organizational structure.

Reference

These considerations are discussed in the Workfront training materials and documentation, which explain the hierarchical relationships and constraints for using portfolios and programs to organize projects.

Objective: Customize a layout template for a group of users in Workfront.

Customizable Items:

Option A: Views, filters, and groupings used with reports

Option B: On-screen terminology

In Adobe Workfront, there are specific constraints regarding the association of projects, programs, portfolios, and tasks. A project and its tasks can only belong to one portfolio and one program at a time. This means that a single project cannot be simultaneously associated with multiple portfolios or programs. This constraint ensures clear and unambiguous project management and reporting within the organizational structure.

Objective: Track project metrics based on the submitted request without allowing the requester to fill in this information.

Configuration Steps:

Step 1: Create a Custom Form with the necessary metric fields.

Step 2: Do not include these metric fields in the part of the form visible to the requester.

Step 3: Add these metric fields to the project details section instead.

For efficient use of a project template that captures phases within each project and supports critical-path timelines, the following elements are essential:

Predecessors: These define the relationships between tasks, ensuring that the sequence of tasks reflects their dependencies. This is crucial for maintaining the integrity of the critical path.

Milestone Tasks: These are key tasks that mark significant points or stages in the project timeline. Including milestone tasks helps in tracking progress and ensuring that critical deadlines are met.

Reference

The importance of predecessors and milestone tasks in project templates is emphasized in Workfront's project management guidelines and best practices for creating reusable workflows.

To ensure Tyson is not over-allocated in the Workload Balancer, a system administrator can take the following actions:

Edit Task Allocation: The administrator can adjust the allocation of hours for the 'Verify Intake Form' task. Specifically, they can redistribute the hours from Wednesday (where Tyson is over-allocated with 9 hours) to other days where Tyson has available capacity.

Reassign Task: The administrator can reassign the 'Kickoff Meeting' task to another user who has available capacity. This will immediately reduce Tyson's workload and ensure the task is still completed without overburdening Tyson.

Reference

Workfront documentation on using the Workload Balancer highlights these options for managing user allocations and ensuring workloads are balanced across team members.

Objective: Identify prerequisites for using the Resource Planner and Workload Balancer.

Prerequisites:

Prerequisite 1: Job Roles assigned to Tasks

Prerequisite 2: Task Planned Hours greater than zero

Prerequisite 3: Task Durations greater than zero