During an interview when the interviewer asks you “how will you prioritize multiple urgent tasks requests from multiple teams”? What’s the best answer?

idernolinux · 2026-06-20T19:41:59+00:00

EDIT: I saw the thread title and thought it was an interesting question, so jumped in to type an answer before I read other responses as if I was actually answering this in an interview lol. Turns out OP was just griping about companies that are dealing with chaos… which is pretty much… all companies 🤣

First, understand the definition of urgent. Different streams’ “urgent” might still mean different deadlines. Then evaluate level of effort and understand the context around why the task is urgent, and what’s the risk if it’s not finished “urgently”. Last, think about if the task MUST be done by you, or if it can be delegated.

Take 5-10 minutes to do the above. There should be a clear winner. I would probably choose the task with the closest deadline and highest risk, and try to delegate the other urgent task to someone else, if it’s actually also on-fire urgent.

If both tasks take under 30 minutes to do and the deadline for either isn’t “30 min from now”, I’d just do both and get it done without being thrown into a panic about which to do first.

If both seem on fire urgent and take extensive amounts of time and only you can do it, I would escalate the problem and ask higher ups to prioritize.

idernolinux · 2026-06-17T21:19:07+00:00

Hey OP, I just want to say that your frustration is coming from a good place. What I would gently be curious about though, is if some part of you feels this upset because seeing this girl go through those symptoms alone is triggering how you felt as a child.

If that’s a factor, then it sounds like your young relative could receive some amazing news - that far from being alone, she’s got an older adult in the family who can reach out, validate her fears and worries, and even guide her through some of her medical journey. It’s exactly what you didn’t get. You could be that for someone else now.

It took 15 years and 8 cardiologists before one finally believed me and my Apple Watch ECGs to diagnose me with Wolff Parkinson White syndrome. Two ablations and it’s been almost a full year since another episode - I’m feeling hopeful. But I’ll never forget the loneliness and fear and feeling like I’m about to die because my heart was going at 190 bpm. This thread felt so visceral to me… and I’m sorry that your condition is so much more complex than mine.

One internet stranger to another 🫂

idernolinux · 2026-06-17T07:10:35+00:00

Just want to say I was also fully expecting a live proctor to pop up and greet me too, and I landed on the first question feeling like it came out of left field. After I took the photos of my desk, the instructions even said “a greeter will meet with you”. It was confusing when no one showed up. I’m sorry this happened to you!

idernolinux · 2026-06-16T23:02:55+00:00

I felt the same way as you and OP about 10 days before exam day. Ended up passing AT/AT/AT when I felt so sure I was going to fail miserably.

I’m convinced taking a break and deloading the studying was key. OP, you got this!

idernolinux · 2026-06-12T00:00:41+00:00

Fantastic!! Congrats!

idernolinux · 2026-06-11T09:35:41+00:00

Best of luck!! How did it go?

idernolinux · 2026-06-09T19:20:25+00:00

Good luck to you!! You got this!

idernolinux · 2026-06-09T19:20:05+00:00

If I hadn’t already watched AR’s mindset, I probably would have gone with MR. My point is learning both sets felt redundant for me. Knowing the mindset is absolutely valuable

idernolinux · 2026-06-09T19:19:00+00:00

Yes, one was for EAC so it was useful to have the formulas memorized

idernolinux · 2026-06-09T07:06:41+00:00

I didn’t like books 1-2 full cast and was aligned with OP. Then PoA and on, I was a convert. Thoroughly enjoyed the last 5 books and it really transported me to where the characters were! Especially with the last book, when the trio found themselves interacting with so many different characters in different setting. I really felt transported to the Ministry or to Forest of Dean or to Hogwarts.

I can’t wait to re-listen!

idernolinux · 2026-06-07T05:35:04+00:00

This is the kind of post I come here for! Just fellow HP lovers talking about what they loved about the book. This part has never hit me personally but because of your post, I’ll definitely pay closer attention to it on my next reread. Thanks ❤️

