DB FPX 9980 Assessment 1 Project Alignment Audit example

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

This DB FPX 9980 Assessment 1 sample paper is a project alignment audit of a doctoral project on apprentice retention, checking that its parts still fit together after months of work. It was written for Capella DB FPX 9980, Doctoral Project Development, a course in the Doctor of Business Administration (DBA) listed as DB-FPX9980. The paper quotes the problem, purpose, research questions and method statements exactly, then examines each junction between them in turn. It gives execution drift, where the study as carried out moved away from the plan, its own section. It grades each misalignment by severity and states the order in which to fix them.

CourseDB FPX 9980 Doctoral Project Development
AssessmentAssessment 1
Paper typeProject alignment audit
LengthAbout 1,090 words, 5 pages
FormatAPA 7 student paper
SchoolCapella University
ProgramDoctor of Business Administration (DBA)
UpdatedSeptember 2026

Free sample paper for DB FPX 9980 Assessment 1

1

Auditing Alignment Across a Doctoral Project: Statements Quoted, Each Junction Examined in Turn, Execution Drift Given Its Own Section, Severity Graded, and the Order of Fixes Stated

Student Name

Capella University

DB FPX 9980: Doctoral Project Development

Instructor Name

Month Day, Year

What this part is doingThe title names the audit's method. Alignment audits are judged on quoting rather than paraphrasing, so quotation is promised.
2

Statements Quoted, Not Summarized

An alignment audit compares what a project says at each stage, so the statements must be quoted exactly; a summary would smooth over the very differences the audit looks for. The six statements below are quoted from the current draft. They were chosen because each is the place where the project commits to something: what the problem is, what the project will do, what it asks, how it will answer, and what it concludes. Other passages restate these commitments, but if the commitments themselves are misaligned, no restatement can repair them. Problem, page 9: "Nobody at the contractor can say whether first-year losses cluster on some crews, or whether they follow differences in how crews take in new apprentices." Purpose, page 12: "This convergent mixed methods study describes how first-year retention differs from one primary crew to another and compares what retained and departed apprentices say about their socialization." Research question 1, page 13: "How widely does first-year retention differ across primary crews?" Research question 2, page 13: "How do retained and departed apprentices differ in their descriptions of crew socialization tactics and of their own adjustment?" Method, page 44: "Crew-level retention is computed from records of every apprentice who entered from 2020 to 2024, and interview transcripts from both groups are coded thematically." Conclusion, page 78: "Crews that pair apprentices with a journeyman retain more of them."

Junctions Examined One at a Time

Problem to purpose: aligned. The problem names two unknowns, concentration on crews and relation to socialization, and the purpose addresses each. Purpose to questions: aligned, with one gap. The purpose names socialization accounts; question 2 names socialization tactics and adjustment. The purpose should add adjustment, since the questions and findings include it. Questions to method: aligned. Question 1 is answered by retention by crew, question 2 by thematic analysis of interviews. Method to findings: aligned in design, but see execution drift below. Findings to conclusion: misaligned. The conclusion's sentence reads as a causal claim and names pairing as the cause, while the findings report that apprentices on high retention crews more often described pairing. The design cannot support the conclusion as worded. It also names one practice as the reason for the difference, although the findings describe several practices that occurred together on the same crews; even a correlational statement should not single out pairing when sequencing and inclusion were reported alongside it. Five of the six junctions hold; the one that breaks is the last, where a finding about accounts became a claim about causes.

What this part is doingEach junction is judged separately. Scorers reward audits that locate the break rather than rate the whole.
3

Execution Drift Given Its Own Section

Alignment can hold on paper and still fail in execution, when what was done differs from what the method said would be done. Three instances of drift were found by comparing the method section with the analysis files. First, the method says interviewers would not know which crews had high or low retention. The interview log shows that the outside interviewer was told the crew rankings before the last four interviews, when a scheduling problem required the researcher to explain which participants were priorities. The four interviews should be identified, and the discussion should note the possible influence. Second, the method assigns each apprentice to whichever crew logged the largest share of that apprentice's first-year hours. The analysis file shows that for three apprentices with equal hours on two crews, the earlier crew was used without a stated rule. The rule should be stated. Third, the method says two coders would code eight transcripts independently. The coding log shows nine, the ninth added when a disagreement arose. This is a harmless drift but should be reported accurately. Adding a transcript when coders disagree is consistent with the reflexive, iterative coding Braun and Clarke (2006) describe, but the method section should say that it happened and why.

Severity Graded

IssueLocationSeverityReason
Conclusion stated causallyPage 78HighClaims more than the design supports
Interviewer knew crew rankings for four interviewsMethod page 49; interview logHighCould bias the data the conclusions rest on
Purpose omits adjustmentPage 12MediumPurpose narrower than questions and findings
Tie rule for primary crew unstatedMethod page 41LowAffects three apprentices, no change to results
Nine transcripts double-coded, not eightMethod page 50LowReporting accuracy only
What this part is doingSeverity is graded by consequence, with a reason for each grade. Scorers reward audits that distinguish serious from cosmetic.
4

Fix Order Stated

