Adobe AD0-E903 Exam - Topic 3 Question 21 Discussion

Actual exam question for Adobe's AD0-E903 exam

Question #: 21
Topic #: 3

A company has decided that all projects for the year need to be created from templates and staffed in the following quarter. The projects will need to remain in a backlog until the team has capacity to work on them. There has been confusion previously because the team used Planning status for all work not started.

What should the project manager do to help the team see the difference between work in the backlog versus work that is now being planned?

ALoad the project template once the team has bandwidth to start on the project.

BCreate projects but leave the roles in place without assigning users.

CCreate a custom status for Backlog to use prior to using the Planning status.

Show Suggested Answer

Suggested Answer: C

In Workfront, creating a custom status specifically for 'Backlog' allows the team to differentiate between work that is pending capacity and work that is actively being planned. This prevents confusion and allows for better project tracking, ensuring that tasks move smoothly from backlog to the planning phase when appropriate.

by Hui at Jun 16, 2025, 09:16 PM

Limited Time Offer

25%

Off

Get Premium AD0-E903 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Jestine

2 months ago

Wait, are we really using templates for everything now?

upvoted 0 times

...

Elouise

2 months ago

Not sure if that’s the best way to go.

upvoted 0 times

...

Glendora

3 months ago

Leaving roles unassigned seems like a bad idea.

upvoted 0 times

...

Mel

3 months ago

Totally agree, it would clear up the confusion!

upvoted 0 times

...

Vicki

3 months ago

I think creating a custom status for Backlog makes sense.

upvoted 0 times

...

Kina

3 months ago

I’m a bit confused about whether leaving roles unassigned would actually solve the problem. It seems like it might just add to the confusion instead.

upvoted 0 times

...

Jacinta

4 months ago

I feel like we practiced a similar question where using a custom status made a big difference in visibility for the team. It could really help here too.

upvoted 0 times

...

Lonny

4 months ago

I'm not entirely sure about the options, but I think loading the project template only when the team is ready might just delay things further.

upvoted 0 times

...

Eleonore

4 months ago

I remember we discussed the importance of distinguishing between backlog and planning statuses in our last class. It seems like creating a custom status could really help clarify things.

upvoted 0 times

...

Rasheeda

4 months ago

Yeah, I agree with Emily. Option C is the way to go here. Creating a separate "Backlog" status will help the team clearly see what's in the pipeline versus what's actively being planned. Simple but effective.

upvoted 0 times

...

Vincenza

4 months ago

Okay, I think I've got it. The issue is that the team was using the "Planning" status for all work, even stuff that was just in the backlog. So we need a way to distinguish that. Option C seems like the best choice - creating a custom "Backlog" status to use before moving to "Planning".

upvoted 0 times

...

Carman

5 months ago

Hmm, I'm a bit confused by the wording of the question. It's talking about project templates and a backlog, but I'm not sure how that relates to the different statuses. I'll need to think this through carefully.

upvoted 0 times

...

My

5 months ago

This seems like a straightforward question about project management. I think the key is to find a way to differentiate between work that's in the backlog versus work that's actively being planned.

upvoted 0 times

...

Frederica

8 months ago

I'm going with C as well. Gotta love it when a project manager comes up with a custom status to solve a problem. Like a project superhero, saving the day with their status-creating powers!

upvoted 0 times

Annice

8 months ago

Yeah, creating a custom status for backlog seems like a smart move. It will make things much clearer for the team.

upvoted 0 times

...

Rose

8 months ago

I think C is the best option too. It will definitely help clarify the difference between backlog and planning.

upvoted 0 times

...

Willetta

8 months ago

Hmm, I'm not sure. Option B seems like it could work too, but then the roles might get confusing. Better to just have a separate Backlog status, in my opinion.

upvoted 0 times

...

Malika

8 months ago

I prefer loading the project template once we have bandwidth to start.

upvoted 0 times

...

Frederica

8 months ago

I think option C is the way to go. Having a dedicated Backlog status will make it crystal clear which projects are just sitting in the queue versus ones that are actively being planned.

upvoted 0 times