Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

1. Requirement Gathering Process

Timeframe: 1.25 - 2.25 Weeks

  • Step 1: Stakeholder Alignment

    • Timeframe: 1–2 days

    • Purpose:

      • Meet with stakeholders (product, engineering, integrations) to understand high-level goals and prioritize features.

    • Output:

      • Initial list of requirements, prioritized based on impact and feasibility.

  • Step 2: Discovery and Research

    • Timeframe: 1–2 weeks (depending on complexity)

    • Purpose:

      • Conduct research, gather input, analyze existing data, and review constraints.

    • Output:

      • Refined list of requirements with supporting data, initial technical considerations, and key dependencies identified.

2. PRD Development

Timeframe: 1–2 weeks

  • Step 1: Initial Draft

    • Timeframe: 1 week

    • Purpose:

      • Write the initial PRD with high-level requirements and user stories.

      • Collaborate with engineering to identify potential challenges, key dependencies, and scope.

    • Output:

      • Draft PRD ready for review.

    • Step 1a: Figma Design

      • Timeframe: 1-2 weeks

      • Purpose:

        • Use written requirements (and possible wireframes to develop initial Figma Design

        • Collaborate with engineering and UI/UX Design team to identify potential challenges, key dependencies, and scope.

      • Output:

        • Figma Design ready for review.

  • Step 2: LOE and High-Level Design Review

    • Timeframe: 1–1.5 weeks

    • Purpose:

      • Collaborate with engineering to refine requirements.

      • Create a high-level design and task breakdown.

      • Estimate the Level of Effort (LOE) for development, integration, and testing.

    • Output:

      • Updated PRD with detailed LOE estimates, risks, and dependencies.

      • High-level design and task breakdown.

3. Jira Ticket Creation and Task Breakdown

Timeframe: 1–3 Days

  • Purpose:

    • Engineering creates Jira tickets based on PRD requirements and the implementation plan.

    • Ensure tasks are actionable and aligned with the roadmap and PRD deliverables.

  • Output:

    • Jira tickets with clear requirements, task ownership, and dependencies, ready for sprint planning and execution.

Requirements Planning Framework (1).png

@startgantt

[Requirements Gathering] lasts 12 days and is colored in #lightblue
[Stakeholder Alignment] lasts 2 days and is colored in #lightblue
[Discovery and Research] lasts 10 days and is colored in #lightblue
[Stakeholder Alignment] -> [Discovery and Research]

[PRD Development] lasts 16 days and is colored in #lightgreen
[Requirements Gathering]-> [PRD Development]
[Initial Draft] lasts 5 days and is colored in #lightgreen
[LOE and High-Level Design Review] lasts 8 days and is colored in #lightgreen
[Timeline and Milestone Planning] lasts 3 days and is colored in #lightgreen
[Discovery and Research] -> [Initial Draft]
[Initial Draft] -> [LOE and High-Level Design Review]
[LOE and High-Level Design Review] -> [Timeline and Milestone Planning]

[Jira Ticket Creation] lasts 3 days and is colored in #lightcoral
[Timeline and Milestone Planning] -> [Jira Ticket Creation]

@endgantt

https://UCFNextgen.ai/public/plantuml/1055

  • No labels