DB9802: Data Analysis Practice and IRB Approval

DB9802 moves a Capella University DBA project from plan to evidence. The catalog says students gain the knowledge and skills to collect data using appropriate, ethical and structured processes described in an approved proposal, noting that collection may occur only if IRB approval is received.

They analyze datasets, write results and look for communities of interest for dissemination.

The course is S/NS graded and sits between the proposal and the full results course. Its pressure points are timing, since IRB approval governs when data can be collected, and discipline, since the analysis must follow the approved plan.

What DB9802 Covers

Key Ideas Explained

Following the Approved Plan

Approved procedures are a commitment. If something must change, such as a recruitment method, ask what approval is needed before acting, and keep a record of the change.

Reporting Results Separately from Interpretation

A results section states what the data show. Interpretation, comparison with the literature and implications belong in later discussion. Keeping them apart makes findings easier to verify.

Choosing Communities for Dissemination

Think about who could use your findings: professional associations, industry groups, or practitioner publications. Naming specific groups is stronger than saying "the business community".

Typical Assignments and How to Approach Them

Where Students Get Stuck

• Waiting for approval. Use the time to prepare instruments and analysis steps.
• Mixing results and discussion. Keep them in separate sections.
• Unclear analysis steps. Write them in sequence with software or methods named.
• Low response. Plan for it and discuss options with faculty early.

Planning Your Term

Writing Results: Structure and Checks

A results section is easier to write when you decide its structure before looking at the data. This table gives a simple planning pattern that works for many designs.

Keep numbers and quotations traceable. Every figure in the text should appear in a table or output you can point to, and every excerpt should come from a record you can locate. This habit prevents embarrassing errors when reviewers check.

Think about limits as you go. Small samples, missing data and non-response are common, and describing them plainly is better than hiding them. The course also asks you to find communities of interest, so note which audience would care about each finding, because that shapes later presentation work.

If your design is qualitative, show your coding trail. A short example of how excerpts became codes and codes became themes gives readers confidence without adding length. If it is quantitative, report the test, the result and the sample it applies to in a consistent format.

Record Keeping That Protects You

Keep a dated log of what you did and when: approval received, recruitment started, data collected, files cleaned, analysis run. If a reviewer queries the process, the log gives a precise answer and shows you followed the approved plan.

Study Tips for DB9802

• Keep raw data, cleaned data and analysis files in separate, backed-up folders.
• Write methods notes as you go instead of afterwards.
• Draw table shells before analysis so you know what to report.
• Check with faculty before any change to approved procedures.

How We Help with DB9802

We cannot collect or analyze your data for submission. We can explain analysis methods, prepare model results sections with illustrative figures, and review your write-up for structure, clarity and APA. See our dissertation data analysis help guide for context.

GradeEssays is independent of Capella University. Our work is a study and reference aid; you complete and submit your own work under Capella's academic integrity policy. Orders are written from scratch, include free revisions within the scope of your original request, and are refunded in full if late.