Where did an owner's 65-day guess go wrong? MT246's Unit 3 exercise re-estimates a food truck launch activity by activity and shows where each phase gap opened. Searches like "mt 246 unit 3 assignment example", "mt246 unit 3 sample" and "mt246 unit 3 example" land here.
What a finished MT246 Unit 3 estimating exercise looks like
Three parts over five pages. An estimate table lists twenty-two activities, each carrying its breakdown code, a working-day figure, the method and its basis. Most rest on a quote, a published processing time or the pitmaster's own records; two outside-party durations use three points. Plan review is 10, 14 and 24 days, weighted to 15 with a standard deviation near 2.3, and the upfit is 24, 30 and 36, weighted to 30. The city license comes from the clerk's issue log, ten working days after the health permit. The owner's four phase guesses then sit beside task-built figures for the same phases: truck build 30 against 42, permits 15 against 30, menu and crew 15 against 18, launch 5 against 9. An assumptions list closes the exercise.
How a MT246 Unit 3 example is structured
Estimates are made at the level where someone could be asked, so each activity carries the name of the person or firm whose number it is. The method column changes with the evidence: a written quote where a firm has committed, a published processing time where an office posts one, low, likely and high values where another organization's queue sets the pace, and recipe trials for menu testing. Phase against task is where the argument lives. Each phase gap is explained by activities the guess never pictured: layout drawings and generator work in truck build, the fire marshal and the city license in permits, a first smoke and a soft launch in launch. The phase figures are never added into a project total, since phases overlap, and a note leaves the combined length to the next unit's network. Reserve stays out of every row.
Whose number each row is
The upfitter's quote, the health department's posted review time, the city clerk's issue log, the pitmaster's trial batches: each duration names the person or record it came from.
Three points for two queues
Plan review and the upfit build depend on other people's backlogs, so both carry low, likely and high values weighted toward the middle, with the spread printed beside the mean.
Four phases, re-estimated
Truck build at 42 working days against a 30-day guess, permits 30 against 15, menu and crew 18 against 15, launch 9 against 5, each figure drawn from the activities inside it.
Work the phases hid
Layout drawings before any build, a generator after it, the fire marshal ahead of the health inspector, a city license after both, and two private services before anyone pays.
No total, on purpose
The phase figures are not summed, because a menu can be tested while the truck is built; a closing note leaves the combined length to the network drawn next.
Where marks go in MT246 Unit 3
Graders test an estimate by asking where it came from, so a duration column with no named source leaves them nothing to check and is marked down accordingly. Estimating at phase level while calling the result bottom-up is the typical miss in this unit; a phase has no single person who could be asked how long it takes. Three-point rows that report a plain average while calling it PERT draw technical comments, and so does a weighted mean shown without its spread. Summing phase figures into a project length, as though phases never overlap, is a quiet error the network later exposes. Effort confused with duration, forty hours entered as forty days, still turns up regularly. Padding tucked into individual rows reads as hidden uncertainty. Missing assumptions, and one method applied to every row regardless of evidence, cost smaller amounts.
Get a MT246 Unit 3 example written to your instructions
Is there a phase-level figure in your scenario that needs testing? Pass along the Unit 2 breakdown, whatever quotes, processing times or rates the case supplies, the Unit 3 prompt and rubric, and any method the course names. Expect the first exercise in 24-48h without charge, every duration traced to a source.
MT246 Unit 3 questions, answered
Why estimate activities instead of phases?
Because an activity has someone who can be asked how long it takes and a basis they can show, while a phase blends several kinds of work under one number. In the example, the permits phase hid four approvals, from three offices, arriving one after another. Estimating each activity on its own exposed a thirty-day chain the phase guess had squeezed into fifteen.
When is a three-point estimate worth using?
When the outcome depends on something the project does not control, such as a review queue or a contractor's backlog, and a single figure would hide how wide the uncertainty runs. The example uses three points on only two rows for that reason. The other rows rest on quotes or records, which carry less doubt and do not need the extra arithmetic.
Can the phase figures be added up to get the project length?
Usually not, and the example says so. Phases overlap: the menu can be tested while the truck is being built, and hiring can run alongside permits. Adding phase durations assumes each waits for the one before it, which overstates the length. The network built in the next unit works out how much of the work actually runs in parallel.