EMSE 6035 Project Tracker
  • Home
  • Project
  • Schedule
  • Critical path
  • Tracker
    • Activities
    • Requirements
    • Risks
    • Week by week
  • Dev log
  • Context bank

Critical path

The chain of activities that cannot slip without moving a deliverable, computed on every render

The project is a strict pipeline: each deliverable is the input to the next, and the final survey has to be in the field over Thanksgiving before any final analysis can happen. Because every submission date is a hard constraint, the critical path is not one long chain but a series of zero-float segments, one per deliverable, joined by the handoffs between them. Today 29 open activities carry zero float, 8 carry one to three days, and 4 have more room than that.

The chain

Only the critical path

The same Gantt as the schedule page, filtered to the open activities with zero float. Hover for early and late dates; click a row to see what feeds it and what waits on it.

Float on every open activity

Early start and finish come from the forward pass; late start and finish from the backward pass off the official deadlines. Total float is the gap between them. Free float is how far the activity can slip before it delays its immediate successor rather than a deadline.

ID Phase Activity Early Late Deadline Total float Free float Feeds into Status
P05 Proposal Proposal workshop meeting with the professor (remote, week 4) Sep 16 to Sep 18 Sep 16 to Sep 18 0 d 0 d P07 Not started
P06 Proposal Revise to v2: remove AI paste artifacts, fix cross-ref and heading levels, add references, benchmark real competitors with prices, quantify the retrofit market, rework price levels, argue the fit Sep 16 to Sep 18 Sep 16 to Sep 18 0 d 0 d P07 In progress
P07 Proposal Move the proposal into the official repo (1-proposal/proposal.qmd, image in images/), apply the workshop feedback, render, spell-check Sep 19 to Sep 19 Sep 19 to Sep 19 0 d 0 d P08 Not started
P08 Proposal Final read-through by a second member, commit and push the proposal Sep 20 to Sep 20 Sep 20 to Sep 20 Sep 20 0 d 0 d SP01, SP02 Not started
SP01 Survey plan Lock the attribute list and levels after the workshop: units, price levels with a base-rent anchor, one-line level definitions Sep 21 to Sep 23 Sep 21 to Sep 23 0 d 0 d SP03 Not started
SP03 Survey plan Choice question text, the attributes-and-levels table with units, and the design parameters (alternatives per question, questions per respondent, no-choice option) Sep 24 to Sep 26 Sep 24 to Sep 26 0 d 0 d SP04, PS02 Not started
SP04 Survey plan Survey content as exact text: welcome, consent (18 plus, 'I have read and understand'), education per attribute, respondent info, other questions Sep 27 to Sep 28 Sep 27 to Sep 28 0 d 0 d SP05, PS03 Not started
SP05 Survey plan Assemble survey_plan.qmd, render, spell-check, commit and push Sep 29 to Sep 29 Sep 29 to Sep 29 Sep 29 0 d 0 d SP06, PS01 Not started
PS01 Pilot survey Learn the surveydown conjoint-buttons template; run the sample app locally Sep 30 to Oct 3 Sep 30 to Oct 3 0 d 0 d PS02, PS03 Not started
PS03 Pilot survey Build survey.qmd from the plan text: welcome, consent, screening, education (with images/), conjoint block, other questions; render it and run app.R locally Oct 4 to Oct 8 Oct 4 to Oct 8 0 d 0 d PS04 Not started
PS04 Pilot survey Connect the Supabase project and confirm responses are stored Oct 9 to Oct 10 Oct 9 to Oct 10 0 d 0 d PS05 Not started
PS05 Pilot survey Deploy to shinyapps.io; end-to-end test on a phone and a laptop; screenshot an example choice question for the reports Oct 11 to Oct 12 Oct 11 to Oct 12 0 d 0 d PS07 Not started
PS07 Pilot survey Push the pilot survey folder and confirm the live link Oct 13 to Oct 13 Oct 13 to Oct 13 Oct 13 0 d 7 d PA01 Not started
PA01 Pilot analysis Classmates take our pilot; we take theirs and fill the feedback sheet (part of HW8) Oct 21 to Oct 24 Oct 21 to Oct 24 0 d 0 d PA02, PA05 Not started
PA02 Pilot analysis Download with sd_get_data(); save raw data; clean-data.R to long format Oct 25 to Oct 26 Oct 25 to Oct 26 0 d 0 d PA03 Not started
PA03 Pilot analysis modeling.R: preliminary logit, coefficient table with standard errors, coefficient plots, utility model in LaTeX Oct 27 to Oct 28 Oct 27 to Oct 28 0 d 0 d PA04, PA06 Not started
PA04 Pilot analysis power-analysis.R: standard errors against sample size; choose the final sample size Oct 29 to Oct 29 Oct 29 to Oct 29 0 d 0 d PA06 Not started
PA06 Pilot analysis report.qmd: abstract, intro, survey design (eligibility, education, attributes justified, alternatives and questions per respondent, no-choice, example question), sample, cleaning counts, modeling, power analysis, changes, appendix Oct 30 to Oct 31 Oct 30 to Oct 31 0 d 0 d PA07 Not started
PA07 Pilot analysis Render, spell-check, commit and push the pilot analysis Nov 1 to Nov 1 Nov 1 to Nov 1 Nov 1 0 d 0 d FS01, FA01, FA07 Not started
FS04 Final survey Fielding on Prolific, arranged through the professor; monitor responses daily Nov 17 to Nov 27 Nov 17 to Nov 27 0 d 0 d FA02 Not started
FA02 Final analysis Clean the final data; sample description table Nov 28 to Nov 29 Nov 28 to Nov 29 0 d 0 d FA03 Not started
FA03 Final analysis Run the models on the final data: logit, mixed logit, sub-group comparison Nov 30 to Dec 1 Nov 30 to Dec 1 0 d 0 d FA04 Not started
FA04 Final analysis analysis.R: WTP, market simulation against competitors, price and attribute sensitivity, tornado plot Dec 2 to Dec 3 Dec 2 to Dec 3 0 d 0 d FA05, PR01 Not started
FA05 Final analysis report.qmd as narrative: abstract, intro with visuals, survey design with the changes from the pilot, data analysis, results, recommendations and conclusions, limitations, attribution, appendix; fully reproducible Dec 4 to Dec 5 Dec 4 to Dec 5 0 d 0 d FA06 Not started
PR01 Presentation Build the slides: product intro, example choice question, sample stats, utility model, WTP, simulation with its attribute table, sensitivity, recommendations Dec 4 to Dec 6 Dec 4 to Dec 6 0 d 0 d PR02 Not started
FA06 Final analysis Render, spell-check, commit and push the final report Dec 6 to Dec 6 Dec 6 to Dec 6 Dec 6 0 d Not started
PR02 Presentation Rehearse to ten minutes with every member presenting at least one slide Dec 7 to Dec 7 Dec 7 to Dec 7 0 d 0 d PR03 Not started
PR03 Presentation Push the slides to the official repo Dec 8 to Dec 8 Dec 8 to Dec 8 Dec 8 0 d 0 d PR04 Not started
PR04 Presentation Present in class (or send the video link by Slack DM) Dec 9 to Dec 9 Dec 9 to Dec 9 Dec 9 0 d Not started
S04 Setup Everyone accepts the official team repo invitation and clones it Sep 10 to Sep 18 Sep 11 to Sep 19 1 d 1 d P08 In progress
FS01 Final survey Apply the pilot changes: attributes, levels, question text; regenerate the design for the chosen sample size Nov 2 to Nov 7 Nov 3 to Nov 8 1 d 0 d FS02 Not started
FS02 Final survey Redeploy the final survey; every referenced file on the web; fresh data table; end-to-end test Nov 8 to Nov 11 Nov 9 to Nov 12 1 d 0 d FS03 Not started
FS03 Final survey Write the eligibility requirements into survey.qmd for the professor's Prolific pre-screen; push the final survey folder Nov 12 to Nov 14 Nov 13 to Nov 15 Nov 15 1 d 2 d FS04 Not started
S05 Setup Ask the professor to add the fifth member to the official repo and confirm the team size Sep 16 to Sep 18 Sep 18 to Sep 20 Sep 20 2 d Not started
SP02 Survey plan Target population, fallback, distribution strategy, and the exact eligibility question text Sep 21 to Sep 24 Sep 23 to Sep 26 2 d 2 d SP04 Not started
PS02 Pilot survey code/1_make_choice_questions.R: generate data/choice_questions.csv with cbc_design using the plan's design parameters Oct 4 to Oct 7 Oct 7 to Oct 10 3 d 3 d PS05 Not started
PA05 Pilot analysis Triage classmate feedback and list the changes for the final survey Oct 25 to Oct 26 Oct 28 to Oct 29 3 d 3 d PA06 Not started
S06 Setup Fill TEAM.md and the team page: one owner and one backup per deliverable, meeting cadence Sep 16 to Sep 23 Sep 22 to Sep 29 6 d 0 d S07 Not started
S07 Setup Decide who owns the shinyapps.io account and the Supabase project Sep 24 to Oct 2 Sep 30 to Oct 8 6 d 6 d PS04 Not started
FA01 Final analysis Scaffold clean_data.R, modeling.R, analysis.R and the report skeleton on the pilot data so the final data only needs re-running Nov 9 to Nov 21 Nov 15 to Nov 27 6 d 6 d FA02 Not started
FA07 Final analysis Define the competitor alternatives for the market simulation (levels and premiums) from the products benchmarked in the proposal Nov 9 to Nov 14 Nov 26 to Dec 1 17 d 17 d FA04 Not started

Where the risk concentrates

Three places have no give at all. This week: the proposal workshop, the revision and the move into the official repo all sit between today and Sunday with zero float, because the meeting and the deadline share the week. Weeks 9 to 11: the pilot exchange on Oct 21 feeds a Nov 1 report through a chain of two-day tasks, and the final survey has to be rebuilt and redeployed by Nov 15 with one day of float, while HW8 to HW10 and Quiz 5 land in the same fortnight. Thanksgiving to Dec 6: the Prolific data arrives at the end of the assumed fielding window and the final report is due the Sunday after the in-class exam, so cleaning, modelling, analysis and writing each get about two days.

The defences are already in the plan: start cleaning on partial pilot data (PA02) while the feedback is triaged in parallel (PA05); scaffold every final-analysis script and the report skeleton on the pilot data in the second week of November (FA01, six days of float, so it can absorb a slip without hurting anything); confirm the Prolific launch date at the Nov 11 class so FS04 stops being an assumption. The risk register carries the triggers and responses.

EMSE 6035 team project tracker. Public site: no grades, no personal details, no credentials.

 

Built with Quarto and R; the schedule is computed from data/*.csv on every render.