Specific qualifications and criteria that must be met for a product, user story, or increment to be considered complete. It’s a three-word description, but the acronym is used here.
This diagram illustrates the relationships among elements in an environment, such as networks, servers, workstations, and people interacting with these elements.
The smallest element in the Work Breakdown Structure (WBS). (Two words)
A user story sizing method that compares stories to predefined sizes (e.g., extra small to extra large). Somethng you might wear on the weekends. (No hyphen)
Unapproved changes to the project scope. (Two words)
A technique for visually organizing and representing project requirements to identify relationships and prioritize them(Two words)
The study and analysis of a system, its components, and their relationships. (Two words)
A method led by a moderator to gather project requirements by engaging stakeholders in discussions and idea generation. (Two words)
A decision-making method where a single individual makes decisions on behalf of the group without consulting others.
These diagrams are used to group similar ideas or concepts together.
Clearly defines what’s included and excluded from the project scope to eliminate misunderstandings.
A decision-making method where everyone must agree.
This is a study of a system’s functions, goals, usage, and customer expectations, considering both the product’s creation and operational cost.
The number of user story points a development team can complete during a sprint, aiding project duration predictions.