The BU 434 Unit 6 prioritization exercise, in full
The Method Ranked Quantity Breaks Above the Data Link, and Was Wrong: A Prioritization Exercise for Eight Functional Requirements at a Composite Michigan Printer
Student Name
Business, Herzing University
BU 434: Business Analysis for Project Managers
Instructor Name
April 8, 2026
The Method Ranked Quantity Breaks Above the Data Link, and Was Wrong: A Prioritization Exercise for Eight Functional Requirements at a Composite Michigan Printer
What Is Being Prioritized and Why
The requirements document for the structured quote request at Ridgeline Press, the invented Grand Rapids printer studied in this course, lists eight functional requirements. The team and the systems contractor cannot build all eight at once; the contractor works two days a month, and the sponsor wants a first release before the summer catalog season. This exercise ranks the eight so that the first release contains the requirements that matter most. The non-functional requirements are treated as constraints that every release must meet, not as items to rank, since a form that fails accessibility or cannot be used on a phone is not a smaller version of the solution but a broken one.
Achimugu et al. (2014) reviewed dozens of requirements prioritization techniques and found that most had been evaluated on small examples and that no single technique was shown to be best, so the choice of method should be stated and its results treated as evidence rather than a verdict. This exercise uses weighted scoring, a relative of the cost-value approach Karlsson and Ryan (1997) described, because it lets every criterion and weight be seen and argued.
The Rules, Stated Before Any Ranking
Four criteria were agreed with the sponsor, the estimating lead and the customer service supervisor on April 1, before any requirement was scored. Contribution to the business requirements, weighted 40 percent, asks how directly the requirement moves request completeness, waiting time or guessed repricings. Breadth of stakeholder need, 20 percent, asks how many stakeholder requirements it serves. Ease of delivery, 25 percent, is scored so that 5 means least effort and least dependence on the contractor. Low risk, 15 percent, asks how unlikely the requirement is to fail or delay the release. Each requirement is scored 1 to 5 on each criterion, and the weighted score adds up the four products of score times weight. Scores were set by the analyst and checked by the estimating lead; two were changed after that check and are marked in the table.
The Scores
The table shows every score and the arithmetic. For FR-1, for example, 0.40 x 5 + 0.20 x 4 + 0.25 x 5 + 0.15 x 4 = 2.00 + 0.80 + 1.25 + 0.60 = 4.65.
| ID | Requirement (short) | Business (0.40) | Breadth (0.20) | Ease (0.25) | Low risk (0.15) | Weighted score | Rank |
|---|---|---|---|---|---|---|---|
| FR-1 | Required fields before submitting | 5 | 4 | 5 | 4 | 4.65 | 1 |
| FR-5 | Clarifications straight to customer, rep copied | 5 | 4 | 4 | 4 | 4.40 | 2 |
| FR-2 | Not sure option routed for advice | 4 | 3 | 4 | 3 | 3.65 | 3 |
| FR-3 | Up to three quantity breaks | 2 | 3 | 5 | 4 | 3.25 | 4 |
| FR-7 | Rep status list | 2 | 2 | 4 | 5 | 2.95 | 5 |
| FR-4 | Record created in estimating module | 4 | 2* | 2 | 2 | 2.80 | 6 |
| FR-8 | Optional draft file upload | 1 | 3 | 3 | 4 | 2.35 | 7 |
| FR-6 | Accepted quote becomes job ticket | 2* | 3 | 2 | 2 | 2.20 | 8 |
The two marked scores were raised or lowered after the estimating lead's review. FR-4's breadth was lowered from 3 to 2, because only estimators benefit directly. FR-6's business score was lowered from 3 to 2, because it does not affect request completeness or waiting time, the two measures the sponsor watches most closely.
Where the Method Gives an Answer the Analyst Would Not Defend
Three results are argued against in the open rather than quietly adjusted. Changing a score after seeing the ranking would hide the disagreement; stating it keeps both the method and the judgment visible.
First, FR-1 and FR-2 are ranked separately, first and third, but they cannot be released separately. A form that demands stock and finishing with no "Not sure" option will push customers who do not know Ridgeline's paper names to guess, which moves the guessing problem from the estimator to the customer, or to abandon the form. The method scores items as independent; these two are one requirement in practice and are released together.
Second, FR-3, quantity breaks, ranks fourth mostly because it is easy. It helps estimators a little but moves none of the business measures much. The ease weight lets cheap, low-value items climb over expensive, important ones, which is a known weakness of scoring that mixes value and cost in one number. It stays in the plan, but not ahead of FR-4.
Third, FR-6 ranks last, and that is the result the analyst would least defend. It scores low because it is hard and does not touch the headline measures. But the current state model found that retyping specifications from quote to job ticket is one of the points where details change, and prepress found mismatches on about 14 percent of jobs. Removing that rekey is also the cheapest time to do it, while the contractor is already working on the estimating link in FR-4. The method measures what the sponsor asked for; it cannot see that FR-4 and FR-6 share most of their build.
The Release Plan That Results
Combining the scores with the three arguments gives a release order in the MoSCoW categories the BABOK guide describes (International Institute of Business Analysis, 2015). Must have for the first release: FR-1 and FR-2 together, and FR-5. Should have, built together in the second release while the contractor is working on the estimating system: FR-4 and FR-6, then FR-7. Could have: FR-3 and FR-8. The first release alone addresses request completeness and the clarification loop, which account for most of the waiting time, and it needs almost no contractor time. Placing FR-4 and FR-6 together also changes the conversation with the chief financial officer, who controls spending above the sponsor's limit: one contractor engagement covering both links is easier to approve and cheaper than two separate ones months apart, and the analyst will present them that way. The ranking will be repeated after the first release, when real completion rates can replace the analyst's scores. Ridgeline Press and every score and date here are composites for this course.
References
Achimugu, P., Selamat, A., Ibrahim, R., & Mahrin, M. N. (2014). A systematic literature review of software requirements prioritization research. Information and Software Technology, 56(6), 568-585. https://doi.org/10.1016/j.infsof.2014.02.001
International Institute of Business Analysis. (2015). A guide to the business analysis body of knowledge (BABOK guide) (Version 3). IIBA.
Karlsson, J., & Ryan, K. (1997). A cost-value approach for prioritizing requirements. IEEE Software, 14(5), 67-74. https://doi.org/10.1109/52.605933
Reading the BU 434 Unit 6 instructions
For the sixth unit, BU 434 asks students to prioritize a set of requirements using a stated technique. Prompts usually require naming the technique and its rules before ranking, applying consistent criteria to every requirement, showing calculations, and interpreting the results. Common methods include MoSCoW, weighted scoring, cost-value analysis and pairwise comparison. Many instructors ask students to discuss where the method's output should be questioned. The result often feeds a release plan. Students should explain how non-functional requirements are handled, since they rarely compete on the same terms. A focused APA 7 paper with a scoring table is typical, and the arguments about the method's weaknesses often carry as much weight as the ranking itself.
How the BU 434 Unit 6 example is put together
The paper begins by explaining what is being prioritized, why the team cannot build everything at once and why non-functional requirements are treated as constraints. It cites a review of prioritization research to justify stating the method openly. A section sets out four criteria, their weights and the scoring rule, agreed and dated before scoring. A table shows every score, the weighted results and ranks, with a worked example and two marked changes explained. The next section argues three results the analyst would not defend and names the property of the method that caused each. The final section converts the ranking and arguments into a MoSCoW release plan and explains the budget benefit of building two links together.
Reading the BU 434 Unit 6 rubric
Prioritization rubrics at Herzing typically reward a clearly described technique, criteria set in advance, consistent application, visible calculations and critical interpretation, plus writing and APA. The technique criterion earns credit for naming and citing the method. Criteria set in advance score highest when weights and scoring rules are explicit and dated. Consistent application is judged by whether every requirement is scored on every criterion. Visible calculations let the instructor check at least one result. The interpretation criterion rewards students who question the output with reasons tied to the method's design. Instructors also look for a practical outcome, such as a release plan, showing the ranking was used rather than merely produced.
Common BU 434 Unit 6 mistakes, and how to avoid them
Prioritization exercises frequently lose points when the ranking appears with no stated method or criteria. Another common problem is choosing weights after scoring, which lets the student produce any order they like. Students often show only final ranks without calculations. Some apply the method and accept every result, missing obvious problems such as dependent items ranked far apart. Others override the method silently by changing scores, hiding the disagreement. Treating non-functional requirements as optional items that can rank low leads to releases that fail basic quality needs. Finally, an exercise that ends with a ranked list and no release decision leaves the reader unsure what the ranking changed.
Get a BU 434 Unit 6 example written to your instructions
Send the Unit 6 instructions and the rubric from your BU 434 classroom, along with the requirement set your section is prioritizing. We write a custom example that fixes the rules first, scores everything on the same criteria, handles dependencies openly and argues the placements worth challenging. First custom sample free, back within 24 to 48 hours.
More BU 434 papers and project management samples
- BU 434 Unit 1: Stakeholder identification and analysis
- BU 434 Unit 2: Elicitation plan
- BU 434 Unit 3: Problem definition
- BU 434 Unit 4: Current state process model
- BU 434 Unit 5: Requirements document
- BU 434 Unit 7: Future state and gap analysis
- BU 434 Unit 8: Traceability and validation plan
- BU 345 Unit 6: Risk response table
- BU 396 Unit 6: Risk register
- BU 433 Unit 6: Ceremony analysis
- BU 436 Unit 6: Supplier and procurement standards
BU 434 Unit 6 questions, answered
Which prioritization method should I pick?
Use the one the instructions name. Where the choice is yours, weighted scoring suits a set with several competing criteria, a category method suits a release conversation, and a pairwise approach suits a short list where nothing obviously separates the items. State the choice and defend it in two sentences. The defense of the method is often worth more than the ranking itself.
Can I override the result the method gives?
Yes, and doing it well is usually where the marks are. What matters is that the override is visible: keep the score as calculated, state the change, and give the reason, whether that is a dependency, a regulatory deadline in the case or a commitment already made. What loses points is quietly adjusting a score until the arithmetic agrees with the answer you wanted.
Our team has a ranked backlog. May I use it?
No. A ranked backlog encodes what your employer decided to fund and why, and that reasoning is commercial information alongside the elicitation notes, interview recordings and requirements files it grew out of. Score the requirements from the assignment case using criteria you can defend from the course material. Your instinct for what usually ranks high is yours to keep; the company's list is not.
Where can I find a free BU 434 Unit 6 sample paper?
The whole BU 434 Unit 6 prioritization exercise is free above, with the criteria, the full scoring table, three argued overrides and margin notes. For your own requirements or method, tell us what your assignment asks and we will prepare a custom exercise for free, typically within 48 hours.
Can I override the method's result in BU 434 Unit 6?
Yes, openly. The sample keeps every score visible and then argues three results it would not defend, naming the weakness in the method behind each. Silent changes to scores hide the disagreement and usually cost points.