Development Process for Music-Blocks v4

[Karan-Palan]

Development Process for Music-Blocks v4

Following our recent meeting, I’d like to outline the development process we’ll be following for Music-Blocks v4. This will help us stay aligned and ensure smooth progress throughout the project.

1. Epics, Stories, and Tasks

We will break down the project into Epics, which represent large features or major components (ex. palette ). Each Epic will be divided into User Stories focusing on specific functionalities (ex.list/tree view). Finally, each Story will have Tasks representing the granular work needed to complete it.

---

2. Design Documentation

For every major feature:

• Design Document (Design Doc) will cover high-level architecture and workflows.
• Functional Specs will define how the feature should behave from a user’s perspective. reference
• Technical Specs will detail the implementation strategy, APIs, and dependencies.

---

3. MVP and Iterative Development

We’ll focus on developing a Minimum Viable Product (MVP) first, delivering the core functionalities. Post-MVP, we will follow an iterative development approach to continuously improve and add features based on feedback.

---

4. Data Flow Diagrams (DFD)

For each major component, we will:

• Create a DFD to map out the data flow. reference
• Identify functional pieces in the DFD, each becoming a separate User Story.
• Associate one or more tasks with each story to cover development, testing, and review.

---

5. Workflow for Task Management

Tasks will follow this status flow:
To Do → Open → In Progress → In Review → QA → Done

This ensures clarity on the progress of each task and helps us identify bottlenecks early.

---

Meeting notes and Progress documents

Meeting notes - https://docs.google.com/spreadsheets/d/1uvbkgH9TiKyKFptygVBOOJrSO0pm42HuInSJf8IhFMk/edit?usp=sharing

PRD progress - https://docs.google.com/spreadsheets/d/1uvbkgH9TiKyKFptygVBOOJrSO0pm42HuInSJf8IhFMk/edit?usp=sharing

[Ubayed-Bin-Sufian]

Initiative, Epics, Stories, and Tasks

• Stories: Headers, workspace, footer, etc; takes 1 - 2 weeks
• Tasks (technical): skeleton of a header, links, etc.
• Epic: Webpage; takes month --> quarter
• Initiative: multiple quaters --> year

For QA:

1. Tests:
   1. unit tests
   2. integration tests
   3. component tests
   4. end to end (e2e) tests

Points 1-4 focus on planning, design, and documentation without involving coding.
Point 5 involves actual implementation through coding.