Exam PMI-ACP topic 1 question 161 discussion

The other options, while useful, do not provide the same level of continuous, proactive quality assurance: B. Perform demos at the end of each iteration helps gather feedback but does not directly address the day-to-day code quality. C. Send coding to the quality assurance (QA) team upon completion could lead to a bottleneck and delays in addressing issues if problems are found late. D. Demonstrate each feature to the client as soon as coding is complete can be valuable for feedback but does not focus on the internal process of ensuring quality before the client sees the work.

Expected Benefits increased code quality: “programming out loud” leads to clearer articulation of the complexities and hidden details in coding tasks, reducing the risk of error or going down blind alleys better diffusion of knowledge among the team, in particular when a developer unfamiliar with a component is pairing with one who knows it much better better transfer of skills, as junior developers pick up micro-techniques or broader skills from more experienced team members large reduction in coordination efforts, since there are N/2 pairs to coordinate instead of N individual developers improved resiliency of a pair to interruptions, compared to an individual developer: when one member of the pair must attend to an external prompt, the other can remains focused on the task and can assist in regaining focus afterwards https://www.agilealliance.org/glossary/pairing/#q=~(infinite~false~filters~(postType~(~'page~'post~'aa_book~'aa_event_session~'aa_experience_report~'aa_glossary~'aa_research_paper~'aa_video)~tags~(~'pair*20programming))~searchTerm~'~sort~false~sortDirection~'asc~page~1)