Requirements Gathering

Effectively gather requirements using proven elicitation techniques to ensure comprehensive understanding of business needs and user expectations.

When to Use This Skill

• Starting new projects
• Defining system requirements
• Understanding user needs
• Gathering stakeholder input
• Exploring solution options
• Validating assumptions
• Capturing business rules
• Documenting constraints

Core Techniques

1. Stakeholder Interviews

Preparation:

• Identify key stakeholders
• Research background
• Prepare questions
• Schedule adequate time
• Choose appropriate setting

Interview Questions:

## Opening Questions
- What are your main goals for this project?
- What problems are you trying to solve?
- Who will use this system?

## Detail Questions
- Can you walk me through your current process?
- What are the pain points?
- What would an ideal solution look like?
- What constraints do we need to consider?

## Closing Questions
- What success looks like?
- Any other requirements or concerns?
- Who else should I talk to?

2. Requirements Workshop

Workshop Agenda (4 hours):

1. Introduction & Objectives (30 min)
   - Project overview
   - Workshop goals
   - Ground rules

2. Current State Analysis (60 min)
   - AS-IS process walkthrough
   - Pain points identification
   - Brainstorming session

3. Future State Design (90 min)
   - TO-BE process design
   - Requirements capture
   - Feature prioritization

4. Review & Next Steps (40 min)
   - Requirements summary
   - Action items
   - Follow-up plan

3. Document Analysis

Documents to Review:

• Existing system documentation
• Process manuals
• Business policies
• User guides
• Support tickets
• Analytics reports
• Compliance documents
• Competitive analysis

4. Observation & Job Shadowing

Observation Checklist:

• Understand actual vs documented process
• Identify workarounds
• Note inefficiencies
• Observe user behavior
• Capture environment context
• Document exceptions
• Measure time and effort

Best Practices

1. Prepare thoroughly – Research and plan
2. Ask open-ended questions – Encourage detailed responses
3. Listen actively – Focus on understanding
4. Document immediately – Capture while fresh
5. Validate understanding – Confirm with stakeholders
6. Use multiple techniques – Triangulate requirements
7. Follow up – Clarify ambiguities
8. Prioritize early – Understand what’s critical

Resources

• BABOK Guide: Requirements elicitation techniques
• Software Requirements by Karl Wiegers