Project Workback — Full Document

← Back to walkthrough

Project Workback Schedule #

Planning a product launch with a fixed deadline. Uses CalcMark’s date arithmetic and compound durations.

Key Dates #

launch_date = Mar 15 2025 → Saturday, March 15, 2025
kickoff = today → Saturday, March 14, 2026

Days until launch:

days_to_launch = launch_date - kickoff → 364 days

Phase Durations #

Using compound duration syntax:

development_time = 4 weeks → 4 week
qa_time = 2 weeks → 2 week
staging_time = 1 week → 1 week
launch_prep = 5 days → 5 day

Total planned time:

total_planned = development_time + qa_time + staging_time + launch_prep → 7.71 week

Buffer Calculation #

buffer = days_to_launch - total_planned → 310 days

Working Backwards from Launch #

Using date arithmetic to calculate milestone dates:

launch_prep_start = launch_date - launch_prep → Monday, March 10, 2025
staging_start = launch_prep_start - staging_time → Monday, March 3, 2025
qa_start = staging_start - qa_time → Monday, February 17, 2025
dev_start = qa_start - development_time → Monday, January 20, 2025

Sprint Planning #

Assuming 2-week sprints during development (4 weeks = 2 sprints):

num_sprints = 2 → 2
sprint_duration = 2 weeks → 2 week

Points per sprint (team velocity):

team_velocity = 40 → 40
total_points = num_sprints * team_velocity → 80

Key Milestones #

Using “X from Y” syntax (works with date literals):

one_week_from_now = 1 week from today → Saturday, March 21, 2026
two_weeks_from_now = 2 weeks from today → Saturday, March 28, 2026
next_month = 1 month from today → Monday, April 13, 2026

Milestone dates calculated from schedule:

design_review = dev_start + 1 week → Monday, January 27, 2025
first_sprint_end = dev_start + 2 weeks → Monday, February 3, 2025
feature_freeze = dev_start + 3 weeks → Monday, February 10, 2025
code_complete = qa_start → Monday, February 17, 2025

Resource Allocation #

developers = 4 → 4
qa_engineers = 2 → 2
devops = 1 → 1

Person-weeks calculation (4 weeks dev, 2 weeks QA, ~2 weeks devops):

dev_person_weeks = developers * 4 → 16
qa_person_weeks = qa_engineers * 2 → 4
devops_person_weeks = devops * 2 → 2

total_person_weeks = dev_person_weeks + qa_person_weeks + devops_person_weeks → 22

Risk Assessment #

Add contingency for unknowns (~15% buffer = 8 days):

risk_buffer = 8 days → 8 day
adjusted_dev_start = dev_start - risk_buffer → Sunday, January 12, 2025

Daily Rate Cost Estimate #

Using rate syntax for daily costs:

dev_daily_rate = $800/day → 800 $/day
qa_daily_rate = $700/day → 700 $/day
devops_daily_rate = $900/day → 900 $/day

Team cost over development phase:

dev_cost = dev_daily_rate * developers over development_time → $89.6K
qa_cost = qa_daily_rate * qa_engineers over qa_time → $19.6K
devops_cost = devops_daily_rate * devops over (staging_time + launch_prep) → $10.8K

Calendar Summary #

Key dates for your calendar:

project_kickoff = adjusted_dev_start → Sunday, January 12, 2025
dev_complete = qa_start → Monday, February 17, 2025
qa_complete = staging_start → Monday, March 3, 2025
staging_complete = launch_prep_start → Monday, March 10, 2025
go_live = launch_date → Saturday, March 15, 2025

Schedule Feasibility #

Time comparison:

available_time = days_to_launch → 364 days
needed_time = total_planned + risk_buffer → 8.86 week

The team needs 8.86 week but has 364 days until launch. Development kicks off Sunday, January 12, 2025 with a risk buffer of 8 day. Total cost across all phases: roughly $89.6K (dev) + $19.6K (QA) + $10.8K (devops).