Role: Analyst
The person in this role represents customer and end-user concerns by gathering input from stakeholders to understand the problem to be solved and by capturing and setting priorities for requirements.
Role Sets: Basic Roles
Relationships

Assess Requirements ConsistencyDetail System-Wide RequirementsDetail Use-Case ScenariosDevelop Technical VisionIdentify and Outline RequirementsManage Changing RequirementsOrganize RequirementsPlan Requirements Management StrategyStructure the Use-Case ModelActorGlossaryRequirements AttributesRequirements Management Process DescriptionRequirements TraceabilityStoryboardSystem-Wide RequirementsUse CaseUse-Case ModelVisionAnalyst

Additionally Performs
Modifies
    Process Usage
    Staffing
    Skills

    An analyst needs the following knowledge, skills, and abilities:

    • Expertise in identifying and understanding problems and opportunities
    • Ability to articulate the needs that are associated with the key problem to be solved or the opportunity to be realized
    • Ability to collaborate effectively with the extended team through collaborative working sessions, workshops, JAD sessions and other techniques.
    • Good communication skills, verbally and in writing
    • Knowledge of the business and technology domains or the ability to quickly absorb and understand such information
    Assignment Approaches

    This role can be assigned in the following ways:

    • One (or more) team member performs this role exclusively. This commonly adopted approach is suitable for complex requirements that are difficult to gather.
    • One (or more) team members performs both this role and tests the software. This is a good option for smaller or resource-constrained test teams.
    • A customer representative performs this role. This approach is suitable to agile teams where the customer is available and is part of the team.