| Course | PUBH 9101 Completing Doctoral Capstone I |
|---|---|
| Week | Week 5 |
| Paper type | Sequence and dependencies plan |
| Length | About 560 words, 5 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | PhD in Public Health |
| Updated | October 2026 |
Free sample paper for PUBH 9101 Week 5
What Waits on What: A Sequence and Dependencies Plan for a Pool Inspection Scheduling Capstone, Naming the Critical Path and Breaking a Loop Between Ethics Review and the Interview Guide
Student Name
Walden University
PUBH 9101: Completing Doctoral Capstone I
Instructor Name
Month Day, Year
What Waits on What: A Sequence and Dependencies Plan for a Pool Inspection Scheduling Capstone, Naming the Critical Path and Breaking a Loop Between Ethics Review and the Interview Guide
The Dependency Table
Every task left in this capstone, which follows an invented county's pools through a change in inspection frequency, is listed below with what it waits on and what waits on it.
Table 1
Tasks and their dependencies
| Task | Waits on | Waited on by | |
|---|---|---|
| Send data request | Final list of files (done) | Data use agreement | |
| Data use agreement signed | Data request; county legal review | Extract | |
| Review board determination | Final interview guide; protocol | Interviews; extract use | |
| Interview guide final | Pilot interview | Review board submission | |
| Pilot interview | Review board approval | Interview guide final | |
| Extract received | Agreement; review board determination | Pairing | |
| Pairing and repeat flags | Extract; switch dates | Analysis | |
| Switch dates received | Program manager's memo search | Pairing | |
| Time series analysis | Pairing and flags | Chapter 4 | |
| Interviews | Review board approval; manager's invitation | Interview analysis | |
| Interview analysis | Interviews | Chapter 4 | |
| Chapter 4 | Both analyses | Final defense | |
Tasks already complete are omitted.
The Critical Path
Drawn as boxes and arrows, one chain is longer than every other: data request, agreement, extract, pairing, analysis, chapter 4. That chain is the critical path. Any delay along it moves the final defense by the same amount, while delays elsewhere can be absorbed. The agreement is the slowest link, since county legal review has no fixed turnaround. For that reason the data request goes out first, before anything else is finished.
The Loop
The table exposed a loop. The review board wants the final interview guide before approving the study. The guide cannot be final until it has been piloted. A pilot interview with an inspector is itself research and needs board approval. As written, neither can happen first.
The loop is broken in two ways. First, the guide will be piloted with a retired inspector from a different county, reading the questions aloud and commenting on their clarity, which tests wording without collecting data about anyone's practice. Second, the protocol will tell the board that minor wording changes after the first two interviews will be submitted as an amendment. Interview guides commonly evolve during qualitative work (Creswell & Creswell, 2018), and stating that in advance is more honest than claiming a guide is final when it has not met a real participant.
What the Sequence Means for the Calendar
Working forward from today, the records strand cannot start analysis until the agreement is signed and the switch dates arrive. The interview strand can begin as soon as the board responds. Because the interviews concern inspectors' professional practice rather than sensitive personal information, the board may find them exempt (45 C.F.R. § 46.104), which would shorten the wait. The records portion uses facility data and may fall outside human subjects rules altogether. Starting interviews while waiting for the extract keeps the term moving. A plain-language project schedule like this one is also what allows a quasi-experimental study's switch dates and windows to be fixed before data arrive, protecting the analysis from choices made after seeing results (Shadish et al., 2002). The table and diagram will be revisited every two weeks, and any task whose prerequisites change will be redrawn so the critical path stays accurate.
References
Creswell, J. W., & Creswell, J. D. (2018). Research design: Qualitative, quantitative, and mixed methods approaches (5th ed.). Sage.
Exemptions, 45 C.F.R. § 46.104 (2018).
Shadish, W. R., Cook, T. D., & Campbell, D. T. (2002). Experimental and quasi-experimental designs for generalized causal inference. Houghton Mifflin.
What the PUBH 9101 Week 5 instructions ask for
Sequencing assignments ask candidates to map the order in which remaining capstone tasks must happen. Prompts usually require a list of tasks with their prerequisites, a diagram or description of the critical path, and identification of bottlenecks or circular dependencies. Instructors expect candidates to act on what the map shows, for example by starting the slowest task first. Plans that list tasks in chronological order without stating dependencies, or that miss a loop that would stall the project, typically lose credit because the week's aim is to find what actually controls the finish date.
How the PUBH 9101 Week 5 example is put together
The plan opens with a dependency table listing each task, what it waits on and what waits on it. A section identifies the critical path and explains why the data use agreement is its slowest link, so the request goes out first. A section describes the loop between the interview guide and review board approval and explains how a wording-only pilot with a retired inspector and an amendment commitment break it. A final section translates the sequence into a calendar, noting that interviews can begin while the records strand waits and that fixing dates early protects the analysis. The diagram is described in words as well as drawn, with the critical path marked heavier, so the plan remains clear in text-only form. The plan commits to redrawing the map every two weeks as prerequisites change.
Where the marks sit in the PUBH 9101 Week 5 rubric
Graders typically evaluate accuracy of dependencies, correct identification of the critical path, recognition of loops and practicality of solutions. Listing dependencies in both directions earns credit because it shows which delays spread furthest. Naming the slowest link and acting on it demonstrates planning sense. Recognizing that a pilot interview is itself research shows ethical awareness. Solutions that are honest with the review board, rather than claiming a guide is final, are often valued. Plans that let parallel work proceed while waiting tend to be judged realistic. Plans that explain why starting the slowest task first shortens the whole project demonstrate an understanding of critical paths that goes beyond listing tasks. Clear language, without project management jargon, makes the plan usable by a chair.
Common PUBH 9101 Week 5 mistakes, and how to avoid them
Write every remaining task on its own line and, beside each, list what must be finished first. Then trace the longest chain from now to your defense; that is your critical path. Start the slowest task on it immediately. Look for any pair of tasks that each wait on the other, and find a way to break the loop honestly. Identify work that can proceed in parallel. Revisit the map every two weeks. If your tasks seem tangled and you cannot see what to start first, we can draw a sample dependency plan from your list.
Get a PUBH 9101 Week 5 example written to your instructions
List every task still between you and a finished study, however rough, plus the Week 5 prompt and rubric. They come back ordered by what each needs first, with the longest chain named and any circular dependency redesigned. Free the first time and ready within 24 to 48 hours; the review loop and task list shown come from no real department.
More PUBH 9101 papers and PhD in Public Health samples
- PUBH 9101 Week 1: Status Memo
- PUBH 9101 Week 2: Decision Sweep
- PUBH 9101 Week 3: Procedure Draft
- PUBH 9101 Week 4: Source Access Plan
- PUBH 9101 Week 6: Sizing Arithmetic
- PUBH 9101 Week 7: Contingency Note
- PUBH 9101 Week 8: Out-of-Scope Statement
- PUBH 9101 Week 9: Peer Stall Test
- PUBH 9101 Week 10: Promise Audit
- PUBH 9101 Week 11: Working Document
- PUBH 9102 Week 5: Non-Response Note
- PUBH 8546 Week 5: Geographic Analysis
- PUBH 9103 Week 5: Claim Calibration
- PUBH 8503 Week 5: Rejected Alternatives
PUBH 9101 Week 5 questions, answered
Where can I find a free PUBH 9101 Week 5 sample paper?
The Week 5 sequence and dependencies plan is above in full, for a pool inspection capstone.
What is the critical path?
Data request, agreement, extract, pairing, analysis and chapter 4.
Which link is slowest?
The data use agreement, because county legal review has no fixed turnaround.
What loop did the table expose?
The board wanted a final interview guide, the guide needed a pilot, and the pilot needed approval.
How was the loop broken?
A wording-only pilot with a retired inspector from another county, plus an amendment plan for later changes.