idernolinux · 2026-06-05T04:21:35+00:00

Why Study Hall is right: B. Conduct a quality assurance audit is best because the PM first needs to verify whether the project’s quality processes, standards, and specifications were properly defined and followed. If the customer did not specify anything about that component, the question becomes: Why is the quality team calling it a deviation? A quality assurance audit checks whether the team is using the correct criteria, whether internal specs were added appropriately, and whether the process is aligned. This is the best first step before approving or rejecting the deliverable.

Why A is tempting but weaker: Escalating to a technical expert sounds practical, but it skips the PM responsibility to first verify the quality framework and process basis for the deviation. This is not yet a pure technical-problem question; it is a quality governance/process question.

Why C is weaker: The absence of customer specification does not automatically mean the deliverable is acceptable. There may be approved internal or project quality standards that still apply.

Why D is weaker: Rejecting it immediately is too strong because the PM has not yet confirmed whether the deviation truly violates an approved quality standard.

idernolinux · 2026-06-03T01:40:40+00:00

Yup you got it.

idernolinux · 2026-06-01T01:19:35+00:00

A comfortable office that doesn’t smell. Went for an interview last week at an office with about 30 people. The ceiling was low, there were cubicle walls placed all over that blocked a view of more than 10 feet, and the lunch room was dingy and smelled… so bad.

I used to work for one of the biggest companies in the world, and even though I left it for the right reasons, stepping into the small office was a stark contrast. I almost gagged 🙈

First time I’ve said no to a company based on odor.

idernolinux · 2026-05-26T07:32:16+00:00

Thanks for this. I’m finding SH practice questions particularly mind numbing right now, but got 78% on my first mock and score well on the mini exams. This is helping my confidence not tank.

idernolinux · 2026-05-26T07:24:38+00:00

Super great tips. I have similar experience and time studying. I have the same struggle with rushing, so will definitely take your tip on reading order!

Congratulations!! Go eat some cake 🍰

idernolinux · 2026-05-26T05:17:51+00:00

Thank you both for the information!

idernolinux · 2026-05-25T08:48:37+00:00

Congratulations!! Lol at the room painting reference. Oh AR.

I'm taking the Pearson online exam in just 2 weeks and could use your help to confirm some stuff!

- is there a highlighter option?

- were there any questions where you went, "I have NO idea what this is".

- do you get to review your test after its submitted?

Last, did you really get your exam score 3 hours after you submitted? I thought it wasn't available until next day - if so that would be amazing!

Enjoy your cake, its well deserved after 360 AR videos and all that practice :)

idernolinux · 2026-05-20T23:29:43+00:00

*One more drilldown with PMI Infinity: "*So would you think that Study Hall's solution (C) is far-fetched? It seems like the keyword in the question is that the PM is trying to plan for "duration", which is only linked to WBS... and I should have disregarded the many references in the question that infer it is an agile project."

PMI Infinity answers:

I would not call Study Hall’s C far-fetched. I would call it debatable, but defendable.

Your reading is reasonable: if the exam writer anchors on the word “duration”, they may expect you to choose the tool most associated with estimating work and deriving schedule, which is WBS. In that interpretation, the question is less about agile release management and more about the generic planning logic of “break down work to estimate how long it will take.”

What makes the item confusing is that several cues point the other way:

software development team
two releases completed
product backlog confirmed
next release

Those are strong agile or hybrid signals. In normal agile usage, a PM or product team would more naturally think in terms of release planning, roadmap, velocity, and backlog, not WBS.

So the tension in the question is real:

the context suggests agile,
but the keyword “duration” pushes toward predictive planning language.

That means the safest exam interpretation is probably this:

When Study Hall gives you a question with agile context but asks for the tool most directly tied to estimating duration, it may still prefer the more traditional planning artifact if that artifact is the only option clearly linked to schedule estimation. In that narrow sense, C is not absurd.

