When gathering business information requirements, you should focus only on the requirements provided by the business groups.
-
True
-
False
When gathering requirements, focusing ONLY on business groups is insufficient. You must also consider technical requirements (performance, scalability, security), data quality needs, integration requirements with other systems, and stakeholder needs from IT, compliance, and operations. A comprehensive requirements-gathering process involves all relevant stakeholders, not just business users.
Good requirements-gathering practice means consulting all relevant stakeholders — end users, subject-matter experts, technical teams, compliance/legal, and management — not just the business groups requesting the change. Focusing only on business-group input risks missing technical constraints, usability needs, regulatory requirements, or conflicting priorities from other stakeholders, leading to incomplete or unworkable requirements. So the statement is False: you should broaden requirements gathering beyond a single source. 'True' would encode a known anti-pattern in business analysis, not the recommended practice.