DB FPX 9802 Assessment 1 Practice Data Analysis example

Reviewed by Blythe Cavendish, PhD Data Analysis Practice and IRB Approval Capella University Free custom sample in 24 to 48h

This DB FPX 9802 Assessment 1 sample paper is a practice data analysis that runs a chi-square comparison of retention by onboarding type on a synthetic dataset before any real project data are touched. It was written for Capella DB FPX 9802, Data Analysis Practice and IRB Approval, a course in the Doctor of Business Administration (DBA) with the catalog code DB-FPX9802. The paper logs every analytic decision, from recoding variables to checking expected cell counts, and presents the output before any interpretation. It keeps its revisions visible, showing what changed after errors were found, and reflects on what the practice run teaches for the real analysis after IRB approval.

CourseDB FPX 9802 Data Analysis Practice and IRB Approval
AssessmentAssessment 1
Paper typePractice data analysis
LengthAbout 1,130 words, 5 pages
FormatAPA 7 student paper
SchoolCapella University
ProgramDoctor of Business Administration (DBA)
UpdatedSeptember 2026

Free sample paper for DB FPX 9802 Assessment 1

1

Practicing the Analysis on Data That Is Not Mine: A Chi-Square Comparison of Retention by Onboarding Type in a Synthetic Dataset, With Every Decision Logged, Output Before Interpretation, and Revisions Kept

Student Name

Capella University

DB FPX 9802: Data Analysis Practice and IRB Approval

Instructor Name

Month Day, Year

What this part is doingThe title names the data and the test. Practice analyses in this course are judged on a visible decision trail, so the log is promised.
2

Purpose and Data

This exercise practices the kind of analysis the doctoral project will use for its records strand, on data that do not come from the project. The dataset, supplied by the course, is synthetic: it describes 240 hypothetical new hires at a retail chain, 120 who received a structured onboarding program with an assigned peer mentor and 120 who received the chain's standard orientation. For each hire it records onboarding type, whether the person was still employed at 12 months, age, and store. No real person is represented, and no data from the doctoral project are used, because the project's data cannot be collected until the institutional review board approves it. The exercise mirrors the quantitative strand of the project's convergent mixed methods design, in which records are analyzed separately from interviews before the two are brought together (Creswell & Plano Clark, 2018).

Every Decision Written Down

Decision 1. The outcome, retention at 12 months, is binary, and the comparison is between two groups, so a chi-square test of independence on a two by two table was chosen, with an odds ratio and phi coefficient to express the size of the difference. Decision 2. Before the file was opened, alpha was fixed at .05. Decision 3. Records were checked for missing values before analysis. Three records had a missing retention value. The dataset's notes state that these hires transferred to another company location, so they were coded as retained, since they remained with the employer. This decision was recorded before the analysis was run. Decision 4. Expected cell counts were checked against the usual requirement that each be at least five; all were above 50. Decision 5. No adjustment for store was made in the main analysis, because the exercise practices the bivariate test the project will use first; a stratified check is reported below as a revision.

Assumptions Checked

The chi-square test assumes that each observation is independent and appears in only one cell. Each hire appears once in the dataset, which satisfies the second condition. Independence is less certain, because hires in the same store share a manager and working conditions, so their outcomes may be related. With 24 stores and about ten hires each, this clustering could make the test's p value smaller than it should be. The exercise notes the problem rather than solving it; in the doctoral project, where apprentices on the same crew share a foreman, the same issue is central, and the project's analysis plan will report crew-level retention directly rather than rely on a test that assumes independence.

What this part is doingEach decision is written down with its reason before results appear. Scorers reward analysis that can be audited.
3

Output Before Interpretation

The output is reported first, without comment.

Onboarding typeRetained at 12 monthsLeft before 12 monthsTotal
Structured with peer mentor78 (65.0%)42 (35.0%)120
Standard orientation61 (50.8%)59 (49.2%)120
Total139 (57.9%)101 (42.1%)240

Chi-square test of independence: chi-square with 1 degree of freedom = 4.94, p = .026. Phi = .14. Odds ratio for retention, structured versus standard = 1.80.

Interpretation

In this synthetic dataset, hires who received structured onboarding with a peer mentor were retained at 12 months at a higher rate than hires who received standard orientation, 65.0% compared with 50.8%, and a gap this large would arise by chance in fewer than 3 samples in 100 if onboarding type made no difference. The size of the association is small by the phi coefficient, although a difference of 14 percentage points in retention would matter a great deal to an employer. The odds of being retained were about 1.8 times as high for structured onboarding.

Revisions Kept in the Record

Two revisions were made after the first run, and both are kept in the record rather than silently replacing the original. Revision 1. The first run treated the three transferred hires as missing and excluded them, giving a slightly different table with 237 cases and a chi-square of 4.71. On rereading the dataset notes, the transfers were recoded as retained, as described in Decision 3, and the analysis was rerun. The conclusion did not change, but the record shows both runs. Revision 2. Because stores might differ in turnover for reasons unrelated to onboarding, a stratified check was run within the dataset's two regions. In each region, retention was higher for structured onboarding, 64% against 52% in one and 66% against 49% in the other, so the direction held in both. The check was not planned before the first run, and it is labeled as exploratory. The first run and the rerun are both in the record, because a clean final table hides how it was reached.

