Project team

About: Project team is a research topic. Over the lifetime, 6443 publications have been published within this topic receiving 97558 citations.

An empirical investigation of the factors affecting data warehousing success

Abstract: The IT implementation literature suggests that various implementation factors play critical roles in the success of an information system; however, there is little empirical research about the implementation of data warehousing projects. Data warehousing has unique characteristics that may impact the importance of factors that apply to it. In this study, a cross-sectional survey investigated a model of data warehousing success. Data warehousing managers and data suppliers from 111 organizations completed paired mail questionnaires on implementation factors and the success of the warehouse. The results from a Partial Least Squares analysis of the data identified significant relationships between the system quality and data quality factors and perceived net benefits. It was found that management support and resources help to address organizational issues that arise during warehouse implementations; resources, user participation, and highly-skilled project team members increase the likelihood that warehousing projects will finish on-time, on-budget, with the right functionality; and diverse, unstandardized source systems and poor development technology will increase the technical issues that project teams must overcome. The implementation's success with organizational and project issues, in turn, influence the system quality of the data warehouse; however, data quality is best explained by factors not included in the research model.

The Logical Framework Method for Defining Project Success

Abstract: Project success is a core concept of project management but its definition remains elusive. The project team must have a clear understanding of their project success objectives. This paper uses the...

Success Factors for Integrating Suppliers into New Product Development

Abstract: Faster, better, cheaper—these marching orders summarize the challenge facing new product development (NPD). In other words, NPD teams must find the means for speeding time to market while also improving product quality and reducting product costs. Cross-functional teams have proved effective for meeting these challenges, and such teams may extend beyond company boundaries to include key materials suppliers. Effective integration of suppliers into NPD can yield such benefits as reduced cost and improved quality of purchased materials, reduced product development time, and improved access to and application of technology. As Gary Ragatz, Robert Handfield, and Thomas Scannell point out, however, those benefits do not automatically accrue to any NPD team that includes representatives from a supplier's company. In a study of 60 member companies from the Michigan State University Global Procurement and Supply Chain Electronic Benchmarking Network, they explore the management practices and the environmental factors that relate most closely to successful integration of suppliers into the NPD process. The study identifies supplier membership on the NPD project team as the greatest differentiator between most and least successful integration efforts. Although the respondents reported only moderate use of shared education and training, the study cites this management factor as another significant differentiator between most and least successful efforts. Respondents listed direct, cross-functional, intercompany communication as the most widely used technique for integrating suppliers into NPD. To integrate suppliers into NPD, a company must overcome such barriers as resistance to sharing proprietary information, and the not-invented-here syndrome. The results of this study suggest that overcoming such barriers depends on relationship structuring—that is, shared education and training, formal trust development processes, formalized risk/reward sharing agreements, joint agreement on performance measurements, top management commitment from both companies, and confidence in the supplier's capabilities. Overcoming these barriers also depends on assett sharing, including intellectual assets such as customer requirements, technology information, and cross-functional communication; physical assets such as linked information systems, technology, and shared plant and equipment; and human assets such as supplier participation on the project team and co-location of personnel.

On Uncertainty, Ambiguity, and Complexity in Project Management

Abstract: This article develops a model of a project as a payoff function that depends on the state of the world and the choice of a sequence of actions. A causal mapping, which may be incompletely known by the project team, represents the impact of possible actions on the states of the world. An underlying probability space represents available information about the state of the world. Interactions among actions and states of the world determine the complexity of the payoff function. Activities are endogenous, in that they are the result of a policy that maximizes the expected project payoff.A key concept is theadequacy of the available information about states of the world and action effects. We express uncertainty, ambiguity, and complexity in terms of information adequacy. We identify three fundamental project management strategies: instructionism, learning, and selectionism. We show that classic project management methods emphasize adequate information and instructionism, and demonstrate how modern methods fit into the three fundamental strategies. The appropriate strategy is contingent on the type of uncertainty present and the complexity of the project payoff function. Our model establishes a rigorous language that allows the project manager to judge the adequacy of the available project information at the outset, choose an appropriate combination of strategies, and set a supporting project infrastructure--that is, systems for planning, coordination and incentives, and monitoring.

Antecedents and consequences of project team cross-functional cooperation

Abstract: Cross-functional teams can greatly facilitate the successful implementation of projects This study examined the influence of a set four antecedent constructs (superordinate goals, accessibility, physical proximity and formalized rules and procedures) on the attainment of both cross-functional cooperation and perceived project outcomes Through the use of path analysis, the results indicated that superordinate goals, physical proximity and project team rules and procedures have significant direct and/or indirect effects on project outcomes through influencing cross-functional cooperation Further, cross-functional cooperation was a significant predictor of both perceived task and psychosocial project outcomes Directions for management practice and future research are discussed