Elicitation Activity Plan

Captures stakeholders, selected techniques, supporting materials, activity, logistics, and sources of background information for the planned elicitation.

The Elicitation Activity Plan receives input from Business Needs and the Stakeholder Engagement Approach. It provides input to Elicitation Results.

Details

An Elicitation Activity Plan contains 6 attributes and 1 task.

  • Elicitation Activity ID: This attribute identifies the planned elicitation for the project.

  • Understand the Scope of Elicitation - Defines the scope of this elicitation plan in terms of its goals and stakeholders who contribute to those goals.

  • Select Elicitation Techniques – For each technique described in the task Prepare For Elicitation, describe the purpose of each technique used in this elicitation activity.

  • Set Up Logistics – Describe the how resources are acquired and setup during elicitation.

  • Secure Supporting Material – Provide information on how to access supporting material used during elicitation.

  • Prepare Stakeholders – Provide a list of instructions for each stakeholder, including dates, times places and what to expect during elicitation.

  • Prepare For Elicitation - This task generates an elicitation activity plan.

Example

Software Development Elicitation Activity Plan

Objective:

To collect, analyze, and refine functional and non-functional requirements to ensure the successful development of a software solution.

Participants:

  • Product owners

  • Software developers

  • UX/UI designers

  • Business analysts

  • End users

  • Stakeholders (internal and external)

Activities:

  1. Stakeholder Interviews

    • Purpose: Understand business goals, technical constraints, and feature expectations.

    • Method: One-on-one or group discussions with key stakeholders.

    • Expected Outcome: Clear documentation of critical software requirements and priorities.

  2. User Story Workshops

    • Purpose: Define requirements from an end-user perspective.

    • Method: Conduct workshops where stakeholders and developers collaborate to create user stories.

    • Expected Outcome: Well-defined user stories with acceptance criteria.

  3. Surveys & Questionnaires

    • Purpose: Gather feedback from potential users and clients.

    • Method: Distribute surveys to collect insights on software usability, features, and pain points.

    • Expected Outcome: Prioritized list of user needs and preferences.

  4. Observation & Shadowing

    • Purpose: Understand how users interact with existing systems or workflows.

    • Method: Observe users working with current software to identify issues and gaps.

    • Expected Outcome: Improved understanding of usability challenges and process inefficiencies.

  5. Prototyping & Wireframe Reviews

    • Purpose: Validate design and functionality before development begins.

    • Method: Create early UI mockups or wireframes and gather feedback.

    • Expected Outcome: Refined UI/UX elements and confirmation of user expectations.

  6. Competitive Analysis

    • Purpose: Assess features of similar products in the market.

    • Method: Research competitor software to identify industry standards and opportunities for differentiation.

    • Expected Outcome: Enhanced product strategy and innovation.

  7. Proof of Concept (PoC) or Minimum Viable Product (MVP) Testing

    • Purpose: Validate core functionalities before full-scale development.

    • Method: Develop a small-scale prototype and test with stakeholders.

    • Expected Outcome: Early feedback to refine features and usability before full development.

Timeline:

  • Week 1-2: Conduct stakeholder interviews and surveys.

  • Week 3: Host user story workshops and shadowing sessions.

  • Week 4-5: Develop wireframes and conduct reviews.

  • Week 6: Perform PoC/MVP testing with stakeholders.

Success Metrics:

  • Clarity and completeness of user stories

  • Stakeholder satisfaction with elicited requirements

  • Usability and feasibility of proposed designs

  • Number of validated features included in the final product

Header

Paragraph

Heading 3

Paragraph 1

Heading 4

Paragraph 2

Heading 5

Paragraph 3

Artifact Title

Artifact Overview

Artifact Title

Artifact Overview