Project Management for Research
Session at a Glance
Research as a project — WBS, Gantt charts, milestone tracking; risk identification and mitigation; managing the supervisor relationship; Git for research version control; psychological resilience for the final phase
Building a detailed WBS and Gantt chart for capstone completion; risk register development; Git repository setup and commit workflow; supervisor communication plan
2 hrs Lecture + 12 hrs Lab/Project
Complete project plan + risk register + Git workflow configured
Learning Objectives
By the end of this session, you will be able to:
- Decompose your remaining capstone work into a Work Breakdown Structure (WBS) — identifying all tasks, estimating their duration, establishing dependencies, and representing them in a Gantt chart that provides a realistic, trackable plan for Weeks 19–30
- Identify, assess, and mitigate the top risks to your capstone completion — building a risk register that specifies likelihood, impact, triggers, and contingency plans for each significant risk
- Manage the supervisor relationship proactively — establishing a communication rhythm, preparing effectively for meetings, delivering what you promise, and navigating difficulties constructively
- Apply Git and GitHub for research version control — committing incrementally with meaningful messages, maintaining a clean repository structure, and using version control as a project management tool (not just a backup mechanism)
- Develop psychological strategies for managing the inevitable setbacks and motivational challenges of the final phase — distinguishing between productive iteration and perfectionism-driven avoidance, and building resilience through structured work practices
Session Planner
Suggested breakdown of the 4-hour contact session.
| Time | Segment | Activity | Mode |
|---|---|---|---|
| 0:00–0:08 | Opening | Recap Week 18 lifecycle; "Last week you mapped where you are. This week: the project management skills to get from here to submission — on time, to quality, with your sanity intact." | Whole class |
| 0:08–0:30 | Lecture 1 | Research as a project — WBS: decomposing the dissertation into manageable work packages; Gantt charts for the writing phase; estimating task durations (and why your estimates are wrong); milestone tracking and the 20% buffer rule | Lecture |
| 0:30–0:55 | Lecture 2 | Risk management — identifying, assessing, and mitigating capstone risks; the risk register. Managing the supervisor relationship — communication rhythm, meeting preparation, navigating difficulties. Git for research — committing writing, not just code; meaningful commit messages; version control as a psychological safety net. | Lecture |
| 0:55–1:10 | Activity | Risk identification brainstorm: list every risk to your capstone completion. Exchange with a partner — they identify risks you missed. Prioritise the top 3 by likelihood × impact. | Pairs |
| 1:10–1:25 | Discussion | Share top risks; discuss common patterns (time, data access, analysis skills, motivation, supervisor relationship). Facilitator shares anonymised risks from previous cohorts and what happened. | Whole class |
| 1:25–1:40 | Break | — | — |
| 1:40–2:00 | Pitfalls & Resilience Lecture | Managing setbacks — the emotional cycle of a research project; distinguishing productive iteration from avoidance; the "minimum viable progress" principle. When and how to escalate problems. Building resilience through structure. | Lecture |
| 2:00–3:40 | Lab Work | Part A: Build detailed WBS and Gantt chart; Part B: Complete risk register; Part C: Configure Git workflow and make first writing commits; Continue analysis/writing | Individual |
| 3:40–3:55 | Peer Accountability | Exchange project plans with a partner. Each person identifies one unrealistic estimate and one missing task. Partners commit to a 2-week check-in on progress. | Pairs |
| 3:55–4:00 | Exit Ticket | Submit WBS, Gantt chart, and risk register | Individual |
1. Research as a Project — The WBS and Gantt Chart
Research is creative, exploratory, and inherently uncertain — which is precisely why it benefits from project management discipline. The goal of project management in research is not to eliminate uncertainty (impossible) or to enforce rigid adherence to a plan (counterproductive). It is to make the work visible, decomposable, and trackable — so that when things go wrong (and they will), you can see exactly what is affected and adjust intelligently rather than react emotionally.
A WBS is a hierarchical decomposition of all the work required to complete the capstone. It breaks the dissertation into chapters, chapters into sections, and sections into specific tasks — each with an estimated duration, an owner (you), and dependencies on other tasks. The WBS answers: "What exactly needs to be done?" A good WBS has tasks that are specific enough to be scheduled ("Write the regression results paragraph for RQ1" — 2 hours, not "Work on Chapter 4" — 2 weeks). The Gantt chart is the visual representation of the WBS on a timeline, showing task durations, dependencies, and milestones.
1.1 Building Your Dissertation WBS
| Chapter / Work Package | Decomposed Tasks (Examples) | Est. Hours | Depends On |
|---|---|---|---|
| Ch 1: Introduction | Adapt proposal background → dissertation prose (future → past tense); update problem statement with any new evidence; rewrite RQs to match executed study; write significance section; write dissertation structure paragraph | 6–8 | Chapters 3, 4 substantially drafted (you can't introduce what you haven't yet written) |
| Ch 2: Literature Review | Expand proposal lit review (600–900 words → 3,000–4,000 words); add 8–12 sources identified during analysis; restructure around final themes; update gap articulation based on findings; write chapter summary | 15–20 | Final thematic structure from analysis (you need to know what themes emerged to structure the review) |
| Ch 3: Methodology | Update to past tense; describe actual (not planned) sample; document instrument development and piloting; describe actual data collection procedures; specify actual analyses run; incorporate retrospective review deviations; update ethics section | 8–10 | Retrospective review (Week 18); data collection complete |
| Ch 4: Results/Findings | Write participant/sample characteristics; write descriptive statistics; write assumption checks; write main analysis for each RQ; create tables and figures; for QUAL: write thematic narrative with quotes; for MM: construct joint displays | 18–25 | All primary analyses complete; themes finalised |
| Ch 5: Discussion | Write summary of key findings; for each finding: interpret in context of literature, note convergence/divergence with prior research, explain mechanisms; write theoretical implications; write practical implications; connect back to RQs | 12–16 | Chapter 4 complete (you discuss what you found) |
| Ch 6: Conclusion | Write study summary; write contributions (theoretical, practical, methodological); write limitations (honest and specific); write future research directions; write final reflections | 6–8 | Chapter 5 complete (conclusion builds on discussion) |
| Revision & Polish | Address supervisor feedback; proofread all chapters; verify all in-text citations in reference list; check table/figure numbering; ensure consistent formatting; check for APA compliance | 10–15 | Complete first draft of all chapters |
| Defence Preparation | Draft presentation slides; rehearse with timer (3+ times); prepare anticipated Q&A responses; conduct mock defence; revise based on mock feedback | 8–12 | Complete dissertation draft |
1.2 The Five Rules of Capstone Task Estimation
Multiply your initial time estimate by 1.5–2.0. This is not pessimism — it is the empirical finding of decades of project management research. Tasks take longer than we think because we estimate the "ideal" duration (no interruptions, no problems, perfect focus). Reality includes interruptions, problems, and imperfect focus.
A task estimated at "2 weeks" is not a task — it is a project that needs decomposition. The maximum useful task size is one working session (3–4 hours). If you cannot complete it in one session, it is too large. Break it down further.
Add 20–30% buffer to your total timeline. If your plan has zero slack, any single delay cascades through the entire schedule. Buffer absorbs the unpredictable — illness, technical problems, supervisor unavailability, data issues discovered during writing.
Map which tasks depend on which. You cannot write the discussion before the results. You cannot write the conclusion before the discussion. Dependencies create the critical path — the sequence of tasks that determines the minimum completion time.
At the end of each week, compare what you planned to accomplish with what you actually accomplished. The purpose is not self-flagellation — it is calibration. If you consistently complete 60% of planned tasks, adjust future plans to 60% rather than repeatedly failing to meet 100%.
2. Risk Management — Identifying What Could Go Wrong Before It Does
Risk management is the systematic identification, assessment, and mitigation of things that could prevent capstone completion. It is not pessimism — it is the professional practice of anticipating problems and having plans in place before they become crises. A risk that is identified early can be mitigated. A risk that is discovered when it materialises becomes a crisis managed under pressure.
2.1 The Capstone Risk Register
| Risk | Likelihood (1–5) | Impact (1–5) | Score (L×I) | Trigger (Early Warning) | Mitigation Strategy | Contingency Plan |
|---|---|---|---|---|---|---|
| Data collection incomplete by Week 20 | 3 | 5 | 15 | < 80% of target sample by Week 19 | Expand recruitment channels now; send personalised reminders; offer incentive; extend collection window by 2 weeks | Close data collection at Week 21 with whatever sample is achieved; document reduced power; treat as limitation; adjust RQs if necessary |
| Analysis skill gap — cannot run required test | 2 | 4 | 8 | Spent 4+ hours stuck on one analysis without progress | Identify specific skill needed; find tutorial/course; ask supervisor for guidance; consult methodology textbook; post on statistics forum | Use simpler analysis technique that you CAN run correctly; document why the more complex technique was not feasible; acknowledge as limitation |
| Supervisor unavailable for extended period | 2 | 4 | 8 | Supervisor announces travel, leave, or heavy commitments | Schedule key feedback points early; identify backup advisor; ensure written feedback mechanism exists even without meetings | Work independently on tasks not requiring feedback; seek peer feedback; escalate to programme coordinator if absence exceeds 3 weeks |
| Motivation collapse — cannot sustain writing effort | 3 | 4 | 12 | Avoiding capstone work; filling time with low-value tasks; feeling overwhelmed when opening the document | Use Pomodoro method (50-min blocks); set tiny daily goals (write 200 words); establish accountability partner; change writing location; celebrate daily progress | Schedule meeting with supervisor to discuss motivation; consider reducing scope temporarily to regain momentum; seek counselling services if needed |
| Discover fundamental flaw in analysis during writing | 2 | 5 | 10 | Results don't make sense when written up; findings contradict each other; supervisor questions analysis approach | Peer-review analysis pipeline (Week 17); show preliminary results to supervisor early; maintain analysis scripts for easy rerunning | Re-run analysis correctly; document the error and the correction in methodology; if results change substantially, discuss with supervisor before rewriting findings |
The risk register is not a bureaucratic exercise. Identify the risk with the highest Likelihood × Impact score — this is the one that deserves your active attention. For most capstone students, the highest-scoring risk is some variant of "I ran out of time because I underestimated the writing/revision phase." The mitigation: start writing earlier than feels comfortable, share imperfect work, and build buffer into every estimate. A risk identified but not mitigated is a crisis postponed, not a crisis prevented.
3. Managing the Supervisor Relationship
The supervisor-student relationship is the single most important professional relationship in your capstone. A productive relationship accelerates progress, catches problems early, and makes the final phase manageable. A dysfunctional relationship generates stress, delays, and avoidable errors. Managing this relationship proactively is a project management skill — arguably the most important one you will develop during the capstone.
3.1 The Productive Supervision Rhythm
| Frequency | Format | What You Bring | What You Ask |
|---|---|---|---|
| Every 1–2 weeks | 15–30 minute check-in (in-person or video) | Progress since last meeting (specific — "I completed the regression for RQ2 and drafted the results section"); current blocker or question (specific — not "I'm stuck" but "My VIF values are 6.8 and 7.2 — should I drop one predictor?"); plan for next period | "Here's the specific question I need your guidance on." "Is this analysis approach sound?" "Here's my draft — what is the single most important revision?" |
| Every 3–4 weeks | Draft review (email or meeting with written feedback) | A complete chapter or substantial section — not a perfect draft but a complete one. Include a cover note: "This is a first draft. I'm particularly uncertain about [specific section]. I'd appreciate feedback on [2–3 specific aspects]." | "Does the argument flow logically?" "Are there gaps in the literature review?" "Is the analysis correctly interpreted?" "What is missing that should be included?" |
| As needed | Quick email (2–3 sentences) | A specific, discrete question that can be answered briefly. "Should I report adjusted R² or regular R² for my hierarchical regression?" — Not: "Can you look at my Chapter 4 draft?" | One question. One clear request. Make it easy for the supervisor to respond in under 5 minutes. |
3.2 Navigating Supervision Difficulties
| Situation | What NOT to Do | What to Do |
|---|---|---|
| Supervisor gives vague feedback ("This needs work" / "Strengthen this section") | Accept the vague feedback and guess what they meant. Make changes blindly. | "Thank you. To make sure I understand — when you say 'strengthen,' do you mean: (a) more citations, (b) deeper theoretical engagement, (c) clearer argument structure, or (d) something else? Could you give me one specific example of what 'stronger' would look like?" |
| Supervisor is slow to respond (2+ weeks without feedback) | Send multiple follow-up emails. Assume they've lost interest. Stop working while waiting. | Send ONE polite follow-up: "Just checking in on the draft I sent on [date]. I'll continue working on [next section] in the meantime. If there are any major issues with the direction I'm taking, please let me know. Otherwise, I'll proceed as planned." Then keep working. Never stop for feedback. |
| Supervisor suggests a direction you disagree with | Dismiss the suggestion ("That won't work"). Accept it silently and resent it. Complain to peers. | "Thank you for that suggestion. I've been thinking about it, and I have a concern — [specific concern with reasoning]. Here's an alternative approach: [your idea]. Would this address the same concern, or am I missing something?" Engage intellectually with the feedback. Disagreement grounded in reasoning is professional. |
| You are significantly behind schedule | Hide from the supervisor. Cancel meetings. Hope they won't notice. Submit everything at once at the last minute. | Proactively communicate: "I want to be transparent — I'm approximately [X] weeks behind my planned timeline. The main causes are [specific reasons]. My recovery plan is [specific plan]. I'd appreciate your guidance on prioritising the remaining work. I'm committed to completing to quality, even if the timeline shifts." |
Supervisors are busy professionals with multiple demands on their time. The students who get the best supervision are not necessarily the most talented — they are the most professional. They send work in advance. They come to meetings with specific questions. They follow through on commitments. They communicate proactively when things go wrong. They treat the supervision relationship as a professional partnership, not a parent-child or teacher-student dynamic. The students who get the weakest supervision are those who disappear for months and then email a complete draft expecting 24-hour turnaround. The quality of supervision you receive is partially under your control — invest in the relationship, and it will invest in you.
4. Git for Research — Version Control Beyond Code
Git is the industry-standard version control system. For BCA students, it is essential for code. But Git is equally valuable for the writing and analysis components of any capstone — tracking changes to your dissertation text, your analysis scripts, and your data processing pipeline. Used effectively, Git provides: a complete history of every change, the ability to revert to any previous version, a backup distributed across multiple locations, and a structured commit log that documents your research process.
4.1 Git for the Capstone — A Minimal Workflow
| When | What to Commit | Example Commit Message | Why This Matters |
|---|---|---|---|
| After every writing session | Your dissertation .docx or .tex file, even if incomplete | "Ch4: drafted regression results for RQ1 and RQ2, added Table 4.2" | Each commit is a save point. If you delete a section and regret it, you can recover it. The commit log is a writing diary. |
| After completing an analysis | Script/syntax file + output + any generated tables/figures | "Analysis: final regression model with diagnostics, all assumptions checked" | Your analysis is reproducible if your script is committed. If you need to rerun with different data, the script is there. |
| Before making a major revision | The current state of all files | "Pre-revision snapshot before restructuring Chapter 5 discussion" | A checkpoint before major surgery. If the restructuring goes badly, you revert to this commit and try a different approach. |
| After supervisor feedback incorporated | The revised chapter(s) | "Ch3: addressed supervisor feedback — updated sample description, added piloting details, corrected tense" | Documents your responsiveness to feedback. Shows the evolution of your thinking. Essential if questions arise about your revision process. |
| End of every week | All changed files — a weekly checkpoint | "Weekly checkpoint W19: Ch3 methodology complete, Ch4 results 60%, risk register updated" | A weekly snapshot of progress. Over 12 weeks, these commits tell the story of your capstone's development. |
4.2 The Psychological Function of Version Control
Beyond its technical function, version control serves a psychological purpose that is particularly valuable during the final phase of the capstone. It provides permission to experiment: you can try a radical restructuring of your discussion chapter knowing that you can revert to the previous version with a single command. It provides visible evidence of progress: when you feel you have accomplished nothing, the commit log shows exactly what you did each day. It provides protection against disaster: a corrupted file, an accidental deletion, a laptop failure — your work exists on GitHub, not just on your machine. And it builds a professional habit: version control is standard practice in both industry and academia. The capstone is where you learn to use it.
5. Managing Setbacks — Resilience Through Structure
Every capstone encounters setbacks. The analysis reveals that your carefully designed instrument has low reliability. A key participant withdraws. Your model does not outperform the baseline. Your supervisor suggests a major restructuring three weeks before submission. These are not failures — they are the normal experience of research. What distinguishes successful capstone students is not the absence of setbacks but their response to them.
5.1 The Emotional Cycle of a Research Project
| Phase | Typical Timing | What It Feels Like | What to Do |
|---|---|---|---|
| 1. Enthusiasm | Proposal phase (Weeks 1–8) | Excitement about the topic; belief that your research will be significant; high motivation | Channel enthusiasm into concrete planning. The proposal should be specific enough to guide you when enthusiasm fades. |
| 2. The Long Middle | Data collection + early analysis (Weeks 9–17) | Repetitive work; progress feels slow; doubts about the topic or methodology begin to surface; "Is this even going to work?" | Focus on process, not outcome. Trust the methodology you designed when you were in Phase 1. Record small wins daily. Maintain momentum through routine. |
| 3. The Trough | Analysis complete, writing begins (Weeks 18–22) | Seeing the full picture of your research — including its limitations — can be deflating. "My findings aren't as strong as I hoped." "Other people have done this better." Imposter syndrome peaks. | This is NORMAL. Almost every researcher experiences this. Your findings don't need to revolutionise the field — they need to be rigorous, honest, and well-argued. Share these feelings with peers and supervisor — you will discover you are not alone. |
| 4. Integration | Discussion + Conclusion (Weeks 22–26) | The pieces start fitting together. You see how your findings connect to the literature. The argument takes shape. Confidence begins to return. | This is where the dissertation becomes rewarding. The intellectual work of synthesis — seeing how your research contributes — is the most satisfying part of the process. Lean into it. |
| 5. Completion | Final revisions + Defence (Weeks 26–30) | Pride in the completed work. Anxiety about the defence. Readiness to be finished. Mixed emotions — relief, accomplishment, exhaustion. | Channel anxiety into preparation. Rehearse the defence until it feels routine. The defence is the final conversation about research you now know better than anyone. You are ready. |
5.2 Productive Iteration vs. Perfectionism-Driven Avoidance
| Dimension | Productive Iteration | Perfectionism-Driven Avoidance |
|---|---|---|
| Goal | Improve the quality of the work through successive drafts | Avoid the discomfort of producing imperfect work |
| Behaviour | Produces a complete draft → identifies weaknesses → revises → produces improved draft. Each cycle produces a complete (if imperfect) version. | Works on one section endlessly without completing it. Never reaches a "complete draft" state because the standard for "complete" keeps rising. Avoids showing work to others. |
| Time Pattern | Time-boxed: "I will spend 4 hours on this section, then move on regardless." Progress is visible in completed sections. | Unbounded: "I'll finish this when it's good enough." Weeks pass on a single section. Other sections remain unwritten. |
| Self-Talk | "This draft isn't perfect, but it exists. I can improve it." | "This isn't good enough yet. I can't show it to anyone. I need to work on it more before I can move on." |
| Result | A complete dissertation that improves with each revision cycle | An incomplete dissertation with one or two heavily polished sections and large gaps |
On days when motivation is absent and the dissertation feels overwhelming, abandon the goal of "writing well." Instead, commit to minimum viable progress: write 200 words — any 200 words, of any section, at any quality level. Open the document. Write something. Save it. That's it. On many days, those 200 words will unlock momentum and you will write more. On some days, 200 words is genuinely all you can manage. Both outcomes are acceptable. The only unacceptable outcome is writing zero words because you were waiting to feel ready to write well. Progress, however small, is the antidote to paralysis. Momentum, however modest, is the cure for avoidance.
Think Deeper — Cross Questions
Discuss in pairs before sharing with the class.
Build a mini-WBS for ONE chapter of your dissertation. Estimate task durations. Now apply the estimation rule (multiply by 1.5). Compare your original estimate with the adjusted one. Where is the gap largest, and what does this reveal about your implicit assumptions — are you estimating for ideal conditions rather than realistic ones?
Complete the risk register (Section 2.1) for your own capstone. Identify your top 3 risks by Likelihood × Impact. For your highest-scoring risk: is your mitigation strategy actually in place, or is it something you plan to do? If it is not yet in place, what is preventing you from implementing it today?
Reflect on your supervision relationship. On a scale of 1–10, how well is it working? If below 7: what is the primary issue, and what is ONE thing YOU could do differently to improve it? (The question is about what YOU can change — not what you wish your supervisor would change.) If above 7: what specific practices have made it work well, and how can you ensure they continue through the final phase?
Identify where you are on the emotional cycle (Section 5.1). Are you in the Trough? If so, what specific evidence contradicts the feeling that "my research isn't good enough"? (Re-read your proposal — the problem was worth studying then; it still is. Re-read your findings — they are more substantial than you think.) If you are in Enthusiasm or Integration: what can you do NOW to prepare for the Trough when it arrives?
Quick Check — Project Management Diagnosis
Diagnose the project management problem in each scenario.
1. A student's WBS entry: "Write Chapter 4: Results. Duration: 2 weeks." No further decomposition. No specific tasks identified.
2. A student's Gantt chart shows every chapter written sequentially with zero overlap and no buffer between the final chapter completion and the submission deadline. When asked about revision time, the student says: "I'll write it right the first time."
3. A student has not met their supervisor for 8 weeks. When asked why, they say: "I don't have anything good enough to show. I'll meet once I have a complete draft."
4. A student's Git repository for their capstone dissertation shows 12 commits, all with the message "update" and no further description. Each commit includes changes across 4–5 different chapter files.
Knowledge Check — Interactive Quiz
Test your understanding of research project management.
Q1. What is the primary purpose of a Work Breakdown Structure (WBS) for a capstone?
Q2. In a risk register, what does the "Likelihood × Impact" score represent?
Q3. What is the most productive frequency for supervisor meetings during the final writing phase?
Q4. Which commit message follows best practice for version-controlling a capstone dissertation?
Q5. The "Minimum Viable Progress" principle suggests that on low-motivation days, you should:
Lab Activity — Project Planning & Risk Management
Part A: Build Your Detailed WBS and Gantt Chart (60 min)
- Using the WBS template (Section 1.1), decompose each remaining dissertation chapter into specific tasks of 2–4 hours each. List each task, estimate its duration (applying the 1.5× rule), and identify dependencies.
- Create a Gantt chart (Excel, Google Sheets, or project management tool) showing all tasks across Weeks 19–30. Include milestones (chapter complete, first draft complete, supervisor feedback received, revisions complete, defence ready).
- Add 20% buffer — if your plan shows completion at Week 29, you have 1 week of buffer before Week 30. If it shows completion at Week 30, you have zero buffer and need to compress or adjust scope.
Part B: Complete Your Risk Register (30 min)
- Identify at least 8 risks specific to your capstone. Use the template (Section 2.1) — for each risk: likelihood (1–5), impact (1–5), trigger, mitigation strategy, and contingency plan.
- Calculate L×I for each risk. Identify your top 3 risks. For the highest-scoring risk: implement the mitigation strategy TODAY if it is not already in place.
- Exchange risk registers with a partner. Identify one risk they missed and one mitigation strategy that could be strengthened.
Part C: Configure Your Git Workflow (30 min)
- Create or verify your capstone GitHub repository structure (data/, scripts/, writing/, figures/, README.md).
- Make your first writing commit: add your current dissertation draft (even if incomplete) with a descriptive commit message. Follow the commit conventions in Section 4.1.
- Set a personal rule: commit after every writing session. The commit message is your writing diary.
Exit Ticket
Submit with your WBS, Gantt chart, and risk register.
- Submit your WBS and Gantt chart. After applying the 1.5× estimation rule and 20% buffer, does your plan show completion by Week 30?
- What is your highest-scoring risk (L×I), and what specific mitigation action did you take TODAY?
- Rate your supervision relationship (1–10). What is ONE action you will take to improve or maintain it?
- Where are you on the emotional cycle (Section 5.1)? What is your strategy for the current phase?
- One project management skill from this week that you will continue using beyond the capstone:
Key Takeaways — Week 19
"Write the dissertation" is not a task — it is a project that needs decomposition. Break each chapter into specific, scheduleable tasks of 2–4 hours. Tasks you can visualise completing are tasks you will complete. Amorphous mega-tasks invite avoidance.
A risk identified at Week 19 can be mitigated. A risk discovered when it materialises at Week 27 is a crisis. The risk register makes risks visible and forces mitigation planning. Your highest L×I risk deserves active attention today, not when it triggers.
The quality of supervision you receive is partially under your control. Professional communication, prepared meetings, specific questions, and regular check-ins with imperfect work produce better supervision than disappearing and surfacing with a complete draft.
Every substantial research project has a trough — a period when the work feels overwhelming, the findings feel inadequate, and motivation collapses. This is normal. Minimum viable progress — 200 words, one analysis, one paragraph — maintains momentum through the trough until integration and completion arrive.
Facilitator Notes
Preparation Checklist
- Prepare a completed exemplar WBS and Gantt chart for a capstone — showing the level of decomposition expected. Use an anonymised previous student's plan or construct a realistic example. Students need to see what "specific enough" looks like.
- Prepare a completed exemplar risk register with realistic capstone risks (not generic "computer crashes" — risks specific to research: analysis skill gaps, participant dropout, supervisor unavailability, motivation collapse).
- Test the Git workflow demonstration on both Windows and Mac — students will have different operating systems and Git setups. Prepare troubleshooting notes for common issues (authentication, line endings, large file handling).
- Prepare a one-page "Supervision Meeting Template" handout — a structured format students can use to prepare for every supervision meeting: progress since last meeting, specific question/blocker, work planned for next period, and anything the supervisor needs to know.
Common Student Difficulties
- Task estimation optimism: Students consistently estimate task durations for ideal conditions. The 1.5× rule feels like "padding" — until they experience their first week where they complete 60% of planned tasks. Enforce the multiplier: review their WBS and push back on every estimate that assumes uninterrupted focus.
- Risk register as checkbox exercise: Students complete the risk register mechanically without implementing mitigations. The exit ticket asks: "What specific mitigation action did you take TODAY?" This forces the register from a document into action.
- Git anxiety for non-programmers: BBA students with no programming experience may find Git intimidating. Teach the GitHub web interface as a starting point — upload files through the browser, use the web editor for README. Command-line Git can wait. The web interface provides 80% of the value with 20% of the learning curve.
- Supervision relationship passivity: Students treat supervision as something that happens TO them rather than something they actively manage. The supervision meeting template and the "navigating difficulties" scenarios (Section 3.2) are designed to shift this mindset.
Pacing Tips
- This week addresses the "how to get it done" dimension that students often feel is missing from methodology training. Acknowledge this explicitly: "You've learned how to design and analyse research. This week: how to manage the project of completing it. These are different skills, and both matter."
- Check in with students who scored their supervision relationship below 7 on the exit ticket (CQ 3). A deteriorating supervision relationship at Week 19 can derail the final phase. A brief mediation conversation with the student (and, if appropriate, the supervisor) can resolve issues before they escalate.
- The peer accountability pairing (end of lab) is valuable if commitments are followed up. Consider implementing a 2-week check-in — at Week 21, give pairs 5 minutes to report to each other on whether they met their Week 19 commitments. Accountability without follow-up is theatre.