مدیریت پروژه های توسعه محصول پیچیده با طراحی ماتریس های ساختار و ماتریس های نقشه برداری دامنه
|کد مقاله||سال انتشار||تعداد صفحات مقاله انگلیسی||ترجمه فارسی|
|2711||2007||15 صفحه PDF||سفارش دهید|
نسخه انگلیسی مقاله همین الان قابل دانلود است.
هزینه ترجمه مقاله بر اساس تعداد کلمات مقاله انگلیسی محاسبه می شود.
این مقاله تقریباً شامل 6840 کلمه می باشد.
هزینه ترجمه مقاله توسط مترجمان با تجربه، طبق جدول زیر محاسبه می شود:
Publisher : Elsevier - Science Direct (الزویر - ساینس دایرکت)
Journal : International Journal of Project Management, Volume 25, Issue 3, April 2007, Pages 300–314
Complexity in product development (PD) projects can emanate from the product design, the development process, the development organization, the tools and technologies applied, the requirements to be met, and other domains. In each of these domains, complexity arises from the numerous elements and their multitude of relationships, such as between the components of the product being developed, between the activities to develop them, and among the people doing the activities. One approach to handing this complexity is to represent and analyze these domains’ design structures or architectures. The design structure matrix (DSM) has proved to be a very helpful tool for representing and analyzing the architecture of an individual system such as a product, process, or organization. Like many tools, the DSM has been applied in a variety of areas outside its original domain, as researchers and practitioners have sought to leverage its advantages. Along the way, however, its fundamental rules (such as being a square matrix) have been challenged. In this paper, we formalize an approach to using a domain mapping matrix (DMM) to compare two DSMs of different project domains. A DMM is a rectangular (m × n) matrix relating two DSMs, where m is the size of DSM1 and n is the size of DSM2. DMM analysis augments traditional DSM analyses. Our comparison of DSM and DMM approaches shows that DMM analysis offers several benefits. For example, it can help (1) capture the dynamics of PD, (2) show traceability of constraints across domains, (3) provide transparency between domains, (4) synchronize decisions across domains, (5) cross-verify domain models, (6) integrate a domain with the rest of a project or program, and (7) improve decision making among engineers and managers by providing a basis for communication and learning across domains.
1.1. Background Complexity in product development (PD) projects stems from many sources. The product or service to be developed (the deliverable) may be complex in its function, form, integration, technology, etc. The work required to develop it is often complex in its number of activities, people, teams, and organizations involved and their relationships. These areas are interwoven, creating a number of complexities and uncertainties for managers. In our view, managers should focus on identifying, understanding, and reducing these product, process, and organizational uncertainties, among others, to add value. Complexity can be identified and handled, and uncertainty reduced, by using a systematic approach to gathering, organizing, integrating, and analyzing the best information about a project. Models and tools that enable this also provide a basis for planning and learning  and . However, models must be based upon the latest and most accurate input information if they are to provide helpful output. Hence, trans-disciplinary or cross-functional teams are advocated to provide the collective expertise, information, and resources for effective model building and problem solving. However, such intensive interaction between people often causes conflicts because of variations in experience, knowledge, organizational or professional loyalty, understanding of the purpose and goals, and/or contradictory purposes and goals. Each project stakeholder has a different mental model of the project, assumptions about it, interpretations of realities, expectations, etc. A shared, codified model can test and align participants’ mental models through discussions and lead to joint understanding of the reality in PD projects. To coordinate agents effectively into teams in the dynamic environment of PD, within and across different domains as indicated above, our research explores the following idea: we must lay bare the assumptions about the nature of the desired result, the activities to get to it, and the organization that will do the work, and the logic by which these domains have been decomposed and integrated. PD projects are dynamic ones in which different domains are interwoven and effective management requires understanding how they interrelate and influence each other. Fig. 1 illustrates some critical aspects of PD that dynamically relate to each other. Product specifications are a consequence of customer requirements as well as logistic and manufacturing system capabilities. It is an illusion that PD starts solely with customer requirements and ends in design of the product structure. In reality this process is like a web. Domains are interrelated and information is flowing back and forth between them. The crucial aspect here is to understand and explore dependencies and the need for information exchange between different domains of product architectures, organizations and processes. The problem for managers is to find the appropriate way to organize people and assign work over time, enable communication, and synchronize actions. The implication of such a dynamic approach is that managers and engineers must understand and take into account interdependencies and relations, and the information that needs to be exchanged, not only within each domain but also across domains. PD projects contain at least five different domains (Fig. 2): the product (or service, or result) system; the process system (and the work done to get the product system); the system organizing the people into departments, teams, groups, etc.; the system of tools, information technology-solutions, and equipment they use to do the work; and the system of goals, objectives, requirements, and constraints pertaining to all the systems. Each of these five systems is composed of elements with relationships and thus can be discussed in terms of its structure, network, and architecture—where architecture is defined, for example, as: “the structure of components, their relationships, and the principles and guidelines governing their design and evolution over time” (IEEE STD 610.12). Moreover, each of the five systems is related to the others. Each system both enables and constrains the others. 1.2. Motivation for our research An enterprise typically has multiple projects going on at once (represented by the layers in the Fig. 2), and there are strong incentives to achieve commonality in these five systems across projects. In multi-project situations, each project usually does not have full control over its organizational structure, product architecture, process structure, etc., since companies usually want some commonality in these across projects to provide economies of scale and scope and easy project comparison. For example, they want organizational commonality so that the employee evaluation and promotion process is similar, product commonality so that all of the company’s products have similar themes, process commonality so that standard processes can be used and people can be assigned to work on multiple projects without having to learn an entirely different process, tool (especially information technology) commonality to provide economies of scale in purchasing software and training employees, etc. In spite of all of these limitations, projects have to be coordinated in order to produce a complete result—a product, a service, etc. However, when a project fails, it is often because someone forgot to account for the effects of some of these systems and their implications. And this should not be surprising, because there is a tremendous amount of information to consider and manage. In multi-project situations it is crucial to examine interfaces between projects and their needs for information exchange , , , ,  and . However, this is necessary in and across all of the domains. It is therefore essential to have a technique for examining the relationships between the elements of these systems. 1.3. Outline of the paper In this paper, we compare two complementary, matrix-based approaches for representing, analyzing, and managing the crucial information regarding project domains and their interactions. The first, the design structure matrix (DSM), is a square matrix that has been used in a variety of product, process, and organization modelling applications over the last twenty years. We formalize the domain mapping matrix (DMM) as a second type of matrix-based approach, used to map between two different project domains. A DMM is a rectangular (m × n) matrix relating two DSMs, where m is the size of DSM1 and n is the size of DSM2. DMM analysis augments and adds insights to traditional DSM analyses. Our comparison of DSM and DMM approaches shows that DMM and DSM–DMM analyses offer a number of managerial insights and benefits. The rest of this paper is organized as follows. Section 2 presents the DSM and DMM as two matrix-based tools for organizing the information that drives complexity within and across the five domains in PD. Section 3 compares and contrasts the DSM and DMM. Section 4 presents three example applications, Section 5 provides further discussion and insights, and Section 6 concludes the paper.
نتیجه گیری انگلیسی
In this paper, we have provided information and comparisons between traditional DSM approaches and the cross-domain DMM approach that show their complementary nature and mutual advantages. We harness dependency matrix approaches to represent and analyze the structure of elements and their interactions both within and across PD project domains. Since the traditional DSM focuses on a single domain, its analysis yields insights deemed optimal from the point of view of that domain only. However, the DMM provides way to represent interactions and relations between domains. We summarize the following points in comparing DSMs and DMMs: • Traditional DSM analysis focuses on dependencies and flows of information in one domain. These single-domain analyses can be carried out in different domains simultaneously, but these analysis do not reflect the dynamics of PD and the need for transformation and comparison of information in one domain to another. • Dual-domain DMM analysis reflects the dynamics of PD and enables transformation and traceability of information between domains. Performing DMM analysis between domains can ensure that information captured in one domain is not forgotten, added or dropped in another. • Cross-domain verification of system models and project assumptions is possible when DMM analysis is performed in different domains. • DMM analysis enables information from different domains to be communicated and understood by a variety of project participants, including engineers, marketers, manufacturers, financiers, and managers. During domain comparisons, information updates in one domain are transparent to everyone and almost automatically updated in other domains. • While all DSMs are square matrices, not all rectangular matrices are DMMs, and some DMMs may be square matrices. The most important characteristic of a DMM is that one domain is mapped against another. Used together, DSMs and DMMs increase our knowledge and understanding of approaches to analyzing dependences in complex systems and thereby facilitate the reduction of uncertainty and ambiguity in PD projects.