Requirements Elicitation - Typical Engagement

Article Index Requirements Elicitation Typical Engagement Engagement Types and Options Facilitating a Requirements Discovery Session Why Use IAG? All Pages Page 2 of 5 Typical Engagement Typical Duration: 1-4 weeks on average Typical Resources: 1 Requirements Consulting Team Typical Format: Day 1: Project/Product Scoping Session with main Stakeholders (10AM-3PM) Analysis and Documentation of Scope and High Level Requirements Requirements Planning Days 2-4: Requirements Discovery Sessions (9AM-3PM) Requirements Analysis and Documentation (3-5PM) Day 5: Requirements Review, Analysis and Verification Days 6-9: Requirements Discovery Sessions (9AM-3PM) Requirements Analysis and Documentation (3-5PM) Day 10: Requirements Review, Validation and Prioritization Typical Work Products: (Various models, templates and tools may be used – based on client needs) • Typical Mid-level Requirements Document including: • Definition of Scope and Objectives • Use Cases • Context Diagram • Conceptual Data Model • Process Models (typically on engagements 3 weeks or longer) • Data Definitions << Prev - Next >>