1. Business Requirements Alignment
Timeframe: 1–3 Days
Step 1: Business Requirement Alignment and Preliminary Analysis
Timeframe: 1–2 days
Purpose:
Meet with stakeholders to identify high-level business goals, assess alignment with strategic priorities, and conduct back-of-the-napkin calculations.
Evaluate initial cost, risk, and benefit to determine if the effort aligns with company priorities and constraints.
Output:
Initial business case with rough calculations to justify further discovery and planning.
Step 2: Business Risk/Cost/Benefit Assessment (Post-PRD)
Timeframe: 1 day
Purpose:
After the PRD is finalized, conduct a more detailed assessment of cost, risks, and benefits using the requirements and LOE estimates.
Provide an updated recommendation to proceed or reevaluate based on feasibility and potential ROI.
Output:
Detailed business case to support the next steps in the process.
2. 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.
...
3. PRD Development
Timeframe:
...
3 - 4 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
1a2:
Figma DesignWireframe Creation
Timeframe:
1-2 weeks3–5 days (overlapping or sequential with Step 1, as needed)
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
Create wireframes to visually represent key workflows, user interactions, and page layouts.
Ensure alignment between product vision, engineering feasibility, and UI/UX requirements.
Output:
- Figma Design ready for review
Wireframes included in the PRD for context and reference during estimation.
- Figma Design ready for review
Step 23: 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.
...
.
Step 4: Timeline and Milestone Planning
Timeframe: 2–3 days
Purpose:
Define a development timeline based on LOE, factoring in dependencies and resource availability.
Incorporate milestones into the PRD.
Output:
Finalized PRD with requirements, wireframes, LOE, timelines, and milestones.
4. 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.
...
5. UX/UI Design (Figma Design)
Timeframe: 1-2 weeks
Purpose:
Use PRD requirements (and possible wireframes) to develop Figma designs and prototypes.
Collaborate with engineering and UI/UX Design team to identify potential challenges, key dependencies, and scope.
Output:
Figma Design ready for review.
...
| Code Block |
|---|
@startgantt ' Business Requirements Alignment Phase [Business Requirements Alignment] lasts 3 days and is colored in #lightgray [Business Requirement Alignment and Preliminary Analysis] lasts 2 days and is colored in #lightgray [Business Requirement Alignment and Preliminary Analysis] -> [Requirements Gathering] ' Requirements Gathering Phase [Requirements Gathering] lasts 12 days and is colored in #lightblue [Stakeholder Alignment] lasts 2 days and is colored in #lightblue and starts at [Requirements Gathering]'s start [Discovery and Research] lasts 10 days and is colored in #lightblue [Stakeholder Alignment] -> [Discovery and Research] ' PRD Development Phase [PRD Development] lasts 16 days and is colored in #lightgreen [Requirements Gathering] -> [PRD Development] [Initial Draft] lasts 5 days and is colored in #lightgreen [Wireframe Creation] 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] -> [Wireframe Creation] [Wireframe Creation] -> [LOE and High-Level Design Review] [LOE and High-Level Design Review] -> [Timeline and Milestone Planning] ' Post-PRD Business Analysis Phase [Post-PRD Business Analysis] lasts 1 day and is colored in #lightgray [Timeline and Milestone Planning] -> [Post-PRD Business Analysis] ' Jira Ticket Creation Phase [Jira Ticket Creation] lasts 3 days and is colored in #lightcoral [Timeline and Milestone Planning] -> [Jira Ticket Creation] ' UX/UI Design Phase [UX/UI Design (Figma Design)] lasts 2 weeks and is colored in #orange [Timeline and Milestone Planning] -> [UX/UI Design (Figma Design)] @endgantt |