2001
DOI: 10.1016/s0923-4748(00)00034-5
|View full text |Cite
|
Sign up to set email alerts
|

The accountant’s contribution to product development teams — a case study

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
19
0

Year Published

2012
2012
2023
2023

Publication Types

Select...
6
1

Relationship

0
7

Authors

Journals

citations
Cited by 20 publications
(20 citation statements)
references
References 2 publications
1
19
0
Order By: Relevance
“…People who conduct the (financial) evaluation of alternative supplier offerings have various job titles, such as “initial buyer,” or “cost analyst,” so we refer to them collectively as “cost analysts.” We compare and contrast their perspective with that of project leaders and key stakeholders within any NPD project. We expect that cost analysts put more emphasis on monetary quantification for achieving NPD project success, while project leaders rely more on nonmonetary, quantitative, and qualitative information (Rabino, ). Even when not all of the supporting details can be expressed in monetary terms, project leaders may find these details useful, for instance, in their arguments to senior management (e.g., quantitative nonmonetary estimates, such as faster cycle times or higher yields).…”
Section: Model Developmentmentioning
confidence: 99%
“…People who conduct the (financial) evaluation of alternative supplier offerings have various job titles, such as “initial buyer,” or “cost analyst,” so we refer to them collectively as “cost analysts.” We compare and contrast their perspective with that of project leaders and key stakeholders within any NPD project. We expect that cost analysts put more emphasis on monetary quantification for achieving NPD project success, while project leaders rely more on nonmonetary, quantitative, and qualitative information (Rabino, ). Even when not all of the supporting details can be expressed in monetary terms, project leaders may find these details useful, for instance, in their arguments to senior management (e.g., quantitative nonmonetary estimates, such as faster cycle times or higher yields).…”
Section: Model Developmentmentioning
confidence: 99%
“…Several surveys investigate the antecedents or consequences (Afonso, Nunes, Paisana, & Braga, 2008;Liker, Kamath, Wasti, & Nagamachi, 1996;Petersen, Handfield, & Ragatz, 2003;Plank & Ferrin, 2002;Rabino, 2001;Yazdifar & Askarany, 2012) of target costing or related cost management methods.…”
Section: Empirical: Observationsmentioning
confidence: 99%
“…Integration is an important theme in these studies on target costing: cross-functional integration within the organization (Rabino, 2001;Zengin & Ada, 2010) and interorganizational toward suppliers (Liker et al, 1996;Petersen et al, 2003;Ro et al, 2007), or with customers (Hoque, Akter, & Monden, 2005;Ibusuki & Kaminski, 2007;Plank & Ferrin, 2002).…”
Section: Empirical: Observationsmentioning
confidence: 99%
“…The existing literature offers insufficient understanding about how different organizational members perceive and manage uncertainties related to project portfolios. Different managerial roles within portfolio management might stem from different organizational responsibility structures that have an influence on management control systems, and how they are perceived among managers (see, e.g., Burchell, Clubb, Hopwood, Hughes, & Nahapiet, ; Mia & Chenhall, )—which possibly moderates designing and using controls in cross‐functional teams that product development activities are likely to be organized in (Rabino, ). The viewpoint of context‐dependence is also central to PPM: “Program and portfolio management is […] not uniform and needs to be adapted to an organization's situation, given through its particular environment and business type.…”
Section: Different Managerial Roles In Product Development Project Pomentioning
confidence: 99%
“…We inter‐viewed managers in the positions of a product manager, business controller, R&D director, and project manager in order to acquire multi‐perspective data from portfolio, program, and project management roles (following Blomquist & Müller, ). With this empirical setting, we try to avoid the single informant bias mentioned, for example, by Teller (, p. 48) who promoted examining portfolio‐level risks by analyzing project and portfolio managers; we also include stakeholders from outside the project management office (Jerbrant & Gustavsson, ); in other words, from business and financial management (Rabino, ). We contribute to the PPM literature by highlighting the variety of managers relevant to identifying and managing uncertainty stemming from the environment, organi‐zational complexity, and single projects, with the help of management control systems.…”
Section: Introductionmentioning
confidence: 99%