QFT1 Business - IT Management Capstone Project is BUS 4890 in the WGU catalog and carries 4 competency units, integrating and synthesizing all competency domains for the B.S. Information Technology Management degree. The four-character code is one of WGU's older formats and appears that way in Degree Plans, so QFT1 and BUS 4890 are one course. Its defining difficulty is the hyphen in the title: the project has to satisfy technical and business aspects at once, and most students are stronger on one side. Aspects are marked individually and each requires a 2.
What this capstone is testing
An IT management degree exists because organizations need people who can stand between a technology decision and a business consequence. The capstone is the examination of that ability. A purely technical project, however competent, will leave the business aspects thin, and a purely managerial project will leave the technical ones unsupported.
The practical implication is that your project needs a technology component with genuine detail and a business case with genuine numbers. Both sides must be specific: an implementation described only in vendor terms fails the technical aspects, and a benefit described only as improved efficiency fails the business ones. The degree's portfolio requirement, PFIT, sits alongside this course, and the broader technical hub is IT and computer science help.
Planning a two-sided capstone
WGU does not publish assessment types or task requirements in its catalog; the Course of Study in your portal has yours. If a performance assessment carries it, sort the aspects into technical and business columns before drafting, and check the balance. A rubric with seven business aspects and four technical ones is telling you where the document's weight belongs, and it is frequently the opposite of where a student's comfort lies.
A worked example. Fourteen aspects and a 4,500 word document. Reserve 300 for front matter and 200 for the conclusion, leaving 4,000. Four aspects covering the business problem and case take 350 each, giving 1,400. Four covering the technical solution and its design take 300 each, giving 1,200. Three covering implementation, risk and change take 300 each, giving 900. Three covering evaluation, security or compliance take 166, 167 and 167, giving 500. Sum: 1,400 plus 1,200 plus 900 plus 500 equals 4,000. Note that the business case takes the largest share, which is the ordering an IT management capstone almost always wants.
A capstone document that satisfies both sides
| Component | The business requirement | The technical requirement |
|---|---|---|
| Problem | The operational cost of the current state, quantified | What in the current systems produces that cost |
| Proposed solution | What changes for users and for the organization | Architecture, integration points and data flow at a describable level |
| Alternatives | Options compared on cost, disruption and time to value | Why the rejected technical approaches were rejected |
| Business case | Cost, benefit, payback and the assumptions behind them | The technical facts that make the benefit estimate credible |
| Implementation | Phases, resources, owners and training | Migration, testing, cutover and rollback |
| Risk | Business exposure and continuity | Security, availability and data integrity risks with controls |
| Evaluation | The measures that prove value was delivered | What is instrumented and how the data is captured |
Evidence across two disciplines
The business half needs numbers with derivations: current cost built from components, projected benefit built from a stated mechanism, and a payback calculation whose assumptions are visible. Estimating is expected at capstone level; refusing to estimate is what costs aspects, since a business case with no arithmetic is a proposal rather than a case.
The technical half needs precision rather than depth. Naming the systems involved, describing where data moves and in what form, and identifying the integration points is enough for a management capstone, and it is considerably more than vendor language provides. Cite standards, documentation and independent sources in APA, and treat supplier performance claims as marketing until corroborated. Submitted work runs through WGU's Similarity Checker, so architecture descriptions and any diagram must be your own construction.
Where these capstones pass and return
WGU marks work Competent or Not Competent, with no letter grades and no GPA, and each aspect requires its own 2. This capstone returns for imbalance more than anything else. A technically strong student produces a detailed solution design and a business case consisting of one paragraph asserting efficiency gains. A managerially strong student produces a persuasive case supported by a technical section that could describe any system.
The reliable correction is to draft your weaker half first, while energy and time are available, and to give it slightly more length than feels natural. Passing documents also connect the two halves explicitly, with sentences that name a technical fact and the business consequence that follows: because the two systems currently exchange data by overnight file transfer, order status is up to a day stale, which produces a stated number of avoidable customer contacts each week. That sentence pattern is the whole degree in miniature. Returned work identifies the aspects that fell short, and a revised submission carries no penalty.
Six mistakes that cost weeks in QFT1
- A project with no business problem. Upgrading because a system is old is not a case; what it costs to keep is.
- Benefits asserted, not derived. Efficiency gains with no mechanism and no arithmetic satisfy no business aspect.
- Vendor material as technical detail. Product descriptions do not demonstrate that you understand the integration.
- Security treated as a paragraph. In an IT management capstone, security and data risk usually carry their own aspects.
- No rollback or contingency. Implementation aspects look for what happens when the cutover fails.
- Scope beyond a capstone. A full enterprise transformation cannot be specified in one document, and everything stays shallow.
Two-sided capstone, one deadline
Send the rubric and your project. You get a scope read, a balance check across technical and business aspects, and a model draft built section by section.
Building a business case an evaluator can check
The business case is where this capstone is won, and it is built from five components that each need a number and a source or a stated assumption.
Current state cost comes first, and it is usually assembled rather than looked up: staff time spent on the workaround, licence and maintenance spend, error and rework cost, and any revenue affected by the current limitation. Implementation cost is second, covering licences or build effort, integration, data migration, training, and the internal time that projects always consume and budgets always omit. Ongoing cost is third, since the new arrangement has its own licence, support and administration burden, and a case comparing implementation cost against total current cost while ignoring ongoing cost overstates the benefit. Benefit is fourth, and it must have a mechanism: time saved multiplied by a rate, errors avoided multiplied by their cost, or revenue enabled with a stated basis. Payback is fifth, and it follows arithmetically once the first four exist.
Then add the sentence that separates a good case from a plausible one: state which assumption the conclusion is most sensitive to, and what value would make the project not worth doing. If the case depends on saving four hours a week per user and it stops paying back within three years at two hours, say so. Evaluators reward that honesty because it demonstrates you understand your own model, and it protects the recommendation from the obvious challenge rather than leaving it exposed.
Three questions QFT1 students ask
How technical does the solution section need to be?
Can I use a project from my job?
When should this capstone begin relative to the term?
Four CUs and the end of the degree
The flat-rate arithmetic that rewards speed everywhere else in a WGU plan works against you at the capstone, where one unfinished course can cost an entire six month term. Schedule the capstone first inside its term rather than last, run lighter courses alongside it, and treat submission date as the target rather than the deadline. The queue timing guide covers the wait to design around.
Where QFT1 sits in WGU's programs
The July 2026 catalog places this code in 1 current WGU program. Open a program page for the complete standard path and term positions. The live Degree Plan remains authoritative after transfer credit, substitutions, and mentor planning.
The assessments, one by one
The public catalog does not publish this course's PA/OA identity or task count. WGU Tutors publishes at most one PA manual per course and only from a WGU-controlled public rubric. Until that source exists, PA help begins from the student's real Course of Study and OA support remains preparation only.