904 resultados para Project management maturity
Resumo:
Are you ready for a tender project? – Analysis of organisational project management maturity in the Austrian- Hungarian border region. Since the 1990s the European Union has paid more and more attention to subsidising cross-border development. It is understandable that different funding from proposal sources is particularly important for the border area, especially to those of utmost importance that support co-operation and rural development. Therefore, they could become a driving force for development. The authors’ research analyses the organisational project management maturity of the projects implemented in the frame of the Austria-Hungary Cross-border Cooperation Programme 2007-2013 (AT-HU). Analysing this kind of organisation is an important issue, since the new call for proposals are open in 2016 and the results of this study may provide a self-evaluation opportunity to organisations that need to know if they are ready or mature enough for a new tender project. The aim of this study was twofold. First of all, those indicators that could be used to analyse the project management maturity of implementing organisations in the AT-HU programme were identified. Based on the empirical research these are the project experience accumulated by the organisation, the internal processes operating at the institution and the professional background. Secondly, factors that can affect this project management maturity were explored and we determined five influencing area: the organisational structure, culture, project managers motivation and the typical and important competences.
Resumo:
Purpose – The purpose of the paper was to conduct an empirical investigation to explore the impact of project management maturity models (PMMMs) on improving project performance. Design/methodology/approach – The investigation used a cross-case analysis involving over 90 individuals in seven organisations. Findings – The findings of the empirical investigation indicate that PMMMs demonstrate very high levels of variability in individual's assessment of project management maturity. Furthermore, at higher levels of maturity, the type of performance improvement adopted following their application is related to the type of PMMM used in the assessment. The paradox of the unreliability of PMMMs and their widespread acceptance is resolved by calling upon the “wisdom of crowds” phenomenon which has implications for the use of maturity model assessments in other arena. Research limitations/implications – The investigation does have the usual issues associated with case research, but the steps that have been taken in the cross-case construction and analysis have improved the overall robustness and extendibility of the findings. Practical implications – The tendency for PMMMs to shape improvements based on their own inherent structure needs further understanding. Originality/value – The use of empirical methods to investigate the link between project maturity models and extant changes in project management performance is highly novel and the findings that result from this have added resonance.
Resumo:
En la actualidad, las buenas prácticas del Project Management Institute, Inc. (PMI®) son utilizadas en muchas organizaciones para la estructuración, ejecución y cierre de diversos proyectos; las buenas prácticas recogidas por este Instituto han servido de base para que las empresas logren conseguir los objetivos estratégicos con una correcta gestión de los programas y proyectos que se vayan a emprender -- El sector de la construcción no es ajeno a la aplicación de estos estándares, más aún cuando el común denominador son los sobrecostos, la prolongación del cronograma y la variación del alcance, que finalmente terminan afectado la rentabilidad de los proyectos y redundan en la rentabilidad de la empresa -- Mabego S.A.S., es una empresa nueva dedicada a la estructuración, ejecución y venta de proyectos inmobiliarios, cuyo centro de operación es la ciudad de Pasto-Departamento de Nariño, el objetivo principal de la empresa es penetrar el mercado inmobiliario local, teniendo como fortalezas la experiencia y conocimiento aportado por los socios -- Con el presente trabajo se analizan los cuarenta y siete (47) procesos dentro de los grupos de inicio, planeación, ejecución, monitoreo y control, además de cierre establecidos en las diez (10) áreas del conocimiento que establece el PMI® en la guía de los fundamentos para la dirección de proyectos (Guía del PMBOK® - Project Management Body of Knowledge) quinta edición; se crea una metodología de acuerdo a las necesidades de la organización; para conseguirlo se analizaron cada uno de los procesos establecidos en el PMI® y como resultado se presenta la estandarización por medio de formatos y procedimientos que ayudan a la empresa a cumplir con los objetivos específicos de cada uno de sus proyectos -- La pertinencia del trabajo radica en la necesidad de la empresa Mabego S.A.S., de formalizar los procedimientos dentro de la misma, esto debido a que se pretende lograr una correcta estructuración, ejecución y liquidación de los proyectos, además, se aplicó una metodología definida con el objetivo de estandarizar los procesos internos y así lograr un posicionamiento en el sector de la construcción por medio del reconocimiento del cliente en la entrega a tiempo y con la calidad propuesta en los documentos de venta del proyecto
Resumo:
The subject of management is renowned for its addiction to fads and fashions. Project Management is no exception. The issue of interest for this paper is the establishment of the 'College of Complex Project Managers' and their 'competency standard for complex project managers.' Both have generated significant interest in the Project Management community, and like any other human endeavour they should be subject to critical evaluation. The results of this evaluation show significant flaws in the definition of complex in this case, the process by which the College and its standard have emerged, and the content of the standard. However, there is a significant case for a portfolio of research that extends the existing bodies of knowledge into large-scale complicated (or major) projects that would be owned by the relevant practitioner communities, rather than focused on one organization. Research questions are proposed that would commence this stream of activity towards an intelligent synthesis of what is required to manage in both complicated and truly complex environments.
Resumo:
Software development is a discipline that is almost as old as the history of computers. With the advent of the Internet and all of its related technologies, software development has been on high demand. But, and especially in SME (small and medium enterprise), this was not accompanied with a comparable effort to develop a set of sustainable and standardized activities of project management, which lead to increasing inefficiencies and costs. Given the actual economic situation, it makes sense to engage in an effort to reduce said inefficiencies and rising costs. For that end, this work will analyze the current state of software development’s project management processes on a Portuguese SME, along with its problems and inefficiencies in an effort to create a standardized model to manage software development, with special attention given to critical success factors in an agile software development environment, while using the best practices in process modeling. This work also aims to create guidelines to correctly integrate these changes in the existing IS structure of a company.
Resumo:
The main goals for the current dissertation is to research on how practices and concepts from Agile Project Management can be applied in a non-IT context and to discover which aspects should be considered when deciding if whether an Agile approach should be implemented or not. Previous studies reflect on the adoption for the identified context. However, the recognition of these practices and concepts by the Project Management field of studies still remains unresolved. The adoption of Agile Project Management emerges as a manifestation against traditional approaches, mainly due to their inability of accepting requirements’ changes. Therefore, these practices and concepts can be considered in order to reduce the risks concerning the increase of competition and innovation – which does not apply to the IT sector solely. The current study reviews the literature on Agile Project Management and its adoption across different sectors in order to assess which practices and concepts can be applied on a non-IT context. Nine different methods are reviewed, where two of these show a higher relevance – Scrum and Extreme Programming. The identified practices and concepts can be separated into four different groups: Cultural and Organizational Structures, Process, Practices, and Artefacts. A framework based on the work by Boehm & Turner in 2004 is developed in order to support the decision of adopting agile methods. A survey intended for project managers was carried in order to assess the implementation of the identified practices and concepts and to evaluate which variables have the highest importance on the developed decision support framework. It is concluded that New Product Development is the project type with the highest potential to implement an agile approach and that the Project Final Product’s Innovativeness, Competitiveness, and the Project Member’s Experience and Autonomy are the most important aspects to consider an implementation of an Agile approach.
Resumo:
During recent decades it has been possible to identify several problems in construction industry project management, related with to systematic failures in terms of fulfilling its schedule, cost and quality targets, which highlight a need for an evaluation of the factors that may cause these failures. Therefore, it is important to understand how project managers plan the projects, so that the performance and the results can be improved. However, it is important to understand if other areas beyond cost and time management that are mentioned on several studies as the most critical areas, receive the necessary attention from construction project managers. Despite the cost and time are the most sensitive areas/fields, there are several other factors that may lead to project failure. This study aims at understand the reasons that may cause the deviation in terms of cost, time and quality, from the project management point of view, looking at the knowledge areas mentioned by PMI (Project Management Institute).
Resumo:
Risk management is an important component of project management. Nevertheless, such process begins with risk assessment and evaluation. In this research project, a detailed analysis of the methodologies used to treat risks in investment projects adopted by the Banco da Amazonia S.A. was made. Investment projects submitted to the FNO (Constitutional Fund for Financing the North) during 2011 and 2012 were considered for that purpose. It was found that the evaluators of this credit institution use multiple indicators for risk assessment which assume a central role in terms of decision-making and contribute for the approval or the rejection of the submitted projects; namely, the proven ability to pay, the financial records of project promotors, several financial restrictions, level of equity, level of financial indebtedness, evidence of the existence of a consumer market, the proven experience of the partners/owners in the business, environmental aspects, etc. Furthermore, the bank has technological systems to support the risk assessment process, an internal communication system and a unique system for the management of operational risk.
Resumo:
Project Management involves onetime endeavors that demand for getting it right the first time. On the other hand, project scheduling, being one of the most modeled project management process stages, still faces a wide gap from theory to practice. Demanding computational models and their consequent call for simplification, divert the implementation of such models in project management tools from the actual day to day project management process. Special focus is being made to the robustness of the generated project schedules facing the omnipresence of uncertainty. An "easy" way out is to add, more or less cleverly calculated, time buffers that always result in project duration increase and correspondingly, in cost. A better approach to deal with uncertainty seems to be to explore slack that might be present in a given project schedule, a fortiori when a non-optimal schedule is used. The combination of such approach to recent advances in modeling resource allocation and scheduling techniques to cope with the increasing flexibility in resources, as can be expressed in "Flexible Resource Constraint Project Scheduling Problem" (FRCPSP) formulations, should be a promising line of research to generate more adequate project management tools. In reality, this approach has been frequently used, by project managers in an ad-hoc way.
Resumo:
Increasing the maturity in Project Management (PM) has become a goal for many organizations, leading them to adopt maturity models to assess the current state of its PM practices and compare them with the best practices in the industry where the organization is inserted. One of the main PM maturity models is the Organizational Project Management Maturity Model (OPM3®), developed by the Project Management Institute. This paper presents the Information Systems and Technologies organizations outcome analysis, of the assesses made by the OPM3® Portugal Project, identifying the PM processes that are “best” implemented in this particular industry and those in which it is urgent to improve. Additionally, a comparison between the different organizations’ size analyzed is presented.
Resumo:
Tuotekehityksestä ja sen johtamisesta on tullut erittäin tärkeä osa tietoliikenneteollisuutta. Jatkuva teknologinen kehitys ja lyhentyneet tuotteiden elinkaaret ovat saaneet yritykset panostamaan tuotekehitysprosesseihin ja johtamiseen. Erityisesti nopeatempoiset ja lyhytkestoiset projektit onkin koettu ongelmallisiksi. Diplomityön tavoitteena oli tutkia teoriassa uusien tuotteiden tuotekehitystä, tuotekehitysprosesseja sekä projektijohtamista. Käytännön osuudessa oli tavoitteena kehittää kokeellinen tuotekehitysmalli nopeatempoisten ja lyhytkestoisten tuotekehitysprojektien tarpeisiin muuttuvissa ja epävarmoissa olosuhteissa. Tavoitteena oli myös käyttää ja analysoida kehitettyä kokeellista tuotekehitysmallia lyhytkestoisen tuotekehitysprojektin yhteydessä. Työn tuloksena saatiin ohjelmistotuote vaadituilla ominaisuuksilla vaaditussa ajassa ja todettiin projektissa käytetyn kokeellisen tuotekehitysmallin osoittautuneen toimivaksi. Jatkotutkimuksia tarvitaan selvittämään mallin sopivuutta ja sen kehityskohteita erilaisten tuotekehitysprojektien kohdalla.
Resumo:
Stora Enso has research centres in Finland, Sweden and Germany. The research centres use PIMS as a research project invoicing and monitoring system. Possible reorganization and new financing model for R&D functions have been considered and the project management system should be developed to support the new operation model. The objective of this thesis is to find a model for R&D project management, and to present the project management system of Stora Enso, and to discuss if the current system could be developed to respond to the new needs or should it be replaced with another system. The theoretical part of the study describes challenges in R&D project management, and presents different project characteristics, and methods for managing R&D project portfolio. It is also described how the project management system can support project monitoring and controlling, and how inter-project learning can be enhanced. The empirical part of the study presents the current project management system of Stora Enso and how the system should be developed to support Stora Enso’s R&D functions better. In conclusion, it is stated that there is no relevant reason to replace PIMS with another system, because PIMS can be developed to support R&D project management better with a hybrid system. It is also suggested that the new financing model should not be implemented before more comprehensive analysis of its effects is conducted.
Resumo:
After decades of mergers and acquisitions and successive technology trends such as CRM, ERP and DW, the data in enterprise systems is scattered and inconsistent. Global organizations face the challenge of addressing local uses of shared business entities, such as customer and material, and at the same time have a consistent, unique, and consolidate view of financial indicators. In addition, current enterprise systems do not accommodate the pace of organizational changes and immense efforts are required to maintain data. When it comes to systems integration, ERPs are considered “closed” and expensive. Data structures are complex and the “out-of-the-box” integration options offered are not based on industry standards. Therefore expensive and time-consuming projects are undertaken in order to have required data flowing according to business processes needs. Master Data Management (MDM) emerges as one discipline focused on ensuring long-term data consistency. Presented as a technology-enabled business discipline, it emphasizes business process and governance to model and maintain the data related to key business entities. There are immense technical and organizational challenges to accomplish the “single version of the truth” MDM mantra. Adding one central repository of master data might prove unfeasible in a few scenarios, thus an incremental approach is recommended, starting from areas most critically affected by data issues. This research aims at understanding the current literature on MDM and contrasting it with views from professionals. The data collected from interviews revealed details on the complexities of data structures and data management practices in global organizations, reinforcing the call for more in-depth research on organizational aspects of MDM. The most difficult piece of master data to manage is the “local” part, the attributes related to the sourcing and storing of materials in one particular warehouse in The Netherlands or a complex set of pricing rules for a subsidiary of a customer in Brazil. From a practical perspective, this research evaluates one MDM solution under development at a Finnish IT solution-provider. By means of applying an existing assessment method, the research attempts at providing the company with one possible tool to evaluate its product from a vendor-agnostics perspective.
Resumo:
According to several surveys and observations, the percentage of successfully conducted IT projects without over-budgeting and delays in time schedule are extremely low. Many projects also are evaluated as failures in terms of delivered functionality. Nuldén (1996) compares IT projects with bad movies; after watching for 2 hours, one still tries to finish it even though one understands that it is a complete waste of time. The argument for that is 'I've already invested too much time to terminate it now'. The same happens with IT projects: sometimes the company continues wasting money on these projects for a long time, even though there are no expected benefits from these projects. Eventually these projects are terminated anyway, but until this moment, the company spends a lot. The situation described above is a consequence of “escalation of commitment” - project continuation even after a manager receives negative feedback of the project’s success probability. According to Keil and Mähring (2010), even though escalation can occur in any type of project, it is more common among complex technological projects, such as IT projects. Escalation of commitment very often results in runaway projects. In order to avoid it, managers use de-escalation strategies, which allow the resources to be used in more effective. These strategies lead to project termination or turning around, which stops the flow of wasted investments. Numbers of researches explore escalation of commitment phenomena based on experiments and business cases. Moreover, during the last decade several frameworks were proposed for de-escalation strategy. However, there is no evidence of successful implementation of the de-escalation of commitment strategy in the literature. In addition, despite that fact that IT project management methodologies are widely used in the companies, none of them cover the topic of escalation of commitment risks. At the same time, there are no researches proposing the way to implement de-escalation of commitment strategy into the existing project management methodology The research is focused on a single case of large ERP implementation project by the consulting company. Hence, the main deliverables of the study include suggestions of improvement in de-escalation methods and techniques in the project and in the company. Moreover, the way to implement these methods into existing project management methodology and into the company general policies is found.