The project velocity has recently slipped, and a decision was made to skip testing to increase the momentum and bong the project back on track. What will the project manager need to focus on as a result of this decision?
Technical debt refers to the additional work that will be required in the future due to taking shortcuts or making decisions that prioritize short-term gains over long-term sustainability.
Skipping testing can lead to significant technical debt as bugs and errors may be introduced into the software that will require additional work to fix later. Additionally, skipping testing can also lead to reduced quality and user satisfaction, which can ultimately harm the success of the project.
The decision to skip testing in order to increase project momentum and get back on track can have several consequences. One of the primary concerns related to this decision is increased technical debt. Technical debt refers to the accumulated shortcuts, compromises, and suboptimal solutions that can result from taking actions to expedite project delivery without properly addressing quality and testing.
Technical debt is a metaphor used in software development that is intended to help people understand that there is a cost to making short-term decisions that result in long-term increases in cost. According to the metaphor, this cost increases similarly to accrued interest, over time
This section is not available anymore. Please use the main Exam Page.PMP Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
RevZig67
Highly Voted 1 year agoOnly12go
Most Recent 7 months, 1 week agovictory108
9 months agokevzzz
9 months, 3 weeks agosnagile
1 year ago