| Course | BUS 660 Quantitative Methods |
|---|---|
| Topic | Topic 3 |
| Paper type | Forecasting method comparison |
| Length | About 950 words, 2 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | MBA |
| Updated | October 2026 |
Free sample paper for BUS 660 Topic 3
Forecast the Past Before the Future: Comparing Moving Averages, Smoothing and a Trend Line on Twelve Weeks of Bread Orders
[Author Name]
Colangelo College of Business, Grand Canyon University
BUS-660: Quantitative Methods
Topic 3 Forecasting Method Comparison
[Instructor Name]
[Date]
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
Forecast the Past Before the Future: Comparing Moving Averages, Smoothing and a Trend Line on Twelve Weeks of Bread Orders
The Task
A composite regional bakery needs a forecast of next week's orders for its standard sandwich loaf, because flour orders and shift schedules are set a week ahead. It has twelve weeks of orders: 4,200, 4,350, 4,100, 4,500, 4,650, 4,400, 4,800, 4,950, 4,700, 5,100, 5,250 and 5,050 loaves. This analysis applies several forecasting methods to the history, compares each method's forecasts with what actually happened, chooses a method on numerical evidence and forecasts forward with a range. Figures are illustrative.
The Methods
Three kinds of method are compared. A three-week moving average forecasts each week as the average of the previous three. Exponential smoothing forecasts each week as last week's forecast plus a fraction, the smoothing constant, of last week's error; the constant is not assumed but tested at 0.1, 0.3, 0.5 and 0.7. A linear trend line fits a straight line through the twelve weeks and extends it (Render et al., 2018). Each method's forecasts for weeks 4 through 12 are compared with the actual orders.
Two Error Measures
The comparison uses two error measures, because they judge errors differently. Mean absolute deviation averages the size of the errors, treating a miss of 400 loaves as twice as bad as a miss of 200. Mean squared error averages the squared errors, treating a miss of 400 as four times as bad as a miss of 200. Choosing between them is a business judgment about which kind of error hurts. For the bakery, a large shortfall means empty grocery shelves and a lost account, which is far worse than two small shortfalls, so mean squared error deserves weight. Hyndman and Koehler (2006) review the strengths and weaknesses of common accuracy measures and recommend choosing them with the forecast's use in mind.
Table 1
Forecast Errors for Weeks 4 to 12 and Forecasts for Week 13
| Method | Mean absolute deviation, loaves | Mean squared error | Forecast for week 13 |
|---|---|---|---|
| Three-week moving average | 213 | About 64,000 | About 5,133 |
| Smoothing, constant 0.1 | 463 | About 250,000 | About 4,620 |
| Smoothing, constant 0.3 | 284 | About 109,000 | About 4,967 |
| Smoothing, constant 0.5 | 245 | About 75,000 | About 5,068 |
| Smoothing, constant 0.7 | 252 | About 69,000 | About 5,087 |
| Linear trend | 136 | About 21,000 | About 5,279 |
Reading the Comparison
The data rise steadily, about 94 loaves a week on the trend line, with weekly ups and downs. Methods that react slowly lag behind the rise: smoothing with a constant of 0.1 trails badly, with errors more than twice those of the others. Higher smoothing constants react faster and do better, and the two measures disagree on which is best: a constant of 0.5 has the lower mean absolute deviation, and 0.7 the lower mean squared error, because 0.7 avoids some of the larger misses. That disagreement shows why the choice of measure matters. The moving average, which also lags a trend, does better than any smoothing constant on both measures here.
The trend line has much the lowest errors on both measures. Part of that advantage is unfair: the line was fitted using all twelve weeks, including those it is being scored on, while the other methods forecast each week using only earlier data. A fairer test refits the trend each week using only the preceding weeks; doing so raises its mean absolute deviation to about 222 loaves, slightly above the moving average's 213, while its mean squared error, about 54,000, remains the lowest of any method. Because the bakery weights large misses heavily, the refitted trend still comes out ahead. Hyndman and Athanasopoulos (2021) describe this kind of evaluation on data not used to fit the model as essential, because in-sample fit flatters every method.
Checks Before Fitting
Before any method is compared, the history itself should be checked. Orders in the sixth week dipped to 4,400 because a grocery customer's warehouse was closed for a day, not because demand fell; an analysis could reasonably adjust that week before fitting, though this one leaves it in to stay conservative. Orders also record what customers asked for, not what they would have bought if the bakery had more capacity, so a week in which the bakery turned orders away would understate demand. Neither problem is visible in the numbers alone, which is why the person forecasting should talk to the sales team before trusting the series.
The Forecast and Its Range
The analysis recommends the trend method, refitted each week, for this product while orders keep rising, and forecasts about 5,280 loaves for week 13. A point forecast presented alone would be treated as more certain than it is. Based on the refitted trend's errors, the bakery should plan for roughly 5,000 to 5,560 loaves, about 1.25 times its mean absolute deviation either side of the forecast, which approximates one standard deviation of error. Flour and staffing should be planned to the point forecast with enough flexibility to cover the upper end of the range.
When the Choice Would Change
The trend method is right only while the trend continues. If a grocery chain's promotion ended or summer brought the usual dip in sandwich-bread demand, a method that assumes steady growth would overshoot. The analysis recommends tracking the weekly forecast error and switching to a smoothing method, or adding a seasonal adjustment once a full year of data exists, if the errors begin to run consistently in one direction.
Conclusion
Forecasting the past first shows that slow methods lag the rising orders and that the trend line, tested fairly, makes the fewest large misses. Two error measures rank the smoothing constants differently, which makes the choice of measure a business decision. Next week's forecast is about 5,280 loaves, with a planning range of about 5,000 to 5,560.
References
Hyndman, R. J., & Athanasopoulos, G. (2021). Forecasting: Principles and practice (3rd ed.). OTexts. https://otexts.com/fpp3/
Hyndman, R. J., & Koehler, A. B. (2006). Another look at measures of forecast accuracy. International Journal of Forecasting, 22(4), 679-688. https://doi.org/10.1016/j.ijforecast.2006.03.001
Render, B., Stair, R. M., Hanna, M. E., & Hale, T. S. (2018). Quantitative analysis for management (13th ed.). Pearson.
BUS 660 Topic 3 instructions, in plain terms
Topic 3 of BUS-660 asks MBA students to compare forecasting methods. Strong comparisons apply each method to the historical series, compare predictions with actual results using more than one error measure, and explain that the choice of measure reflects which errors hurt the business. Students should test smoothing constants rather than assume one, evaluate methods fairly on data not used to fit them, check the data for problems before fitting, and forecast forward with a range rather than a single number. The analysis should say when it would switch methods. Students should also check the history for unusual weeks before fitting any method, and explain how an outlier distorts each error measure.
Inside the BUS 660 Topic 3 example
The finished example forecasts the past before it forecasts the future. Each method is applied to the historical series, its predictions are compared against what actually happened, and an error measure is computed so the comparison is numerical rather than visual. More than one error measure appears, since a measure that squares errors punishes large misses far more heavily than one that does not, and the choice between them is itself a business judgment about which kind of error hurts. The smoothing constant is not assumed but tested at several values. The example finishes by forecasting forward and attaching a range, because a point forecast presented alone will be treated as more certain than it is.
BUS 660 Topic 3 rubric: what Excellent looks like
Faculty reward forecasting the past before the future. An Excellent paper scores six methods on both error measures in a table. Credit goes to showing that mean absolute deviation and mean squared error rank the smoothing constants differently, with Hyndman and Koehler on choosing measures. The rubric values refitting the trend on earlier weeks only, following Hyndman and Athanasopoulos. Strong papers check the history for a closed-warehouse week and turned-away orders. Top marks go to a forecast with a stated planning range and a rule for switching methods. Papers that refit the chosen method each week and say when the bakery should switch methods, rather than naming a winner once, show forecasting treated as a process.
Common BUS 660 Topic 3 mistakes, and how to avoid them
Choosing a method with no accuracy comparison is the shortfall this topic exists to prevent, since preference and familiarity are not evidence. A second failure is a single error measure reported as though it settled the question, when different measures rank methods differently and the choice between them reflects a business judgment. Papers lose marks for applying a method that cannot represent the pattern in the data, such as a simple average on a series with obvious trend, without noticing why it fails. Adopting a default smoothing constant without testing alternatives leaves an arbitrary choice carrying the forecast. Point forecasts reported with no range invite a confidence the method does not support.
Get a BUS-660 Topic 3 example written to your instructions
Send the BUS-660 Topic 3 problems and the rubric your classroom posts, with the time series your section supplied. We write a custom example to those criteria, with every method tested on the history, more than one error measure reported, the smoothing constant tuned and a range attached to the forecast, in 24 to 48 hours. The first is free.
More BUS 660 papers and MBA samples
- BUS 660 Topic 1: Payoff Table Analysis
- BUS 660 Topic 2: Decision Tree Analysis
- BUS 660 Topic 4: Predictive Regression Model
- BUS 660 Topic 5: Linear Programming Formulation
- BUS 660 Topic 6: Network Optimization Problem
- BUS 660 Topic 7: Simulation and Inventory Analysis
- BUS 660 Topic 8: Project Scheduling Recommendation
- BUS 655 Topic 3: Price Elasticity Estimate
- BUS 635 Topic 3: Sponsorship Valuation Proposal
- ACC 650 Topic 3: Activity Based Costing Analysis
- HRM 635 Topic 3: Build Versus Buy Cost Case
BUS 660 Topic 3 questions, answered
How do I compare forecasting methods fairly?
Run each one over the same historical periods and measure how far its predictions sat from what actually occurred. That converts a preference into a number. Use the same periods for every method, since a method evaluated over a calmer stretch will look better for reasons that have nothing to do with its quality, and report the comparison as a table rather than as a conclusion.
Which error measure should I use?
Depends on how much large misses hurt your business. A measure that squares the errors weights big misses heavily, which suits a situation where a large stockout is disproportionately damaging. A measure using absolute values treats all errors proportionally. A percentage measure lets you compare across products of different sizes. Report at least two and say which matters here.
How do I choose a smoothing constant?
By testing it rather than accepting a default. Run the method at several values across your history and see which minimizes the error measure you care about. A higher value makes the forecast respond faster to recent movement and also to noise; a lower one is stable and slow to react. The trade is real and the data will tell you where it sits for this series.
Where can I find a free BUS 660 Topic 3 sample paper?
The forecasting comparison appears here complete: the task, the methods, two error measures, reading the comparison, checks before fitting, the forecast and its range, when the choice would change and the conclusion. Share your series and we will compare methods free.
Why use two error measures in BUS 660 Topic 3?
Mean absolute deviation weighs errors by size while mean squared error punishes large misses far more. For a bakery, a big shortfall can lose an account, so large misses deserve extra weight.