R
The role in Scrum is accountable for maximizing the value of a product, primarily by incrementally managing and expressing business and functional expectations for a product to the Development Team(s).
Refinement
see #Product Backlog Refinement
RACI matrix
See the responsible, accountable, consulted, and informed matrix.
Regulator
A stakeholder from outside the organization is responsible for defining and enforcing standards.
Repository
A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Request for information (RFI)
A formal elicitation method intended to collect information regarding a vendor’s capabilities or any other information relevant to a potential upcoming procurement.
Request for proposal (RFP)
A requirements document is issued when an organization seeks a formal proposal from vendors. An RFP typically requires that the proposals be submitted following a specific process and using sealed bids, which will be evaluated against a formal evaluation methodology.
Request for quote (RFQ)
A procurement method of soliciting price and solution options from vendors.
Request for tender (RFT)
An open invitation to vendors to submit a proposal for goods or services.
Requirement
A usable representation of a need.
Requirements allocation
The process of assigning requirements to be implemented by specific solution components.
Requirements allocation
The process of assigning requirements to be implemented by specific solution components.
Requirements architecture
The requirements of an initiative and the interrelationships between these requirements.
Requirements artifact
A business analysis artifact containing information about requirements such as a diagram, matrix, document, or model.
Requirements attribute
A characteristic or property of a requirement used to assist with requirements management.
Requirements defect
A problem or error in a requirement. Defects may occur because a requirement is poor quality (see requirements verification) or because it does not describe a need that, if met, would provide value to stakeholders (see requirements validation)
Requirements document
See the requirements package.
Requirements life cycle
The stages through which a requirement progresses from inception to retirement.
Requirements management
Planning, executing, monitoring, and controlling any or all of the work associated with requirements elicitation and collaboration, requirements analysis and design, and requirements life cycle management.
Requirements management plan
A subset of the business analysis plan for a specific change initiative, describing specific tools, activities, and roles and responsibilities that will be used on the initiative to manage the requirements. See the business analysis plan.
Requirements management tool
Special-purpose software that supports any combination of the following capabilities: elicitation and collaboration, requirements modelling and/or specification, requirements traceability, versioning and baselining, attribute definition for tracking and monitoring, document generation, and requirements change control.
Requirements model
An abstract (usually graphical) representation of some aspect of the current or future state.
Requirements package
A specialized form of a business analysis package primarily concerned with requirements. A requirements package may represent a baseline of a collection of requirements.
Requirements traceability
The ability to track the relationships between sets of requirements and designs from the original stakeholder is needed for the actual implemented solution. Traceability supports change control by ensuring that the source of a requirement or design can be identified and that other related requirements and designs potentially affected by a change are known.
Requirements validation
Work is done to evaluate requirements to ensure they support the delivery of the expected benefits and are within the solution scope.
Requirements verification
Work is done to evaluate requirements to ensure they are defined correctly and at an acceptable quality level. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the solution's design, development, and implementation.
Requirements workshop
A structured meeting in which a carefully selected group of stakeholders collaborate to define and/or refine requirements under the guidance of a skilled neutral facilitator.
Residual risk
The risk remains after an action or plan has been implemented to deal with the original risk.
Responsible, accountable, consulted, and informed matrix (RACI matrix)
A tool used to identify the responsibilities of roles or team members and the activities or deliverables in which they will participate by being responsible (doing the work), accountable (approving the results), consulted (providing input), or informed of the completed item after it has been completed.
Retrospective
See lessons learned process.
Return on investment (ROI) (business analysis)
A measure of the profitability of a project or investment.
RFI
See the request for information.
RFP
See the request for the proposal.
RFQ
See the quote request.
RFT
See the request for tender.
Risk (business analysis)
The effect of uncertainty on the value of a change, a solution, or the enterprise. See also residual risk.
Risk assessment
Identifying, analyzing, and evaluating risks.
ROI
See return on investment.
Root cause
The cause of a problem having no deeper cause, usually one of several possible causes.
Root cause analysis
A structured examination of an identified problem to understand the underlying causes.
Last updated