Project Management basics - 5.2 Collect Requirements Flashcards
What is the main purpose of the stakeholder register?
a. Identify stakeholders who evaluate the work breakdown structure (WBS).
b. Identify stakeholders who create the stakeholder engagement plan.
b. Identify stakeholders who can provide information on the requirements.
d. Identify decision making stakeholders.
b.Identify stakeholders who can provide information on the requirements. ?
The stakeholder register is used to identify stakeholders who can provide information on the requirements. It also captures requirements and expectations that stakeholders have for the project.
See Section 5.2.1.3 Project Documents
Which of the following requirements describes temporary capabilities needed to move from the current as-is state to the desired future state?
a. Scope requirements
b. Transition and readiness requirements
c. Requirements management plan
d. Quality requirements
b. Transition and readiness requirements ?
Transition and readiness requirements. These describe temporary capabilities, such as data conversion and training requirements, needed to transition from the current as-is state to the desired future state.
See Section 5.2.3.1
What tool or technique is used to obtain information from stakeholders by speaking with them directly?
a. Brainstorming
b. Focus groups
c. Interviews
d. Questionnaires and surveys
c. Interviews
An interview is a formal or informal approach to elicit information from stakeholders by talking to them directly. It is typically performed by asking prepared and spontaneous questions and recording the responses. Interviews are often conducted on an individual basis between an interviewer and interviewee, but may involve multiple interviewers and/or multiple interviewees
See Section 5.2.2.2. Data Gathering
Which of the following describes capabilities that are temporary and are no longer needed after the new product/service/result is ready?
a. Solution requirements
b. Business requirements
c. Quality requirements
d. Transition requirements
d. Transition requirements
Transition and readiness requirements. These describe temporary capabilities, such as data conversion and training requirements, needed to transition from the current as-is state to the desired future state.
See Section 5.2.3.1
You are involved in collecting requirements for your project. You are likely to use the stakeholder register for all of the following EXCEPT:
a. Capturing major requirements that stakeholders may have for the project.
b. Capturing main expectations that stakeholders may have for the project.
c. Identifying stakeholders who can provide information on the requirements.
d. Evaluating the product breakdown structure (PBS) associated with each of the key stakeholders.
d. Evaluating the product breakdown structure (PBS) associated with each of the key stakeholders.
The stakeholder register is used to identify stakeholders who can provide information on the requirements. It also captures requirements and expectations that stakeholders have for the project.
See Section 5.2.1.3 Project Documents
What is the purpose of the Collect Requirements process?
Use the Collect Requirements process to determine, document, and manage stakeholder needs and requirements for meeting objectives.
What is the role of the project manager in the Collect Requirements process?
- Ensure requirements are accounted for in the project management plan.
- Ensure activities for requirements deliver value
- Ensure activities are performed on time and within budget
- Collaborate with business analysts to obtain documents, and manage stakeholder requirements to meet business and project objectives.
Define Requirement:
A Requirement is a condition or capability that should be present in a product, service or result to satisfy its specifications.
Which project assets are considered appropriate inputs(s) for the Collect Requirements process?
- Project Charter
- Project Management Plan
a. Scope Management Plan
b. Requirements Management plan
c. Stakeholder Engagement Plan - Business Documents
- Enterprise Environmental Factors
- Agreements
- Organizational Process Assets
- Project Documents
a. Assumption Log
b. Lessons Learned Register
c. Stakeholder Register
Which project assets are considered appropriate outputs(s) for the Collect Requirements process?
- Requirements Documentation
2. Requirements Traceability Matrix
Which of the following BEST describes the Collect Requirements process?
a. Determining, documenting, and managing sponsor needs and requirements to meet objectives,
b. Determining, documenting, and managing client needs and requirements to meet objectives.
c. Determining, documenting, and managing customer needs and requirements to meet objectives.
d. Determining, documenting, and managing stakeholder needs and requirements to meet objectives.
d. Determining, documenting, and managing stakeholder needs and requirements to meet objectives.
Collect Requirements is the process of determining, documenting, and managing stakeholder needs and requirements to meet objectives.
See Section 5.2 Collect Requirements
Which of the following allows stakeholders to experiment with a model of the final product rather than being limited to discussing abstract representations of their requirements?
a. Critical path
b. Monte Carlo simulation
c. Prototypes
d. Schedule model
c. Prototypes
Prototyping is a method of obtaining early feedback on requirements by providing a model of the expected product before actually building it. Prototypes allow stakeholders to experiment with a model of the final product rather than being limited to discussing abstract representations of their requirements
See Section 5.2.2.8
Which of the following links product requirements from their origin to the deliverables that satisfy them?
a. Work performance data
b. Requirements traceability matrix
c. Configuration management
d. Work Breakdown Structure (WBS)
b. Requirements traceability matrix
Requirements traceability matrix is a grid that links product requirements from their origin to the deliverables that satisfy them. The implementation of a requirements traceability matrix helps ensure that each requirement adds business value by linking it to the business and project objectives. It provides a means to ensure that requirements approved in the requirements documentation are delivered at the end of the project.
See Section 5.2.3.2 Requirements traceability Matrix