A

Alan Miller

Boeing (United States)

Publishes on Agricultural Economics and Policy, Genetically Modified Organisms Research, Auditing, Earnings Management, Governance. 29 papers and 98 citations.

29Publications
98Total Citations

Is this you? Claim your profile.

Add your photo, update your bio, and get notified when your ranking changes.

Top publicationsby citations

RISK MANAGEMENT FOR FARMERS
Alan Miller, Craig L. Dobbins, James G. Pritchett et al.|AgEcon Search (University of Minnesota, USA)|2004
Cited by 40Open Access

Risk is present in all decisions, though often its assessment is skewed to the negative effects. This paper presents material on the sources of risk in agriculture, procedures for managing two types of risks (operational and strategic) and the interaction of time and risk.

Farm Enterprise Analysis: Has It Lost Its Usefulness?
Alan Miller, Freddie L. Barnard, Norman Brown et al.|AgEcon Search (University of Minnesota, USA)|2010
Cited by 2Open Access

Farm enterprise analysis is a term that has traditionally been used to describe the process of determining costs associated with farm business enterprises and enterprise profitability. A key challenge to those who would know their costs has been the lack of guidance on cost accounting principles and the application of those principles to agriculture. However, that recently changed with the publication of the Farm Financial Standards Council’s Management Accounting Principles for Agricultural Producers, which has led to questions about the usefulness of enterprise analysis. The differences between the two approaches to determining costs for farm business enterprises are discussed as they relate to the usefulness of the output to managers for decision making.

Customer requirements and user requirements: why the discrepancies?
M. Deraitus, Alan Miller|Journal of Lightwave Technology|2004
Cited by 1

Development teams often speak about the need to satisfy the customer and to meet their requirements. But exactly who is the customer, how do they determine their requirements, and how do these differ from user requirements? If the customer requirements don't realistically (or objectively) present user requirements, can the developers still build a usable product? And if not, who's to blame when the product meets the requirements of the customer, but not the user?.