ACP-420 study plan
ACP-420 · Give each week a clear focus.
8 weeks · About 7 hours per week
Project creation, project types, and project-level configuration
Distinguish company-managed from team-managed projects and list which configuration elements each type owns
Create one project of each major type (software, business, service) and record the default scheme set each receives
Map the project-level configuration surface: project details, project category, default assignee, project lead, and notification/email settings
Explain how a project template choice constrains later issue type, workflow, and field decisions
Your checkpoint
A one-page comparison matrix covering at least 4 project types with columns for scheme ownership, who can edit configuration, and typical use case, plus 3 self-written practice questions answered from it
Workflows, workflow schemes, and transitions
Build a workflow from scratch with at least 5 statuses and label each transition as global, directed, or initial
Add conditions, validators, and post functions to transitions and state the execution order for each transition
Create a workflow scheme and associate it with a project, then verify which issue types map to which workflow
Diagnose the effect of editing a shared versus inactive workflow on live issues
Your checkpoint
A working 5-status workflow in a test project plus a written transition table (from status, to status, condition, validator, post functions) and answers to 3 troubleshooting scenarios
Permissions, permission schemes, and issue security
Explain the permission scheme model and rank the sources of access (permission scheme, issue security, project role, group, application access)
Create a custom permission scheme granting access via project roles rather than individual users and apply it to a project
Configure an issue security scheme with 3 levels and verify visibility as two different test users
Trace a 'user cannot see the issue' complaint through issue security level, permission scheme, and project role membership
Your checkpoint
A permission and issue security design document for a sample project, validated by a two-user visibility test log with at least 6 test cases and observed results
Fields, field configuration, and screen schemes & Issue types, schemes, and issue type schemes
Create custom fields of 5 different types and place each on the correct screen for the intended operation (create, edit, view)
Build a field configuration and field configuration scheme, then demonstrate which fields are required versus optional per issue type
Assemble a screen scheme and screen scheme-to-issue-type mapping and verify the create versus edit experience
Design an issue type scheme with at least 4 issue types and a sub-task type, and attach it to a project
Your checkpoint
An end-to-end field and screen configuration applied to a test project, documented as a mapping table (issue type → screen scheme → screens → fields with required/optional flags)
Agile boards, backlog, and sprint configuration
Create a board from an existing filter and explain how the filter's JQL determines board contents
Configure board columns and status mapping so each column corresponds to workflow statuses
Configure and run a sprint end-to-end: backlog ranking, sprint creation, start, complete, and incomplete-issue handling
Adjust estimation statistic and configure at least two swimlane options, then compare their effect on the board view
Your checkpoint
A board configuration record showing filter JQL, column-to-status mapping, swimlane setting, and estimation statistic, plus a completed sprint walkthrough with screenshots-free written steps and 3 configuration pitfalls noted
Project roles, groups, and team access management & Dashboards, filters, and reporting for projects
Create project roles, populate them with groups rather than individuals, and grant permissions to those roles in a permission scheme
Distinguish group membership, project role membership, and application access, and state which one gates which behavior
Build a JQL filter, share it with a project role, and use it to drive a dashboard gadget
Add 3 dashboard gadgets that report on project progress and set the dashboard sharing scope appropriately
Your checkpoint
A shared filter plus dashboard with 3 working gadgets, accompanied by a role/group access matrix showing exactly which team type can see and edit each artifact
Project administration practices and troubleshooting & Project creation, project types, and project-level configuration & Workflows, workflow schemes, and transitions
Reproduce and resolve 5 common administration failures (scheme not applied, missing permission, broken transition, wrong screen on edit, board column mismatch)
Audit a project's full scheme association list and identify any scheme that is shared when it should be dedicated
Re-run practice questions from weeks 1-3 and re-derive the answers for every item missed
Document a safe change procedure for editing a live workflow scheme or permission scheme
Your checkpoint
A troubleshooting playbook of 5 symptom → diagnostic steps → fix entries, plus a completed scheme audit of one project with all mismatches corrected
Issue types, schemes, and issue type schemes & Fields, field configuration, and screen schemes & Permissions, permission schemes, and issue security & Agile boards, backlog, and sprint configuration
Complete two timed full-length practice sets and score each domain separately
Rebuild from memory the scheme chain for a project: issue type scheme, workflow scheme, field configuration scheme, screen scheme, permission scheme, notification scheme
Drill the two lowest-scoring domains until each reaches a self-set target score
Summarize the 10 highest-risk distinctions (shared vs dedicated schemes, role vs group, required vs optional field, global vs directed transition) into a single review sheet
Your checkpoint
A scored practice-exam log for both attempts with per-domain percentages, plus a one-page final review sheet of the 10 riskiest distinctions
Milestones
Week 2: Can build a multi-status workflow with validators and post functions, attach it via a workflow scheme, and explain the transition execution order without notes
Week 4: A test project is fully configured end-to-end (issue types, workflow, fields, screens) and a second user can be granted access purely through project roles
Week 6: A shared filter drives a dashboard visible to the correct role, and the role/group access matrix has no unresolved access gaps
Week 8: Both timed practice sets completed with every domain at or above the self-set target and no domain left unreviewed