PMI Exam PMI-ACP Topic 6 Question 86 Discussion

Actual exam question for PMI's PMI-ACP exam

Question #: 86
Topic #: 6

[All PMI-ACP Questions]

An agile practitioner wants to communicate the effect of technical debt on the project What should the practitioner do?

APost and discuss rises in the burn down chart

BAdjust story points to account for technical debt.

CLog technical debt as an impediment.

DAdd refactoring tasks to all stones

Show Suggested Answer

Suggested Answer: C

by Delsie at Sep 09, 2024, 10:51 PM

Limited Time Offer

25%

Off

Get Premium PMI-ACP Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Salina

2 months ago

Option D sounds like a recipe for a never-ending project. Refactoring tasks in every story? That's like trying to build a house while constantly fixing the foundation. No thanks!

upvoted 0 times

...

Erasmo

2 months ago

I'm going with Option B - adjusting story points is the most honest and straightforward approach. No beating around the bush with this one.

upvoted 0 times

Earleen

1 months ago

I agree with Earleen, Option B seems like the best way to communicate the effect of technical debt on the project.

upvoted 0 times

...

Jerlene

1 months ago

User Comment: I'm going with Option B - adjusting story points is the most honest and straightforward approach.

upvoted 0 times

...

Yvette

1 months ago

I think we should go with Option A - posting and discussing rises in the burn down chart.

upvoted 0 times

...

Ira

2 months ago

Option B is the way to go. The product owner will thank you for being upfront about the technical debt and its impact on the project.

upvoted 0 times

Dierdre

1 months ago

A) Post and discuss rises in the burn down chart

upvoted 0 times

...

Rikki

1 months ago

C) Log technical debt as an impediment.

upvoted 0 times

...

Mitsue

1 months ago

B) Adjust story points to account for technical debt.

upvoted 0 times

...

Azzie

2 months ago

Burn down charts are great, but they don't really capture the impact of technical debt. Option A doesn't seem like the best choice here.

upvoted 0 times

...

Jestine

2 months ago

Adding refactoring tasks to all stories, as in Option D, sounds like a lot of extra work. I'm not sure that's the most efficient solution.

upvoted 0 times

Lashanda

1 months ago

I agree, adding refactoring tasks to all stories does seem like a lot of extra work.

upvoted 0 times

...

Tanesha

2 months ago

C) Log technical debt as an impediment.

upvoted 0 times

...

Lizette

2 months ago

B) Adjust story points to account for technical debt.

upvoted 0 times

...

Marva

2 months ago

A) Post and discuss rises in the burn down chart

upvoted 0 times

...

Precious

3 months ago

I like the idea of logging technical debt as an impediment in Option C. That way, it stays visible and can't be ignored.

upvoted 0 times

An

2 months ago

D) Add refactoring tasks to all stones

upvoted 0 times

...

Long

2 months ago

C) Log technical debt as an impediment.

upvoted 0 times

...

Mattie

2 months ago

B) Adjust story points to account for technical debt.

upvoted 0 times

...

Annamae

2 months ago

A) Post and discuss rises in the burn down chart

upvoted 0 times

...

Roslyn

3 months ago

Option B seems like the most straightforward way to account for technical debt. Adjusting story points is a clear and transparent approach.

upvoted 0 times

Layla

2 months ago

C) Log technical debt as an impediment.

upvoted 0 times

...

Brittni

2 months ago

B) Adjust story points to account for technical debt.

upvoted 0 times

...

Juan

3 months ago

I believe adding refactoring tasks to all sprints can also help manage technical debt.

upvoted 0 times

...

Cherrie

3 months ago

I agree with Kenneth, it's important to address technical debt as an impediment.

upvoted 0 times

...

Kenneth

3 months ago

I think the practitioner should log technical debt as an impediment.

upvoted 0 times

...