Points/Hours System Estimation

Purpose and Scope

This SOP outlines how to estimate development efforts using points (for Bubble/FlutterFlow) or hours (for Glide/Webflow). The goal is to ensure consistent and transparent time estimations, enabling accurate client quotes and project planning.

Client Estimates: Always convert points to hours by applying the appropriate multiplier:

Base multiplier: total points ×2
If task includes both design and QA: total points ×3

Client-facing estimates must always be in hours.

Definitions

Point System: A method to estimate tasks using points (Bubble/FlutterFlow only).

Scale:

1 point = 1–3 hours (less than half a day)
2 points = 4 hours (half a day)
3 points = 8 hours (1 workday)

Client Conversion:

Default: Total points ×2 = Client hours
With design and QA: Total points ×3 = Client hours
(e.g., 3 points with design and QA = 9 client hours)

Development Tasks: Work requiring software creation/modification (front-end, back-end, integration).

PM: Project Manager overseeing timelines and resource allocation.

Procedure

Assess Task Requirements
- Break down tasks into components (front-end, back-end, testing, etc.).
- Flag incomplete scopes or dependencies to the PM.
Assign Dev Points/Ranges

For Bubble/FlutterFlow:
- Assign a point range (e.g., 3–5 points).
- Include testing/QA time in points.
Example:

mathematica

Front-End: 1–2 points Back-End: 1–2 points Testing: 1 point Total: 3–5 points → Client estimate = 6–10 hours (or 9–15 hours if includes design and QA)

For Glide/Webflow: Estimate directly in hours (no points).

Always: Overestimate rather than underestimate.
Add Estimates to Task
- Input points/hours in the task’s custom field.
- For Points: Add a comment with the client hour conversion (e.g., “3–5 points = 6–10 client hours” or “3–5 points = 9–15 client hours (includes design + QA)”).
Tag the PM
- Notify the PM in the task comments (e.g., “@PM – Dev points added: 3–5 points (9–15 client hours including design + QA)”).

Example Scenario

Task: Build a user dashboard (Bubble).

Estimates:

Front-End: 2–3 points
Back-End: 1–2 points
Testing: 1 point
Total Points: 4–6

Client Hours:

Default: 8–12 hours
With Design + QA: 12–18 hours

Communication:
“@PM – Dashboard task: 4–6 points (12–18 client hours including design + QA). Testing included.”

Best Practices

Transparent Client Communication:

Never share internal points with clients—always use hours.
Explain hourly ranges to clients (e.g., “This feature will take 12–18 hours”).

Collaboration:

Discuss uncertainties with the PM before finalizing estimates.

Documentation:

Record assumptions (e.g., “Testing assumes no major back-end bugs”).

Key Considerations

Double-Check Multipliers: Ensure the right multiplier (×2 or ×3) is used for client hours.
Buffer for Complexity: Add 10–20% extra hours for ambiguous tasks.
Feedback Loop: Review past estimates to improve accuracy.