Fixes should be made in this order. First, investigate the four interviews conducted after the interviewer learned the rankings: compare their themes with the other 22 and report whether they differ; if they do, report findings with and without them. This comes first because its result could change the findings that later fixes depend on. The check takes about a day, since the themes are already coded. Second, rewrite the conclusion on page 78 and any similar sentences to describe association. Third, add adjustment to the purpose statement. Fourth, state the tie rule and correct the count of double-coded transcripts. Fixing in this order avoids rewriting the conclusion twice if the interview check changes what can be concluded.

What the Audit Does Not Cover

The audit examines alignment among the project's statements and between its method and its execution. It does not evaluate whether the literature review is complete, whether the writing is clear, or whether the findings are important; those belong to other reviews. Nor does it recheck the calculations in the findings, which the final manuscript review covers. A clean audit would therefore not mean the project is ready, only that its parts say the same thing. The audit was completed in two sittings, and its log of quoted statements is attached so that the chair can check each judgment against the draft itself. If the chair disagrees with any severity grade, the fix order can be revised before the author begins. Keeping the audit to alignment made it possible to read the six statements closely enough to see a single verb that changed the project's claim.

Conclusion

Quoting each statement shows a project that is aligned from problem to method, breaks at the final step where a finding became a causal claim, and drifted in execution in one serious way, the interviewer's knowledge of crew rankings. Severity is graded and fixes are ordered so that the most consequential question is settled first.

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 1 instructions

DB FPX 9980 Assessment 1 asks you to audit the alignment of your doctoral project. You quote the key statements from your project, including the problem, purpose, research questions, design, sample and analysis, check whether each connects logically to the next, identify places where the project as carried out has drifted from the proposal, rate how serious each misalignment is and set the order for correcting them. The audit diagnoses problems rather than fixing them, which comes next. Capella's doctoral alignment guidance and methods texts on research design coherence support the audit.

How the DB-FPX9980 Assessment 1 example is put together

Statements, junctions, drift, severity. The opening assembles the four statements as they currently appear in the document, quoted rather than summarized, since the audit is about their actual wording. Each junction is examined separately and produces a finding, recorded whether or not the finding is welcome. A separate block asks what has changed during execution and whether the written statements have kept up, which is the section a proposal stage audit cannot have. Misalignments are then graded by severity, separating wording from substance. The closing sets out what has to be corrected before further writing, and in what order, since some fixes make others unnecessary. Headings name the junctions, and every finding cites the passage of the document it rests on rather than describing it.

Where the marks sit in the DB FPX 9980 Assessment 1 scoring guide

Capella's criteria for the audit cover the quotation of statements, the examination of each junction, the treatment of execution drift, the severity grading and the order of fixes. Statements reach Distinguished when quoted exactly from the project, since paraphrase can hide the very misalignment the audit is looking for. Junctions score higher when examined one at a time, such as whether the purpose statement names the same population as the problem statement. Execution drift earns credit when given its own section, covering changes like a smaller sample or a different data source than planned. Severity is judged on whether grades are defined, separating fatal problems from cosmetic ones. The order of fixes should start with the problems that affect other parts. The audit should stop short of rewriting. A Proficient audit finds mismatches; a Distinguished one tells the writer exactly what to fix first.

DB FPX 9980 Assessment 1 help from the desk

Alignment audits often paraphrase the project's statements, which smooths over the differences they are meant to catch. Another weakness is checking only the obvious junction between the problem and research questions while ignoring method and analysis. Execution drift is left out, although most projects change during data collection. All problems are treated as equally serious, so the writer fixes small issues first. The audit slides into rewriting, losing its diagnostic focus. Committee feedback is ignored. Laying the quoted statements in a column and marking each junction with a pass, a minor issue or a serious issue gives the audit clarity and prepares the chapter integration draft in Assessment 2.

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

Send the Assessment 1 instructions and the scoring guide from your DB FPX 9980 courseroom, with the statements your project currently carries. 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 audit of your own project is yours to conduct on your own document. 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 1 questions, answered

What if the audit finds a serious misalignment?

Report it and sequence the fix, which is what the assessment is for. Finding a design problem now is expensive; finding it at defense is worse. An audit that surfaces something substantial and proposes an ordered correction demonstrates exactly the judgment this course is assessing.

How is this different from the proposal alignment check?

The project has run. A proposal is checked for internal consistency before anything happens; this audit also asks whether the study that was actually conducted still matches the statements written before it. Drift during execution is normal, and the audit's job is to find where the document has not caught up.

Should the audit correct the misalignments it finds?

Follow your instructions. Where correction belongs to a later assessment, the audit's job is to locate, grade and sequence rather than to rewrite. Auditing and fixing in the same pass tends to produce fixes for the problems found early and less attention to whatever was found last.

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

The full doctoral project alignment audit is here, with statements quoted, each junction examined in turn, execution drift given its own section, severity graded and the order of fixes stated.

What if the audit finds a serious misalignment in DB FPX 9980 Assessment 1?

Grade it as serious and fix it first. Finding it now, before final review, is far better than having the committee find it.