DDBA 8303 Week 11 Case Synthesis Report Example

Qualitative and Case Study Methodology for Business Analysis Research Walden University Free custom sample in 24 to 48h

This DDBA 8303 Week 11 case synthesis report example turns eleven weeks of partial work into one account whose edges are visible from the first page. Walden DDBA 8303 closes with the report, and the sample follows a composite Columbus civil engineering consultancy of about 120 people that began pursuing design-build contracts with two construction partners between 2023 and early 2026. A boundary log records two changes: partners' representatives added in Week 3 and a Cincinnati water-treatment pursuit removed in Week 7. Four findings name their sources, from partner selection and declined pursuits to project managers' changing time and design-build fees reaching about 11 percent of revenue. Recommendations sit on a separate page, following Miles and colleagues, with Yin, Stake and Tracy supporting this DBA report.

CourseDDBA 8303 Qualitative and Case Study Methodology for Business Analysis Research
WeekWeek 11
Paper typeCase synthesis report
LengthAbout 820 words, 5 pages
FormatAPA 7 student paper
SchoolWalden University
ProgramDoctor of Business Administration (DBA)
UpdatedOctober 2026

Free sample paper for DDBA 8303 Week 11

1

One Account With Its Edges Showing: The Closing Case Report on a Civil Engineering Consultancy's Move Into Design-Build Contracts, With a Boundary Log and Findings Kept on a Separate Page From Recommendations

Student Name

Walden University

DDBA 8303: Qualitative and Case Study Methodology for Business Analysis Research

Instructor Name

Month Day, Year

What this page is doingThe title names the case and the two disciplines of the closing report, a visible boundary and a wall between findings and advice.
2

One Account With Its Edges Showing: The Closing Case Report on a Civil Engineering Consultancy's Move Into Design-Build Contracts, With a Boundary Log and Findings Kept on a Separate Page From Recommendations

Where the Case Stops

This case concerns the decision by Stanton Engineering, a composite civil engineering consultancy of about 120 people in Columbus, Ohio, to begin competing for design-build contracts with two construction partners between 2023 and early 2026, rather than serving only as the designer under contracts held by public owners. The research question asks what strategies the firm's principals used to enter design-build work while protecting the firm's reputation as an independent designer. Inside the case are the five principals, the business development director, project managers on the four design-build pursuits the firm made in the period, the firm's proposal records and partner agreements, and two representatives of the construction partners. Outside it are the firm's traditional design contracts, its other offices, the public owners who awarded or declined the pursuits and rival firms. Yin (2018) argues that a case report should make its boundaries clear so readers can judge what the findings cover.

What this page is doingThe report states its boundary on the first page, so every finding can be read against the edges of the case.
3

Changes to the Boundary During the Term

The boundary changed twice, and both changes are recorded here with their dates and reasons.

The first change widened the case. Partners were initially outside on the reasoning that the question concerned the firm's principals. But by the third interview, it was clear that the choice of partners and the terms of the teaming agreements were strategies in themselves, and the partners' view was needed to understand them. The second change narrowed the case. A pursuit led from the firm's Cincinnati office used a progressive design-build contract with different risk allocation, and including it would have mixed two kinds of strategy.

Table 1

Boundary Log

DateChangeReason |
Week 3Added the two construction partners' representativesInterviews showed the partners shaped the firm's strategy as much as the principals did |
Week 7Removed the firm's water-treatment design-build pursuitIt was led by a separate office outside the case and followed a different contract model |

Each change was entered in the boundary log on the date it was made and approved by the chair.

The Evidence Base

The case draws on 14 interviews (five principals, the business development director, six project managers and two partner representatives), the firm's proposal files for four pursuits, two teaming agreements, minutes of 11 principals' meetings and the firm's revenue records by contract type. Each finding below names which sources support it.

What this page is doingThe report summarizes its sources in a sentence each, since the reader needs to know what kind of evidence stands behind each finding.
4

Findings

Finding 1: The principals entered design-build through partner selection rather than through internal change. All five principals and both partner representatives described choosing partners whose own reputations matched the firm's, and the teaming agreements give the firm control over design decisions within set limits. Sources: interviews and agreements.

Finding 2: The firm protected its independence by declining pursuits rather than adjusting its standards. Minutes record the principals declining two invitations to pursue design-build work with contractors they regarded as likely to press for cheaper designs. Four of six project managers described this as the decision that convinced them the move was safe. Sources: minutes and interviews.

Finding 3: Design-build work changed how project managers spend their time. Project managers described more time in cost meetings with contractors and less time with public owners' engineers. Two described this as a loss; four as a gain. Sources: interviews only, so this finding is less well supported than the others.

Finding 4: Revenue from design-build grew but remained small. Design-build fees rose from zero in 2022 to about 11 percent of revenue in 2025, from two won pursuits. Sources: revenue records.

Limits of the Findings

