PMI Exam PMI-ACP Topic 9 Question 94 Discussion

Actual exam question for PMI's PMI-ACP exam

Question #: 94
Topic #: 9

[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 Nobuko at Dec 11, 2024, 08:06 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Fannie

2 months ago

Ah, the age-old question of technical debt. I'd say option C is the way to go - it's the most transparent approach.

upvoted 0 times

Nilsa

1 months ago

Adding refactoring tasks to all sprints can help in gradually reducing technical debt and improving the overall project quality.

upvoted 0 times

...

Eleni

1 months ago

It's important to address technical debt early on to prevent it from becoming a bigger issue later.

upvoted 0 times

...

Tyra

1 months ago

I agree, logging technical debt as an impediment helps the team understand the impact it has on the project.

upvoted 0 times

...

Yolando

2 months ago

Option C is definitely the way to go. Transparency is key when it comes to technical debt.

upvoted 0 times

...

Alaine

2 months ago

Hmm, I'm torn between B and C. Technical debt is a tricky beast, but I think logging it as an impediment is the way to go.

upvoted 0 times

...

Lettie

2 months ago

I'm going with D. Adding refactoring tasks to all stories is a proactive way to address technical debt as it arises.

upvoted 0 times

...

Maryann

2 months ago

B seems like a good option too. Adjusting story points to account for technical debt can help the team understand its effect.

upvoted 0 times

Coral

1 months ago

C) Log technical debt as an impediment.

upvoted 0 times

...

Annamae

2 months ago

B) Adjust story points to account for technical debt.

upvoted 0 times

...

Jesse

2 months ago

A) Post and discuss rises in the burn down chart

upvoted 0 times

...

Viva

2 months ago

B seems like a good option too. Adjusting story points to account for technical debt can help the team understand its effect.

upvoted 0 times

...

Isaac

2 months ago

B) Adjust story points to account for technical debt.

upvoted 0 times

...

Louisa

2 months ago

A) Post and discuss rises in the burn down chart

upvoted 0 times

...

Glendora

2 months ago

I think adjusting story points to account for technical debt is a good approach too.

upvoted 0 times

...

Fernanda

2 months ago

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

upvoted 0 times

...

Lavelle

3 months ago

I think the correct answer is C. Logging technical debt as an impediment is the best way to communicate its impact on the project.

upvoted 0 times

Lynette

2 months ago

D) Add refactoring tasks to all stones

upvoted 0 times

...

Eladia

2 months ago

C) Log technical debt as an impediment.

upvoted 0 times

...

Jerry

2 months ago

B) Adjust story points to account for technical debt.

upvoted 0 times

...

Carolann

2 months ago

A) Post and discuss rises in the burn down chart

upvoted 0 times

...

Ruby

3 months ago

I agree with Selma. It's important to address technical debt as an impediment.

upvoted 0 times

...

Selma

3 months ago

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

upvoted 0 times

...