nerdexam
CompTIA

PK0-005 · Question #159

A development team, which is working on a software project demonstrates software functionality 10 project stakeholder a week before the implementation date. Several stakeholders comment that the…

The correct answer is B. Requirements Traceability Matrix. To validate software functionality against expectations when stakeholders are dissatisfied, the project manager should use a Requirements Traceability Matrix.

Tools and documentation

Question

A development team, which is working on a software project demonstrates software functionality 10 project stakeholder a week before the implementation date. Several stakeholders comment that the software does not meet the communicated expectations. Which of the following tools should the project manager use to validate the functionality?

Options

  • AProject status report
  • BRequirements Traceability Matrix
  • CDetect log
  • DSigned project charter
  • EWork breakdown structure

How the community answered

(49 responses)
  • A
    14% (7)
  • B
    69% (34)
  • C
    8% (4)
  • D
    6% (3)
  • E
    2% (1)

Why each option

To validate software functionality against expectations when stakeholders are dissatisfied, the project manager should use a Requirements Traceability Matrix.

AProject status report

A project status report provides an overview of project progress, issues, and risks, but it does not directly validate specific software functionality against requirements.

BRequirements Traceability MatrixCorrect

A Requirements Traceability Matrix (RTM) links requirements to test cases, design elements, and business objectives, allowing the project manager to track whether all defined requirements have been met and tested, thus validating functionality against communicated expectations. It provides a structured way to identify which specific requirements are not being met by the current functionality demonstrated.

CDetect log

A 'Detect log' is not a standard project management tool for validating software functionality against requirements; it sounds like a log for issues or defects.

DSigned project charter

A signed project charter formally authorizes the project and outlines high-level objectives, but it doesn't detail the specific functionality or serve as a tool for validating it.

EWork breakdown structure

A Work Breakdown Structure (WBS) decomposes project deliverables into smaller, manageable work packages, but it doesn't directly validate if the software's functionality meets requirements.

Concept tested: Project requirements management - Requirements Traceability Matrix

Topics

#Project Reporting#Requirements Validation#Stakeholder Management#Project Control

Community Discussion

No community discussion yet for this question.

Full PK0-005 Practice