DB FPX 9980 Assessment 3 Completion Plan example

Reviewed by Blythe Cavendish, PhD Doctoral Project Development Capella University Free custom sample in 24 to 48h

This DB FPX 9980 Assessment 3 sample paper is a completion plan for finishing a doctoral project on time, built from tasks rather than wishes. It completes Capella DB FPX 9980, Doctoral Project Development, in the Doctor of Business Administration (DBA), catalog code DB-FPX9980. The paper breaks the remaining work into tasks and estimates each from the author's own past pace, not from general advice. It separates tasks that depend on other people, such as committee reviews, places buffer where the uncertainty actually is and decides contingencies in advance. It closes with a weekly check the author will use to stay on track.

CourseDB FPX 9980 Doctoral Project Development
AssessmentAssessment 3
Paper typeDoctoral completion plan
LengthAbout 1,100 words, 5 pages
FormatAPA 7 student paper
SchoolCapella University
ProgramDoctor of Business Administration (DBA)
UpdatedSeptember 2026

Free sample paper for DB FPX 9980 Assessment 3

1

Finishing the Doctoral Project on Time: A Completion Plan Built From Tasks, Estimated From the Author's Own Past Pace, With People Dependencies Separated, Buffer Where the Uncertainty Is, and Contingencies Decided in Advance

Student Name

Capella University

DB FPX 9980: Doctoral Project Development

Instructor Name

Month Day, Year

What this part is doingThe title names the plan's method. Completion plans are judged on realism, so estimates from past pace are promised.
2

Tasks, Not Chapters

A plan that says "revise Section 4 in April" hides the work. It hides how many separate things must happen, which of them depend on someone else, and which could change the others. Tasks with a clear definition of done can be checked off; chapters cannot. This plan breaks the remaining work into tasks, each with a definition of done.

TaskDone whenEstimate
Check four interviews held after the interviewer learned crew rankingsThemes compared with the other 22 and result written up1 week
Rewrite causal sentences in Sections 5 and abstractAll instances replaced; chair confirms1 week
Add adjustment to purpose statement and align Section 3Purpose, questions, and method use same terms3 days
State tie rule for primary crew and correct coding countMethod section updated1 day
Integration edits from the integration draftClean draft circulated3 weeks
Chair review of full draftWritten comments received3 weeks
Revisions from chair commentsResponse memo and revised draft sent3 weeks
Full committee reviewApproval to schedule defense4 weeks
Defense preparation and rehearsalTwo timed rehearsals completed2 weeks
DefenseCommittee decision recorded1 day
Final formatting review and submissionAccepted by the university's format reviewer3 weeks

Estimates From What Has Already Happened

The estimates are not guesses about how long tasks should take; they are based on how long similar tasks have taken this author. The proposal's methodology section was planned for four weeks and took seven. The findings section was planned for five weeks and took eight. The literature review revision was planned for three weeks and took four. Across these, actual time averaged about 1.6 times the planned time. The author's own writing tasks in the table above have therefore been estimated at 1.6 times the first instinct: integration edits, first estimated at two weeks, appear as three. The committee's review times are also taken from experience rather than hope. The author's employer is another source of delay: the contractor's busy season runs from May through August, and in each of the past two summers the author's writing time fell by about a third during those months. The plan therefore schedules the heaviest writing tasks for April and early May and places review periods, which require little of the author, in the summer. The chair's reviews of the proposal and the findings draft took 16 and 22 days; three weeks is used. The full committee's review of the proposal took 26 days; four weeks is used.

What this part is doingEstimates come from recorded past pace, with the multiplier shown. Scorers reward plans based on evidence about the planner.
3

Dependencies on People Separated

Some tasks depend only on the author; others depend on other people, whose time the author cannot control. The plan separates them. Author-only tasks total about nine weeks. Tasks that depend on others are the chair's review, the full committee's review, scheduling the defense, which requires three calendars to align, and the format review. These total about ten weeks of waiting, during which the author can work only on tasks that do not depend on the result. During the chair's review, for example, the author prepares defense slides; during the committee's review, the author prepares the formatting. Using waiting periods this way turns ten weeks of dependency into productive time, and it means that when comments arrive, the author is ready to act on them at once rather than finishing other work first. One dependency is especially uncertain. The methodologist is on leave for six weeks in the summer, and if the full committee review falls in that period, it will stop. The plan schedules the committee review to finish before the leave begins.

Buffer Where the Uncertainty Is

The plan places buffer where the uncertainty is greatest rather than adding a margin to every task. The largest uncertainty is the check of the four interviews held after the interviewer learned crew rankings: if their themes differ from the others, findings must be reported with and without them, adding perhaps three weeks of analysis and rewriting. Because the themes were built through the iterative review and refinement Braun and Clarke (2006) describe, removing four transcripts could change a theme's boundaries, not only its counts, and that is the reason the estimate is generous. Three weeks of buffer is placed immediately after that task. A second buffer of two weeks is placed before the defense, because defense scheduling has slipped for classmates by that much. No buffer is placed on small author-only tasks, where the 1.6 multiplier already covers slippage. The buffer sits after the one task whose result could change the findings, not spread thinly across every line.

The Calendar

With the estimates, dependencies, and buffers, the plan runs about 26 weeks from April 1: the interview check and buffer through early May, rewriting and integration through mid-June, the chair's review and revisions through mid-August, the committee review through mid-September, the defense in early October, and format review and submission by the end of October.

