Courses / Portfolio & Interview Prep
1. Project timeline & task breakdown
Splitting the MVP into discrete tasks with estimated durations and sequencing.
How It Works
Think of the MVP as a recipe: each task is an ingredient or step with a prep time; some steps must wait for previous ones (bake after mix), others can run in parallel (chop veggies while water boils).
List all features and break each into small implementation tasks.
Estimate time for each task — use optimistic, likely, and pessimistic numbers if unsure.
Create dependencies between tasks and find the critical path that determines overall duration.
Schedule parallel tasks to reduce total time and add buffer for risks.
See It
The code computes the critical-path total by recursively finding each task's earliest finish (max of dependency finishes plus its duration) and then taking the maximum. The output shows total hours required assuming serialized dependencies and parallelizable independent tasks. Try changing task C duration to 10 to see how the critical path grows.
Use It
Building the first release of a TODO app with signup, CRUD, and sync.
Breaking work into small, dependent tasks reveals what must be done first, what can run in parallel, and gives a defensible time estimate for the release.
Break It
What will this print?
The naive function sorts tasks by duration and sums all durations regardless of dependencies — so it adds 8+6+2 = 16. The surprise is that summing durations of all tasks is not the same as the critical-path estimate; dependencies allow parallel work and the critical path is the longest dependent chain, not the total sum.
Compute earliest finish times respecting dependencies and return the max finish (critical path) instead of summing sorted durations.
Level Up
Monte Carlo estimates for task durations: run randomized samples across optimistic/likely/pessimistic ranges to produce probability distributions for release date.
Dependency graph visualization: render tasks as a DAG to spot parallelism and bottlenecks, improving scheduling and communication.
Breaking tasks into vertical slices: implement thin end-to-end features (UI → API → DB) to get earlier usable feedback and reduce integration risk.
Prove It
Given a list of tasks with ids, durations and deps, return the critical path length in hours; ignore resource limits (assume perfect parallelism).
JavaScript
Project timeline & task breakdown
Breaking an MVP into sequenced, time-estimated tasks so you can build it predictably and track progress.
"I want to stop guessing how long features take and actually deliver the smallest usable product."
Split the MVP into discrete tasks, give each a duration estimate, and order them by dependency and risk; use those pieces to make a realistic timeline. This helps reveal hidden work, parallelizable tasks, and the minimum deliverable path.
"I want to stop guessing how long features take and actually deliver the smallest usable product."
Split the MVP into discrete tasks, give each a duration estimate, and order them by dependency and risk; use those pieces to make a realistic timeline. This helps reveal hidden work, parallelizable tasks, and the minimum deliverable path.