The case describes one firm, four pursuits and the people inside the boundary. It cannot describe how public owners viewed the firm's move, since they were outside the case. Finding 3 rests on interviews alone. And because only two pursuits were won, the case cannot say which strategies lead to winning. Stake (1995) emphasized that the value of a single case lies in understanding it well, not in generalizing; these findings are offered in that spirit.

Recommendations (Separate From the Findings)

The following recommendations go beyond the evidence and are offered as the author's judgment. First, the firm should formalize its criteria for declining partners, since those decisions appear central to protecting its reputation. Second, it should track how project managers' time shifts on design-build projects, so concerns raised in interviews can be measured. Third, it should seek feedback from public owners on its design-build submissions, filling the gap this case could not. Miles et al. (2014) recommend keeping conclusions drawn from data distinct from actions proposed on the basis of them; placing recommendations here, apart from the findings, follows that advice. Tracy (2010) describes sincerity about one's choices and limits as a marker of quality, and the boundary log and this separation are the report's way of showing it.

What this page is doingRecommendations sit on their own page, so a reader can accept the findings while disagreeing with the advice.
5

References

Miles, M. B., Huberman, A. M., & Saldana, J. (2014). Qualitative data analysis: A methods sourcebook (3rd ed.). SAGE Publications.

Stake, R. E. (1995). The art of case study research. SAGE Publications.

Tracy, S. J. (2010). Qualitative quality: Eight "big-tent" criteria for excellent qualitative research. Qualitative Inquiry, 16(10), 837-851. https://doi.org/10.1177/1077800410383121

Yin, R. K. (2018). Case study research and applications: Design and methods (6th ed.). SAGE Publications.

DDBA 8303 Week 11 instructions, in plain terms

The final week asks for a case report that brings together your term's work into one account. State on the first page where the case stops: what is inside and outside, and why. Report every change to the boundary since the start of term, with its date and reason, ideally in a log. Summarize the evidence base. Present the findings, each naming the sources that support it and noting any that rest on a single source. State the limits of the findings. Then, separately, present recommendations, marked as the author's judgment beyond the evidence. Cite case study and qualitative quality sources. The report should let a reader accept the findings while disagreeing with the recommendations.

How this DDBA 8303 Week 11 example is built

The report's first section sets the boundary, citing Yin: five principals, the business development director, project managers on four pursuits, proposals and agreements inside; traditional contracts, other offices, public owners and rivals outside. A boundary log follows with two dated changes and reasons, one widening the case and one narrowing it. The evidence base lists 14 interviews, proposal files, agreements, minutes and revenue records. Four findings each end with their sources, and the third is flagged as resting on interviews alone. A limits section cites Stake on the value of a single case. Three recommendations appear on their own page: formal criteria for declining partners, tracking project managers' time and seeking public owners' feedback, with Miles and colleagues and Tracy supporting the separation.

Reading the DDBA 8303 Week 11 rubric

The report is graded on transparency. A boundary stated on the first page, and a log of every change with reasons, lets a reader judge the case; instructors weigh this heavily because boundaries often drift unrecorded. Findings earn credit when each names its sources and the report flags findings that rest on a single kind of evidence. Limits should be specific to the case. Keeping recommendations separate from findings, and marking them as judgment, is a key discipline of the week and is checked closely. The report should read as one account rather than a set of weekly papers. Sources should support the reporting choices. Honest scope is valued above broad claims.

Common DDBA 8303 Week 11 mistakes, and how to avoid them

Closing reports often bury the boundary and mix advice into findings. Put the boundary on page one. Go back through the term and list every time the case changed; write the date and reason for each. For each finding, name the sources behind it and say if it rests on one kind only. Write limits that a reader could check. Then move every should and recommend into a separate section and label it as your judgment. Read the report as someone who disagrees with your advice and check that the findings still stand. A tutor can help you separate findings from recommendations in your draft.

Get a DDBA 8303 Week 11 example written to your instructions

Enclose the Week 11 report guidelines and rubric, plus any earlier weeks' work and instructor feedback you want carried forward. A full case report returns within 24-48h, and a first request costs nothing. Evidence behind its findings is constructed, so what arrives is the report's shape, ready for your own data to fill.

More DDBA 8303 papers and DBA samples

DDBA 8303 Week 11 questions, answered

Where can I find a free DDBA 8303 Week 11 sample paper?

The complete case synthesis report, from boundary to recommendations, is available lower on this page without charge.

What case does the DDBA 8303 Week 11 report cover?

A civil engineering consultancy's move into design-build contracts with two construction partners between 2023 and 2026.

How did the boundary change during the term?

The partners' representatives were added in Week 3, and a separate office's water-treatment pursuit was removed in Week 7.

Which finding rests on the thinnest evidence?

That design-build changed how project managers spend their time, which rests on interviews alone.

Why are recommendations on a separate page?

So a reader can accept the findings while disagreeing with the author's judgment about what to do.