What this part is doingThe calendar is derived from tasks, estimates, and buffers rather than chosen first. Scorers reward schedules that add up.
4

Contingency Decided in Advance

Three contingencies are decided now, so that no decision has to be made under pressure later. If the interview check shows that the four affected interviews differ from the others, the author will report findings both ways and add a limitation, and will use the first buffer rather than seeking an extension. If the chair's review takes more than four weeks, the author will ask the chair for comments on Sections 4 and 5 first, since those drive the remaining revisions. If the defense cannot be scheduled by mid-October, which would push submission past the program's term deadline, the author will request enrollment in one additional course term now, before the registration deadline in August, because the cost of one term is lower than the cost of an unplanned gap in enrollment.

Conclusion

The completion plan turns the remaining work into defined tasks, estimates them from the author's own past pace and the committee's past review times, separates waiting from working, places buffer after the most uncertain task, and settles three contingencies in advance. It projects submission by the end of October. The plan will be reviewed every two weeks against the task table, and any task that runs more than a week past its estimate will trigger a check of whether the buffer that follows it is still enough.

5

References

Braun, V., & Clarke, V. (2006). Using thematic analysis in psychology. Qualitative Research in Psychology, 3(2), 77-101. https://doi.org/10.1191/1478088706qp063oa

Reading the DB-FPX9980 Assessment 3 instructions

The final assessment in DB FPX 9980 asks you to plan how you will complete your doctoral project. You list every remaining task, estimate each using how long similar work has taken you before, identify tasks that depend on other people and their likely turnaround, add buffer where estimates are most uncertain, decide in advance what you will do if key tasks slip and set a way to monitor progress. The plan should be realistic about work and family commitments. Research on doctoral completion and project planning supports the plan.

How the DB-FPX9980 Assessment 3 example is put together

Inventory, estimates, dependencies, sequence, contingency. The opening lists the remaining work at a granularity somebody could act on, tasks rather than chapters. Each carries an estimate with the basis stated, usually how long similar work has already taken. The dependency block then maps what waits on what, separating dependencies on the writer's own effort from those on other people, since only the first can be compressed. A sequence follows, built from the dependencies rather than from preference, with the critical path identified. Buffer is placed against the uncertain steps. A contingency block states what would be reduced first if time ran short, and in what order. The closing names the date the plan implies and the single assumption that most threatens it.

DB FPX 9980 Assessment 3 scoring guide: what Distinguished looks like

Marks go to the task list, the estimates, the handling of dependencies, the placement of buffer, the contingencies and the monitoring plan. The task list reaches Distinguished when every remaining piece of work is broken into tasks of a few days each, such as revising the limitations section or updating the reference list. Estimates score higher when based on the author's own past pace, drawn from a log of how long similar work took. Dependencies earn credit when tasks that wait on other people, like committee reviews and editing, are separated with realistic turnaround times. Buffer is judged on whether it sits where uncertainty is highest rather than being spread evenly. Contingencies should be decided in advance, such as which optional analysis to drop if the schedule slips. Monitoring should be weekly and simple. Distinguished plans finish on time.

Common DB FPX 9980 Assessment 3 mistakes, and how to avoid them

Completion plans often list chapters rather than tasks, which hides the real work inside each chapter and makes estimates guesses. Another weakness is estimating from optimism or general advice instead of the author's own record. Committee turnaround is ignored, although reviews often take weeks. Buffer is spread evenly across every task or left out entirely. Contingencies are left to decide later, when stress makes good decisions harder. Monitoring is vague, like "check progress regularly." Work and family commitments are not considered. Listing tasks of no more than a few days each, estimating them from a log of past work and marking those that wait on other people keeps the plan realistic and ends the doctoral sequence with a credible path to completion.

Get a DB FPX 9980 Assessment 3 example written to your instructions

Send the Assessment 3 instructions and the DB FPX 9980 scoring guide from your courseroom, with the work your project has left. We write a custom example against those exact criteria and return it in 24 to 48 hours. The first custom sample is free, and the plan for finishing your own project is yours to build and to keep. The paper above is an original model document written by our desk, not a submitted student paper and not an official Capella University document.

More DB FPX 9980 papers and DBA samples

DB FPX 9980 Assessment 3 questions, answered

How do I estimate work I have not done before?

Use the closest thing you have done. A chapter you have not written is best estimated from the chapters you have, adjusted for what is genuinely different. Where nothing comparable exists, break the task down until the pieces resemble work you have completed, and estimate those instead.

How much buffer is realistic?

Enough to absorb one significant delay on each uncertain step, placed against those steps rather than pooled at the end. A plan with no slack assumes nothing goes wrong across months of work involving several other people, which has never once been true of a doctoral project.

What should the contingency block contain?

The specific reductions you would accept, in the order you would accept them, decided now while you are calm. A narrower scope for one analysis, a shorter discussion section, a delayed submission window. Deciding this in advance is what stops the choice being made badly at the point of pressure.

Where can I find a free DB FPX 9980 Assessment 3 sample paper?

The complete doctoral completion plan is here, built from tasks, estimated from the author's own past pace, with people dependencies separated, buffer where the uncertainty is and contingencies decided in advance.

How much buffer is realistic in DB FPX 9980 Assessment 3?

Often twenty to thirty percent, placed on the tasks you have least experience with and those that depend on committee review, rather than spread evenly.