Adobe Workfront
Core Developer Expert

You should have at least 18-24 months experience with Adobe Workfront, and should be able to:

• Navigate the Workfront system, understanding where its functionality resides
• Configure all aspects of the system
• Discuss requirements with customers and translate those into a viable solution
• Elicit and modify existing process for improvement in a collaborative way
• Understand and apply the marketing and PMO uses cases
• Recommend and create reports that support customer processes

Section 1: Core system administration and setup (17%)

• Given a scenario, describe ways to effectively share permissions and access.
• Given a scenario, identify when a group status versus a system status should be used.
• Given a data set, demonstrate the capabilities of kickstarts.
• Given a scenario, identify best practices for auto-provisioning users.
• Given a scenario, demonstrate how Groups and Teams within a user’s profile can affect what can be seen or done within Workfront.
• Given a scenario, recommend a Boards configuration to meet a custom requirement.
• Given a scenario, identify best practices for group administration.

Section 2: Intake, custom forms, and project initiation (13%)

• Given a scenario, identify the configuration areas needed to support the work allocations.
• Given a scenario, identify how a value is passed to a project custom form.
• Given a scenario, describe what must be done to address reporting and calculation errors.
• Given a scenario, identify supporting elements that lend themselves to templates.
• Given a scenario with multiple forms, determine actions to control access, visibility and dependency.
• Given a scenario with calculated fields on multi-object forms, identify the correct formula.

Section 3: Strategic functionality: portfolio and program management, resource management (13%)

• Given a scenario, define tools to capture changes in the project scope.
• Given a scenario, create a view that identifies within a portfolio whether a project meets the average level of requisite criteria to be executed.
• Given a scenario, describe ways to manage risk qualitatively or quantitatively.
• Given a scenario, provide a mechanism to ensure the highest priority projects are set up to be resourced appropriately.
• Given a scenario, provide a mechanism to ensure that projects are fully staffed by using Resource Management tools.
• Given a scenario, use Resource Management tools to determine why a user is overallocated.

Section 4: Document management and proof (13%)

• Given a scenario, demonstrate when to utilize document management versus proofing
• Given a scenario, identify best practices for using the proofing viewer, settings, and markup functionality
• Given a scenario, demonstrate how to edit and set permissions on a file
• Given a scenario, demonstrate how to set up external document storage with security restrictions
• Given a scenario, set up a connection to AEM as a Cloud Service or AEM Assets Essentials.

Section 5: Reporting (11%)

• Given a scenario, describe ways to combine multiple columns of data into a single column.
• Given a report or filter, demonstrate the merits of using wildcard values.
• Identify how to report on parent-to-child relationships using native reporting.
• Given a scenario, describe how reporting facilitates efficient execution of work.
• Given a scenario, illustrate Workfront Reporting to monitor and improve user adoption.
• Given a scenario, determine how a field type would render on a report. (Field types include: rich text, images, multi-select)

Section 6: Methodology / best practices / use cases (22%)

• Given a scenario within Workfront, demonstrate functionality for setting up tracking of deliverables that are part of a single campaign.
• Given a scenario within Workfront, demonstrate functionality around strategic prioritization and justification of work.
• Given a scenario within Workfront, demonstrate functionality around financials, utilization, forecasting, billing rates/records.
• Given a scenario within Workfront, demonstrate functionality around setting up workflow and approvals.
• Given a scenario, recommend a framework for governance around system administration when expanding a client’s instance.
• Given a scenario, identify areas for consideration when expanding a client’s instance to enable additional teams to work together.
• Given a scenario using Workfront Boards, identify native features to show progress.
• Given a scenario, recommend a framework for governance around system and group administration.

Section 7: Business consulting (11%)

• Given a scenario, describe the process needed to fully support effort of implementing Workfront in a cross-functional department.
• Given a scenario, explain how to adapt an existing Workflow to meet a recent change in a critical, inflight business process.
• Given a scenario, identify configuration settings that are most difficult to change to a given instance.
• Given a scenario, identify the key considerations of change management for a Workfront implementation
• Given a scenario where a client has multiple teams, provide a recommendation to increase efficiency.