Quick Navigation

BUSINESS ANALYSIS#1

The practice of identifying business needs and determining solutions to business problems.

STAKEHOLDER#2

Any individual or group that has an interest in a project or can influence its outcome.

REQUIREMENTS GATHERING#3

The process of collecting and defining what stakeholders need from a project or product.

USE CASE#4

A description of how users will interact with a system to achieve a specific goal.

BUSINESS REQUIREMENTS DOCUMENT (BRD)#5

A formal document outlining the business needs and requirements for a project.

STAKEHOLDER ENGAGEMENT#6

The process of involving stakeholders in decision-making and project execution.

DOCUMENTATION STANDARDS#7

Guidelines that dictate how documentation should be structured and formatted.

INTERVIEW#8

A technique for gathering requirements through direct conversation with stakeholders.

SURVEY#9

A method of collecting data from a group of people using questionnaires.

FOCUS GROUP#10

A gathering of stakeholders to discuss and provide feedback on project requirements.

REQUIREMENTS ANALYSIS#11

The process of assessing gathered requirements for clarity and completeness.

PROTOTYPING#12

Creating a preliminary model of a product to visualize requirements and gather feedback.

SCOPE CREEP#13

The uncontrolled expansion of project scope without adjustments to time, cost, and resources.

FUNCTIONAL REQUIREMENTS#14

Specifications that describe what a system should do.

NON-FUNCTIONAL REQUIREMENTS#15

Specifications that outline how a system performs a function, like security or usability.

STAKEHOLDER MAP#16

A visual representation of stakeholders and their influence on a project.

CHECKLIST#17

A list of items to be verified or completed, often used in requirements gathering.

VISUALIZATION#18

The use of diagrams or charts to represent data and processes clearly.

FEEDBACK LOOP#19

A process where outputs of a system are circled back as inputs, allowing for continuous improvement.

DRAFTING#20

The initial process of writing a document, focusing on content rather than perfection.

PEER REVIEW#21

A process where colleagues evaluate each other's work for quality and accuracy.

FINAL DELIVERABLE#22

The completed project output, such as a BRD, submitted for stakeholder approval.

COMMUNICATION STRATEGY#23

A plan for how information will be shared among stakeholders throughout a project.

ANALYSIS PARALYSIS#24

A situation where overthinking prevents decision-making, often in requirements gathering.

CHANGE MANAGEMENT#25

The process of managing changes to project scope, objectives, and requirements.

RACI MATRIX#26

A tool used to clarify roles and responsibilities in a project.