58 resultados para Project Management Maturity Model
Resumo:
As levels of investment in advanced manufacturing systems increase, effective project management becomes ever more critical. This paper demonstrates how the model proposed by Mintzberg, Raisinghani and Theoret in 1976, which structures complicated strategic decision processes, can be applied to the design of new production systems for both descriptive and analytical research purposes. This paper sets a detailed case study concerning the design and development of an advanced manufacturing system within the Mintzberg decision model and so breaks down the decision sequence into constituent parts. It thus shows how a structured model can provide a framework for the researcher who wishes to study decision episodes in the design of manufacturing facilities in greater depth.
Resumo:
The control needed in the management of a project was analysed with particular reference to the unique needs of the construction industry within the context of site management. This was explored further by analysing the various problems facing managers within the overall system and determining to what extent the organisation would benefit from an integrated mangement information system. Integration and management of information within the organisational units and the cycles of events that make up the main sub-system was suggested as the means of achieving this objective. A conceptual model of the flow of information was constructed within the whole process of project management by examining the type of information and documents which are generated for the production cycle of a project. This model was analysed with respect to the site managers' needs and the minimum requirements for an overall integrated system. The most tedious and time-consuming task facing the site manager is the determination of weekly production costs, calculation and preparation of interim certificates and valuation of variations occurring during the production stage and finally the settlement and preparation of supplier and sub-contractors' accounts. These areas where microcomputers could be of most help were identified and a number of packages were designed and implemented for various contractors. The gradual integration of stand-alone packages within the whole of the construction industry is a logical sequence to achieve integration of management system. The methods of doing this were analysed together with the resulting advantages and disadvantages.
Resumo:
The research described here concerns the development of metrics and models to support the development of hybrid (conventional/knowledge based) integrated systems. The thesis argues from the point that, although it is well known that estimating the cost, duration and quality of information systems is a difficult task, it is far from clear what sorts of tools and techniques would adequately support a project manager in the estimation of these properties. A literature review shows that metrics (measurements) and estimating tools have been developed for conventional systems since the 1960s while there has been very little research on metrics for knowledge based systems (KBSs). Furthermore, although there are a number of theoretical problems with many of the `classic' metrics developed for conventional systems, it also appears that the tools which such metrics can be used to develop are not widely used by project managers. A survey was carried out of large UK companies which confirmed this continuing state of affairs. Before any useful tools could be developed, therefore, it was important to find out why project managers were not using these tools already. By characterising those companies that use software cost estimating (SCE) tools against those which could but do not, it was possible to recognise the involvement of the client/customer in the process of estimation. Pursuing this point, a model of the early estimating and planning stages (the EEPS model) was developed to test exactly where estimating takes place. The EEPS model suggests that estimating could take place either before a fully-developed plan has been produced, or while this plan is being produced. If it were the former, then SCE tools would be particularly useful since there is very little other data available from which to produce an estimate. A second survey, however, indicated that project managers see estimating as being essentially the latter at which point project management tools are available to support the process. It would seem, therefore, that SCE tools are not being used because project management tools are being used instead. The issue here is not with the method of developing an estimating model or tool, but; in the way in which "an estimate" is intimately tied to an understanding of what tasks are being planned. Current SCE tools are perceived by project managers as targetting the wrong point of estimation, A model (called TABATHA) is then presented which describes how an estimating tool based on an analysis of tasks would thus fit into the planning stage. The issue of whether metrics can be usefully developed for hybrid systems (which also contain KBS components) is tested by extending a number of "classic" program size and structure metrics to a KBS language, Prolog. Measurements of lines of code, Halstead's operators/operands, McCabe's cyclomatic complexity, Henry & Kafura's data flow fan-in/out and post-release reported errors were taken for a set of 80 commercially-developed LPA Prolog programs: By re~defining the metric counts for Prolog it was found that estimates of program size and error-proneness comparable to the best conventional studies are possible. This suggests that metrics can be usefully applied to KBS languages, such as Prolog and thus, the development of metncs and models to support the development of hybrid information systems is both feasible and useful.
Resumo:
Using a wide range of operational research (OR) optimization examples, Applied Operational Research with SAS demonstrates how the OR procedures in SAS work. The book is one of the first to extensively cover the application of SAS procedures to OR problems, such as single criterion optimization, project management decisions, printed circuit board assembly, and multiple criteria decision making. The text begins with the algorithms and methods for linear programming, integer linear programming, and goal programming models. It then describes the principles of several OR procedures in SAS. Subsequent chapters explain how to use these procedures to solve various types of OR problems. Each of these chapters describes the concept of an OR problem, presents an example of the problem, and discusses the specific procedure and its macros for the optimal solution of the problem. The macros include data handling, model building, and report writing. While primarily designed for SAS users in OR and marketing analytics, the book can also be used by readers interested in mathematical modeling techniques. By formulating the OR problems as mathematical models, the authors show how SAS can solve a variety of optimization problems.
Resumo:
Customer relationship management (CRM) implementation projects reflect a growing conceptual shift from the traditional engineering view of projects. Such projects are complex and risky because they call for both organisational and technological changes. This requires effective project management across various phases of the implementation process. However, few empirical researches have dealt with these project management issues. The aim of this research is to investigate how a “project team” manages CRM implementation projects successfully, across the different phases of the implementation process. We conducted an in-depth case study of the “Firm-Clients Branch” of a large telecommunications company in France. The findings show that, to manage CRM implementation projects successfully, an integrated and balanced approach is required. This involves appropriate system selection, effective process re-engineering and further development of organizational structures. We highlight the need for a “technochange approach” to achieve successful organisational transition and effective CRM implementation. The study reveals that the project team plays a central role throughout the implementation phases. Furthermore the effectiveness of technochange depends on project team performance, technology efficiency and close coordination with stakeholders.
Resumo:
The eighth edition is a fundamental and essential update to the seventh edition published in 2000. This new edition examines a comprehensive range of existing and newer topics that are relevant to project financing in 2012 and explores current trends in the project finance and leasing industries. Contributors are experienced academics and practitioners. Since the first edition was published, the financial markets have undergone tremendous upheavals and many new structures and instruments have been created to meet the financing needs of business. This edition considers the wider world of project finance, applicable to such diverse situations as venture capital and leveraged buyouts, and using new approaches such as Islamic finance techniques. The eighth edition is an essential and over-due update to the previous edition published in 2000. The eighth edition updates a comprehensive review of financial and related topics which are relevant to project financing in 2012 and explores current trends in financial modelling of a project, risk management and the private finance initiatives. This is a comprehensive and practical book full of advice and tips for successful project financing, including leasing, offering a clear, easy to understand guide to a complex area with examples. The topic coverage is well organized and complete moving from the fundamentals to the more complex issues. There is an extensive glossary to support readers. Finally the use of 12 practitioner case studies brings many of these complex issues to life. This is the new edition of the clear, easy-to-understand industry-standard text on project financing. With a good overview of a broad area and using principles of project financing to explain complex structures, this book includes lots of examples and case studies (including Eurotunnel, Dabhol, multiple Paiton deals and other recent deals along with subsequent developments) to show the concepts in use, examine outcomes and to ensure you understand important issues such as effective project structuring and financing, financial modelling for project valuation, and risk management. Substantially updated and expanded to provide the latest developments in all aspects of project financing. An important manual reference, this book is a must-have for every project financier's desk. The text unites the domain of project financing with a wealth of project management techniques, supported by diagrams and charts and other pictorial features, where appropriate. All these supporting features facilitate a better understanding of the accompanying text for the reader. In many chapters there are diagrams to clarify the specific transaction structure discussed in the accompanying text. These diagrams enable the reader to get a very clear idea of the transaction structure, which is particularly useful where it is complex or unusual. There are also a number of checklists to assist stakeholders in the project and resource management of complex project financings. The new financial modelling chapters allow exploration of some of the pitfalls project models encounter, challenging the accurate replication of the project cash flows for stakeholders to evaluate. In the later new risk management chapters, worked examples are included to illustrate the techniques in practice. The new public private partnership/private finance initiatives chapter introduces readers to this new approach to public projects. References are made to useful websites throughout the text. Cases are included at the end of the main text to encourage examination of real-life examples of project financing in practice and also highlight specific issues of current interest. The book will be helpful to project finance sponsors, lawyers, host governments, bankers and providers of capital
Resumo:
Conventional project management techniques are not always sufficient to ensure that schedule, cost and quality goals are met on large-scale construction projects. These jobs require complex planning, designing and implementation processes. The main reasons for a project's nonachievement in India's hydrocarbon processing industry are changes in scope and design, altered government policies and regulations, unforeseen inflation, under and/or improper estimation. Projects that are exposed to such an uncertain environment can be effectively managed by applying risk management throughout the project life cycle.
Resumo:
A cross-country pipeline construction project is exposed to an uncertain environment due to its enormous size (physical, manpower requirement and financial value), complexity in design technology and involvement of external factors. These uncertainties can lead to several changes in project scope during the process of project execution. Unless the changes are properly controlled, the time, cost and quality goals of the project may never be achieved. A methodology is proposed for project control through risk analysis, contingency allocation and hierarchical planning models. Risk analysis is carried out through the analytic hierarchy process (AHP) due to the subjective nature of risks in construction projects. The results of risk analysis are used to determine the logical contingency for project control with the application of probability theory. Ultimate project control is carried out by hierarchical planning model which enables decision makers to take vital decisions during the changing environment of the construction period. Goal programming (GP), a multiple criteria decision-making technique, is proposed for model formulation because of its flexibility and priority-base structure. The project is planned hierarchically in three levels—project, work package and activity. GP is applied separately at each level. Decision variables of each model are different planning parameters of the project. In this study, models are formulated from the owner's perspective and its effectiveness in project control is demonstrated.
Resumo:
Projects that are exposed to uncertain environments can be effectively controlled with the application of risk analysis during the planning stage. The Analytic Hierarchy Process, a multiattribute decision-making technique, can be used to analyse and assess project risks which are objective or subjective in nature. Among other advantages, the process logically integrates the various elements in the planning process. The results from risk analysis and activity analysis are then used to develop a logical contingency allowance for the project through the application of probability theory. The contingency allowance is created in two parts: (a) a technical contingency, and (b) a management contingency. This provides a basis for decision making in a changing project environment. Effective control of the project is made possible by the limitation of the changes within the monetary contingency allowance for the work package concerned, and the utilization of the contingency through proper appropriation. The whole methodology is applied to a pipeline-laying project in India, and its effectiveness in project control is demonstrated.
Resumo:
The aim of this study is to address the main deficiencies with the prevailing project cost and time control practices for construction projects in the UK. A questionnaire survey was carried out with 250 top companies followed by in-depth interviews with 15 experienced practitioners from these companies in order to gain further insights of the identified problems, and their experience of good practice on how these problems can be tackled. On the basis of these interviews and syntheses with literature, a list of 65 good practice recommendations have been developed for the key project control tasks: planning, monitoring, reporting and analysing. The Delphi method was then used, with the participation of a panel of 8 practitioner experts, to evaluate these improvement recommendations and to establish their degree of relevance. After two rounds of Delphi, these recommendations are put forward as "critical", "important", or "helpful" measures for improving project control practice.
Resumo:
There are several studies on managing risks in information technology (IT) projects. Most of the studies identify and prioritise risks through empirical research in order to suggest mitigating measures. Although they are important to clients for future projects, these studies fail to provide any framework for risk management from IT developers' perspective. Although a few studies introduced a framework of risk management in IT projects, most of them are presented from clients' perspectives and very little effort has been made to integrate this with the project management cycle. As IT developers absorb a considerable amount of risk, an integrated framework for managing risks in IT projects from developers' perspective is needed in order to ensure success in IT projects. The main objective of the paper is to develop a risk management framework for IT projects from the developers' perspective. This study uses a combined qualitative and quantitative technique with the active involvement of stakeholders in order to identify, analyse and respond to risks. The entire methodology has been explained using a case study on an information technology project in a public sector organisation in Barbados.
Resumo:
Although the various tools and techniques of quality management are routinely deployed in order to improve healthcare quality, an integrated approach is lacking, which combines the customer focus to identify quality issues, analytical techniques for prioritising improvement measures and a project management approach to plan, implement and evaluate the improvement projects. This study develops an innovative framework using Quality Function Deployment (QFD) and a logical framework in order to address this issue, and demonstrates its effectiveness using a case study on the intensive care unit of a hospital.
Resumo:
Purpose – The purpose of this paper is to help managers to successfully plan, implement, and operate enterprise resource planning (ERP) projects using a risk management framework. Design/methodology/approach – This paper adopted a combined literature review and case study method. Using literature review, the paper first identified major issues of managing ERP projects and develops a risk management framework for managing those issues. The proposed risk management framework was then applied to a ERP implementation project of a UK-based energy services group and its effectiveness for managing ERP projects implementation had been demonstrated. Additionally, the risk factors as identified from the case application are compared with the risk factors from the previous researches so as to suggest mitigating measures. Findings – All the risk factors are categorized into planning, implementation and operations phases along with project processes, organizational transformation and information technology (IT) perspectives. Project implementation phase is the most vulnerable to failure. The case study results reveal that the effect of other projects on on-going ERP project, management of overall IT architecture and non-availability of resources for organizational transformation are most critical from likelihood and impact perspectives. Managing risk across various phases of project and equal emphasize to effective project management, organizational transformation and IT adoption are the key to success in ERP implementation. Practical implications – The risk factors, which were identified using literature review and the case study, have great significance as mitigating measures of those risks may result successful implementation of ERP projects in the industry. Additionally, proposed risk management framework could be customized to implement ERP projects elsewhere. Originality/value – ERP projects are risky as they are capital intensive, technically complex, and call for organizational transformation. There are both success and failure stories. However, both researchers and practitioners agree, that if it can be implemented and operated successfully and benefits should be achievable. Although there are many studies on ERP implementation, little has been discussed on managing risks of ERP projects. Therefore, this paper bridges the gap.
Resumo:
The process framework comprises three phases, as follows: scope the supply chain/network; identify the options for supply system architecture and select supply system architecture. It facilitates a structured approach that analyses the supply chain/network contextual characteristics, in order to ensure alignment with the appropriate supply system architecture. The process framework was derived from comprehensive literature review and archival case study analysis. The review led to the classification of supply system architectures according to their orientation, whether integrated; partially integrated; co-ordinated or independent. The classification was combined with the characteristics that influence the selection of supply system architecture to encapsulate the conceptual framework. It builds upon existing frameworks and methodologies by focusing on structured procedure; supporting project management; facilitating participation and clarifying point of entry. The process framework was initially tested in three case study applications from the food, automobile and hand tool industries. A variety of industrial settings was chosen to illustrate transferability. The case study applications indicate that the process framework is a valid approach to the problem; however, further testing is required. In particular, the use of group support system technologies to support the process and the steps involving the participation of software vendors need further testing. However, the process framework can be followed due to the clarity of its presentation. It considers the issue of timing by including alternative decision-making techniques, dependent on the constraints. It is useful for ensuring a sound business case is developed, with supporting documentation and analysis that identifies the strategic and functional requirements of supply system architecture.