SPRINT PLAN

Now we do the most practical - sprint development plan (design + frontend + backend) to go from concept to product. Without an extra theory, this is already a plan on which you can really start.

SPRINT PLAN MVP

Construction Crystal (6–8 weeks)

The General Logic

• Sprint = 1 week
• Total: 6–8 Sprints
• Every week → specific result

SPRINT 1 — Foundation

Objective: Launch basic infrastructure and design system

Design, create a Figma file

• collect:
• Colors
• Typography
• spacing
• do:
• Button
• Input
• Status Badge

Frontend, create a project (Next.js)

• set up:
• Tailwind
• routing
• layout

⚙Backend

• Raise:
• NestJS / FastAPI
• PostgreSQL
• create:
• users
• companies
• projects

Result:

• UI base
• there are API skeleton
• There is BD

SPRINT 2 — Register

Purpose: Earned Register of objects and companies

> Design

• Screen:
• list of projects
• Project Card
• Status:
• loading
• empty

💻 Frontend

• page /projects
• List of objects
• Filters

⚙Backend

• API:
• GET /projects
• POST /projects
• GET /companies

The result: the register is already alive

SPRINT 3 — Graph (core)

Purpose: A graph of links appeared

> Design

• Node (3 type)
• Graph Canvas
• Hover / select

💻 Frontend

• connect:
• Cytoscape.js
• implement:
• nodes
• edges
• zoom

⚙Backend

• Neo4j
• do:
• /projects/{id}/graph

The result: You can see the connections (this is a turning point)

SPRINT 4 — Right panel (control)

Purpose: Management is emerging

> Design

• Entity Panel:
• object
• Company
• Risk

💻 Frontend

• Click on node → panel
• Data display

⚙ Backend

• API:
• GET /projects/{id}
• GET /companies/{id}

The result: The interface becomes manageable

SPRINT 5 — Risks and events

Purpose: The system begins to “think”

> Design

• Risk Node
• Risk List
• status

💻 Frontend

• Risk mapping
• Selection in red

⚙ Backend

• API:
  
• POST /risks
• GET /risks
• PATCH /risks

Result: There is real value

SPRINT 6 — Timeline

Purpose: Add time

> Design

• Timeline
• Status

💻 Frontend

• Slider
• Switching status

⚙ Backend

• events
• project metrics

Results: You can see the dynamics

SPRINT 7 — Analytics (basic)

Purpose: Management at the system level appears

> Design

• dashboard
• KPI

💻 Frontend

• Metric Card

⚙ Backend

• /analytics/dashboard

Result: Can be shown to investors

SPRINT 8 — Polishing

Purpose: to make the product “alive”

Tasks:

• UX improvements
• Graph Optimization
• Bugs
• Authorization
• Roles

? Result: ? MVP is ready

Team (minimum)

• 1 Backend
• 1 Frontend
• 1 Product/Architect(s)
• 1 Designer (part-time)

Critical points 

1. Graph is the heart. If the graph is bad → everything will fall apart

2. Do not overload MVP

None:

• BIM
• Complex Integrations
• “The Lord” immediately

3. UI should be simple

If the user does not understand the 10 seconds → failure

> Checkpoints of success

After the sprint 3: , you can already show (there is a graph)

After the sprint 5: ? already have value (risks)

After the sprint 7: you can raise money

Bottom line. After 6–8 weeks we receive:

• Work product
• Count of the Construction System
• management of objects
• Analytic
• basis for scaling

. . . honest advice. Do not go into endless processing. > Once there is a Graph + UI → show

? TEAM STRUCTURE - MVP

Minimum, but working composition:

The Core

Product / Architect 

Role:

• Product Vision
• priorities
• task setting
• Logic Control

You hold the meaning and the system

Backend Developer. Role:

• API
• database
• Graph (Neo4j)
• Business Logic

Frontend Developer

Role:

• interface
• Graph UI
• integration with API

Designer (UI/UX, part-time)

Role:

• Figma
• Components
• UX

Additional (as it grows)

• DevOps (Infrastructure Configuration)
• QA (Testing)

TASK STRUCTURE (TASK TREE)

We break down not “on screens”, but on system modules.

Models 1: AUTH

Backend:

• Registration
• login
• JWT

Frontend:

• Entry Form

Models 2: REEST

Backend:

• CRUD projects
• CRUD companies
• Communications

Frontend:

• list of projects
• Card

? MODULE 3: GRAPH (KEY)

Backend:

• Neo4j
• graph API
• Synchronization

Frontend:

• Visualization
• interaction

Model 4: ENTITY PANEL

Backend:

• API Details

Frontend:

• right panel
• Switching

Models 5: RISKS

Backend:

• CRUD risks

Frontend:

• display
• Management

Models 6: EVENTS

Backend:

• Events
• log

Frontend:

• timeline

Models 7: ANALYTICS

Backend:

• Units

Frontend:

• dashboard

Task format (very important)

Each task should be designed as follows:

Example of task

🔹 Title:

Show Project Graph

🔹 Description:

Implement mapping of project nodes and links in GraphCanvas

🔹 Acceptance Criteria:

• nodes are displayed:
• project
• company
• risk
• links are displayed
• There is a Zoom
• There is Click

🔹 Tech Notes:

• Cytoscape
• data from /projects/{id}/graph

🔹 Estimate:

2–3 days

Example of a beclog (task top)

The Critical Path MVP

Backend:

• Create tables (projects, companies)
• API projects
• API companies
• Connect Neo4j
• API graph

Frontend:

• Layout
• Project Page
• Graph Canvas
• Node interaction
• Right Panel

Design:

• Design system
• Graph nodes
• Panel

DISTRIBUTION OF ROLES BY TASK

Backend

Total tasks: 👉 ~30

MVP core (required):