Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
CompTIA Project+ · CompTIA
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
The correct answer is: ✅ B. Scrum (Most Voted and Correct) Here's why: Scrum is an Agile framework that emphasizes continuous collaboration between the development team and the business (product) team, including: Daily stand-ups Sprint planning Sprint reviews Backlog grooming Frequent feedback and decisions from the Product Owner (a business role) This constant involvement means that the business team (especially the Product Owner) must be highly available and responsive throughout the project.
Agile deployments generally take the most time with regular meetings and is iterative, meaning business team involvement would be necessary throughout. SDLC is the Software Development Life Cycle and doesn't necessarily need business team involvement. Prince2 is a Waterfall methodology which isn't iterative and likely wouldn't require business team involvement throughout. D is just C.
SDLC (Software Development Life Cycle): This isn't a specific methodology but rather a general framework encompassing various approaches. Business team involvement can vary depending on the chosen methodology within the SDLC. Scrum: This agile methodology emphasizes close collaboration and frequent interaction between the development team and the business team. This option likely requires the most availability from the business team due to ongoing participation in sprint planning, backlog refinement, and daily scrum meetings. PRINCE2: This is a structured project management methodology with less emphasis on continuous business team involvement compared to Scrum. While participation in key stages is important, it may not require the same level of ongoing availability. Waterfall: This traditional waterfall methodology typically has less frequent interaction between development and business teams compared to agile approaches. Business involvement is crucial during initial requirements gathering and later stages like acceptance testing, but overall availability requirements might be lower than Scrum.