Requirement to software Delivery in midsize comp CHEATSHEET

Source: Dev.to

Process Overview

In a modern mid‑size startup (≈ 50–200 employees), the software development process balances the speed of a small team with the predictability required by investors and stakeholders. The workflow follows a Discovery → Planning → Execution loop rather than ad‑hoc coding.

Phases

Initiation

• Triggered by data, customer feedback, or strategic goals.
• Catalysts: Product Management (user feedback/analytics), Leadership (strategic pivot), or Sales/Customer Success (high‑value client requests).

Discovery Phase

• A Discovery squad (Product Manager, Lead Designer, Tech Lead) validates the idea before any code is written.
• Activities: user interviews, technical feasibility spikes.
• Key output: Product Requirements Document (PRD) – a living document (e.g., Notion, Confluence) containing problem statement, target user, user stories, success metrics (KPIs), and out‑of‑scope items.

Planning

• Designers receive the PRD, analyze requirements, and produce high‑fidelity mockups (usually in Figma).
• The Tech Lead discusses the PRD and UI mockups with engineers, identifies edge cases, and drafts a Technical Design Document (RFC/TDD) covering system architecture, database changes, API designs, metric‑gathering plan, and release plan.
• The design is peer‑reviewed across the engineering team.

Backlog Grooming

• Product Manager and Engineering Lead break the PRD into tickets (tasks) in a tool like Jira.
• Each ticket receives Story Points for effort estimation.
• Teams typically use Scrum or Kanban with 2‑week sprints.

Execution

• Development proceeds in sprints: coding, pull‑request reviews, continuous integration/deployment.
• Daily stand‑ups (≈ 15 min) keep the team aligned.

QA / UAT

• Automated tests run continuously.
• Stakeholders perform User Acceptance Testing on a release candidate.

Launch

• Features are released behind feature flags for phased rollout.
• A “dark launch” (code deployed but hidden) precedes full release.

Supporting Practices

• Asynchronous Documentation: All decisions and updates are written down for asynchronous consumption.
• Product Roadmap: High‑level quarterly timeline (Now, Next, Later).
• RACI Matrix: Defines who is Responsible, Accountable, Consulted, and Informed.
• SLAs: Document expected uptime and performance for the new feature.

Tooling

• Project Tracking: Linear, Jira, Asana
• Documentation: Notion, Confluence, GitHub Wiki
• Design: Figma
• Communication: Slack (integrated with GitHub/Jira)

Example Timeline for a Medium‑Sized Feature (e.g., new dashboard)

Post‑Launch Activities

• User Feedback & Analytics: Monitor tools like Amplitude, Mixpanel, Google Analytics to assess impact against PRD goals.
• Observability & Monitoring
• Feature Flag Cleanup
• Technical Debt Management (e.g., “Nothing is more permanent than a temporary solution”)
• Performance Tuning

Post‑Launch Review (formal meeting 1–2 weeks after launch)