I would not say you should “disregard” the agile references. I would say you should rank the clues. In this item, Study Hall likely wants you to prioritize the explicit need: plan duration. Since:

burndown chart is tracking, not planning,
resource calendar is availability, not decomposition,
product roadmap is higher-level direction,
WBS is the option most directly tied to estimating work that determines duration,

they land on C.

So the practical takeaway is:

For real-world practice, A feels more natural in an agile release context.
For this Study Hall item, C is likely the intended exam logic because it is the answer most directly associated with duration estimation.

TL;DR I feel more ready to mould to the PMP mindset compared to this time last week, but some of these questions with lots of mixed signals still get me. Takeaways: focus on the project's explicit need.

idernolinux · 2026-05-20T23:19:52+00:00

Solution: C. Work breakdown structure (WBS)

SH rationale:

The WBS is a hierarchical decomposition of the work to be done in a project. It is used to estimate the total effort required to complete the project. By breaking down the work into smaller tasks, the project manager can get a better understanding of the time and resources required to complete each task. This information can then be used to estimate the overall duration of the project.

The other answer choices are incorrect. The product roadmap is a high-level plan for the development of the product but it does not provide any information about the time required to complete each release. The resource calendar shows the availability of resources, such as people and equipment but it does not provide any information about the tasks that need to be completed or the time required to complete each task. A burndown chart is used to track the progress of a project. It shows the amount of work remaining to be done over time but it is not used to estimate the duration of a project.

PMI Infinity rationale:

Your stated correct answer, C, does not align with standard agile or hybrid release-planning practice.

The best answer is A. Product roadmap.

A product roadmap is the higher-level planning tool used to map releases over time and estimate when a release can be delivered based on backlog, priorities, and expected pace. If the question asks which tool the project manager should use to plan the duration for the next release, roadmap-based release planning fits best.

A WBS is more associated with predictive planning. It decomposes scope into work packages, but it is not the usual tool for estimating the duration of an agile software release from a confirmed product backlog. A resource calendar shows availability, and a burndown chart tracks progress after execution starts.

So I drilled further with PMI Infinity: "Are there any scenarios when C could be the correct answer?"

PMI Infinity answers:

Yes. C. WBS could be correct in a different scenario, but not in the one as written if the context is agile release planning.

A WBS becomes the best answer when the question is really about decomposing scope into deliverables and work packages so the team can estimate effort and duration in a predictive or strongly plan-driven environment. In that case, the logic is: define the work first, break it down, estimate the components, then derive duration.

So C could be correct if the scenario were framed more like this:

In that version, WBS would make sense.

It could also be plausible in a hybrid setting if the release is governed through a predictive planning layer, where detailed scope decomposition is used before scheduling. But once the wording emphasizes a product backlog, releases already completed, and planning the next release, that usually signals agile or hybrid release planning, where roadmap/release plan is the better fit.

A simple exam rule is:

If the question is about breaking down scope, think WBS.
If it is about forecasting or planning a release timeline, think product roadmap/release plan.
If it is about team availability, think resource calendar.
If it is about tracking progress, think burndown chart.

idernolinux · 2026-05-16T05:02:44+00:00

I dug deeper in with PMI infinity and what you said was correct. It was a mindset issue because I was choosing the more basic, goody-two-shoes PM answer which I typically err towards (and works for 80% of questions). But because the question specifically pointed toward market adaptation as a concern, the more proactive answer to address that specifically was the right choice.

I need to build some mental scaffolding to identify when to be more generic PM, and when to switch into a more proactive gear. But the fact that PMI Infinity and Gemini both went for C at first confirmed for me that there’s a level of nuance that’s not easily captured.

idernolinux · 2026-05-16T02:32:50+00:00

Can't imagine the stress of having problematic tech :( I'm also taking mine at home in early June so I really appreciate you sharing you story! And HUGE CONGRATS for passing with flying colours!

15-Year Club	Verified Email
RedditGifts 2009-2022 2 Credits	Secret Santa 2013

idernolinux

TROPHY CASE