Claims Held to What Practice Data Allows

Because the data are synthetic and supplied for practice, no claim is made about real retail workers, about onboarding programs in general, or about the doctoral project's setting. The exercise supports claims about the procedure: the author can set up the test, check its assumptions, report output in standard form, and document decisions. It also exposed a question the project will face, how to code apprentices whose employment ended for reasons other than leaving, such as a transfer or a layoff, and the project's coding rules will be written before its records are opened.

What the Practice Taught About the Project's Records

Three lessons carry over to the project. First, the outcome needs a written definition that covers edge cases before any data are seen; in the project, apprentices who were laid off during a slow period, who transferred to the contractor's other division, or who were dismissed must each be coded by a rule set in advance. Second, clustering matters more in the project than in the exercise, because crews are small and apprentices on one crew share one foreman, so crew-level summaries will be reported rather than a single test across all apprentices. Third, keeping every run in the record took little extra effort and made the analysis easier to explain, so the project will keep an analysis log from the first day. Even within the practice data, the design is observational; hires were not randomly assigned to onboarding type, so the association cannot be read as an effect of onboarding.

What this part is doingClaims are limited to the procedure, not the synthetic findings. Scorers reward restraint about what practice data can show.
4

Conclusion

The practice analysis compared retention between two onboarding types in a synthetic dataset, found a difference of about 14 percentage points, and documented each decision and revision. Its value lies in the practiced procedure and in the coding question it raised for the doctoral project, not in its synthetic result.

5

References

Creswell, J. W., & Plano Clark, V. L. (2018). Designing and conducting mixed methods research (3rd ed.). SAGE Publications.

The Capella DB FPX 9802 Assessment 1 instructions

DB FPX 9802 Assessment 1 asks you to practice your planned analysis on a dataset that is not your project data. You prepare the practice data, state the research question and hypotheses, check the assumptions of the test you have chosen, such as expected frequencies for a chi-square test, run the analysis, report the output in standard form before interpreting it, record each decision and revision in a procedural log and reflect on what you learned for your real analysis. Practice data protect participants, since no real data may be analyzed before IRB approval. Statistics texts such as Field support the analysis.

How the DB-FPX9802 Assessment 1 example is put together

Dataset, question, procedure, output, reflection. The opening describes the practice dataset and what it can and cannot support, which sets the ceiling on every later claim. The second block states the analytic question in a form the data could answer. The third is the procedural record, written chronologically with each decision and its reason, including the ones that turned out to be wrong and were revised. The fourth presents output as produced, with the display kept plain, before any interpretation begins. The fifth interprets briefly and within the limits already stated. A closing block reflects on what the run revealed about the procedure itself, which is what the assessment is actually building. Headings follow the prompt, and methodological choices cite methodologists.

DB FPX 9802 Assessment 1 scoring guide: what Distinguished looks like

The scoring guide weighs the data preparation, the hypotheses, the assumption checks, the reporting of output, the procedural record and the reflection. Preparation reaches Distinguished when every step, from recoding onboarding type to handling missing values, is logged. Hypotheses score higher when stated before the analysis is run. Assumption checks earn credit when shown, including whether expected cell counts are large enough for a chi-square test. Output is judged on whether it is reported in APA format before any interpretation, with the effect size alongside the significance test. The procedural record should keep revisions visible, such as a coding error found and corrected. Reflection should connect the practice run to the real project and the IRB timeline. Distinguished practice runs make the real analysis safer.

DB FPX 9802 Assessment 1 help from the desk

Practice analyses often skip assumption checks because the data are not real, which defeats the purpose of practicing. Another weakness is interpreting results in the same sentence as reporting them. The procedural log is thin or written afterward. Errors are corrected silently. The reflection is generic. Real project data are used before approval, which is an ethics breach. Keeping a dated log as you work, and reporting the test result in a short APA-style table before discussing them, keeps the analysis clean and prepares you for the real work after IRB approval.

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

Send the Assessment 1 instructions and the scoring guide from your DB FPX 9802 courseroom, along with the practice dataset your section supplied. We write a custom example against those exact criteria and return it in 24 to 48 hours. The first custom sample is free, and it models the procedural record rather than the result. 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 9802 papers and DBA samples

DB FPX 9802 Assessment 1 questions, answered

Why does this assessment use practice data?

Because the point is the procedure rather than the finding. Building an analytic routine on data whose properties are known, where a mistake costs nothing, is how the routine becomes reliable before it meets your own material. It also means the record can be shared and discussed in a way real project data usually cannot.

How much detail belongs in the procedural record?

Enough that somebody with the same dataset could reproduce your numbers. That means every decision that affected the result: exclusions, transformations, how missing values were treated, which options were selected. Steps that had no effect on the output can be summarized, but if in doubt, record it.

Can you analyze my own project data?

No. A custom sample shows how a procedure gets recorded and how output is reported, written against your assessment instructions. The analysis of your own project data is your scholarly work and stays yours, which is a boundary this program takes seriously and one we hold to without exception.

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

This page presents the full practice chi-square analysis of retention by onboarding type, with every decision logged, output before interpretation and revisions kept visible.

Why use practice data in DB FPX 9802 Assessment 1?

Real project data cannot be analyzed until the IRB approves the study. Practicing on synthetic or public data lets you test your methods without risk to participants.