How to define Requirement elicitation actors ie. except Business analyst WHO else can gather requirement, with different elicitation methods, who can participate or gather the requirement from the stakeholder.
Hi @Gaurav Wagh
When it comes to requirement elicitation, a diverse group of actors contribute their expertise to gather, analyze, and refine requirements. While the Business Analyst plays a central role, other key actors include:
- Product Owners, who define product vision and prioritize requirements
- Project Managers, who ensure alignment with project goals and manage stakeholder expectations
- Subject Matter Experts, who provide domain-specific insights
- Developers and Engineers, who identify technical constraints and feasibility
- Quality Assurance Analysts, who ensure testability and suggest improvements
- UX/UI Designers, who gather user-centric requirements and refine user interface needs
- End Users and Customers, who provide firsthand insights into system usage and expectations
- Regulatory and Compliance Officers, who ensure adherence to legal and security standards
- Sales and Marketing Teams, who offer customer feedback and market trends
- Operations and Support Teams, who provide insights on post-deployment issues and maintenance concerns
To elicit requirements, these actors may employ various techniques, including:
- Interviews with stakeholders, SMEs, and end users
- Workshops and brainstorming sessions with cross-functional teams
- Surveys and questionnaires for customers and users
- Observation and job shadowing of end users and support teams
- Prototyping by UX designers and developers
- Focus groups with marketing, sales, and end users
- Use case and scenario analysis by BAs, developers, and UX designers
- Document analysis by compliance and regulatory officers
Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey,
In our case (we are the editor of the Requirement Yogi app) we noticed in 90% of cases in hardware, engineers themselves define the requirements. BAs act at a higher level to choose the product and organize the requirements after they've been defined.
Since you're experts, we've been wondering what were the most used / best softwares used to both write and gather the requirements, and manage them with the whole team. Is Confluence and Jira still accurately used for it? Or is IBM doors still a leader ? What about Jama, and even Google Docs?
Thank you, I hope it doesn't drift too far from the subject :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mileva, Thanks for sharing this unique process as I get to know about this new way of elicitation method
Thanks for you valuable feedback : )
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.