Weekly live AEP workshops every Friday - reserve your seat →
Student question · Delivery

The MarTech implementation backlog and dependency tracker

What a MarTech backlog is, when it is built and a ready-made AEP dependency tracker from use cases to go-live.

Quick answer

A MarTech backlog is the prioritised list of everything an Adobe program must deliver - data requirements, schemas, identities, sources, audiences, journeys, destinations, tags and integrations - with a dependency for each item. It starts in pre-planning and discovery, and keeps steering delivery, migration and support. Use cases must be final before architecture, schema, journey and audience design.

What goes into the backlog

  • All data requirements
  • All business use cases
  • All journeys
  • All audiences
  • All integrations
  • All tags, events, schemas, sources and destinations

When the backlog is created

It appears in different forms across the program: during pre-planning and discovery as a list of use cases to solve, during build as a dependency-tracked scrum backlog, and later for migration and support. In every phase the goal is the same — steer the project with objective tracking.

Dependency tracker template

ItemDescriptionDepends onPriority
Business requirementsFinalise use cases and requirementsNoneHigh
Schema designCreate XDM schemasBusiness requirementsHigh
Identity strategyDefine identity namespacesSchema designHigh
Dataset creationCreate profile and event datasetsSchema designHigh
Data ingestionIngest batch, streaming and SDK dataDataset creationHigh
Profile stitchingUnified profile creationData ingestionHigh
Consent mappingIntegrate OneTrust or other consent dataSchema designHigh
GovernanceApply data usage labels and access controlsConsent mappingMedium
SegmentationCreate real-time and batch audiencesProfile stitchingHigh
AJO journeysCreate templates, events and journeysSegmentationHigh
DestinationsConfigure email and advertising destinationsSegmentationMedium
ActivationExport audiences to destinationsDestinationsHigh
CJA setupConnections and data viewsData ingestionMedium
QA validationEnd-to-end testingAll previous itemsHigh
Go-liveFinal approvals and launchQA validationHigh

The critical path

AEP critical pathAEP CRITICAL PATH1Use casesagreed2SchemasXDM3Datasets & identity4Ingestionbatch + stream5Profile & audiences6Journeys & activationthen QA, go-live
Items on the critical path cannot start until their dependency is done.

Frequently asked questions

Who owns the MarTech backlog?

Usually a product owner or delivery lead, with the solution architect owning technical dependencies.

Should consent be early or late in the backlog?

Early. Consent mapping depends only on schema design and must be in place before audiences and journeys go live.

Last updated:

Ready to move your Adobe MarTech program forward?

Consulting for enterprise teams, training for professionals. Tell us where you are today.

WhatsApp