903 resultados para Project management reference model
Resumo:
Modelos de maturidade e modelos de referência em gerenciamento de projetos têm sido implantados de forma crescente na área de tecnologia da informação (TI). Este artigo tem por objetivo analisar o impacto do grau de maturidade organizacional em gerenciamento de projetos e o da adoção de modelos de referência no sucesso de projetos de TI. Foi adotada a abordagem de pesquisa quantitativa, com levantamento junto a 51 profissionais da área. Os resultados apontam para correlação positiva entre o grau de maturidade organizacional em gerenciamento de projetos e a satisfação das demandas dos stakeholders (principais interessados no projeto). Também foi constatada relação estatística positiva entre a adoção do PMBoK e o sucesso de projetos de TI, no que concerne ao atendimento dos requisitos e satisfação das demandas dos stakeholders.
Resumo:
The aim of this study is to investigate the role of operational flexibility for effective project management in the construction industry. The specific objectives are to: a) Identify the determinants of operational flexibility potential in construction project management b) Investigate the contribution of each of the determinants to operational flexibility potential in the construction industry c) Investigate on the moderating factors of operational flexibility potential in a construction project environment d) Investigate whether moderated operational flexibility potential mediates the path between predictors and effective construction project management e) Develop and test a conceptual model of achieving operational flexibility for effective project management The purpose of this study is to findout ways to utilize flexibility inorder to manage uncertain project environment and ultimately achieve effective project management. In what configuration these operational flexibility determinants are demanded by construction project environment in order to achieve project success. This research was conducted in three phases, namely: (i) exploratory phase (ii) questionnaire development phase; and (iii) data collection and analysis phase. The study needs firm level analysis and therefore real estate developers who are members of CREDAI, Kerala Chapter were considered. This study provides a framework on the functioning of operational flexibility, offering guidance to researchers and practitioners for discovering means to gain operational flexibility in construction firms. The findings provide an empirical understanding on kinds of resources and capabilities a construction firm must accumulate to respond flexibly to the changing project environment offering practitioners insights into practices that build firms operational flexibility potential. Firms are dealing with complex, continuous changing and uncertain environments due trends of globalization, technical changes and innovations and changes in the customers’ needs and expectations. To cope with the increasingly uncertain and quickly changing environment firms strive for flexibility. To achieve the level of flexibility that adds value to the customers, firms should look to flexibility from a day to day operational perspective. Each dimension of operational flexibility is derived from competences and capabilities. In this thesis only the influence on customer satisfaction and learning exploitation of flexibility dimensions which directly add value in the customers eyes are studied to answer the followingresearch questions: “What is the impact of operational flexibility on customer satisfaction?.” What are the predictors of operational flexibility in construction industry? .These questions can only be answered after answering the questions like “Why do firms need operational flexibility?” and “how can firms achieve operational flexibility?” in the context of the construction industry. The need for construction firms to be flexible, via the effective utilization of organizational resources and capabilities for improved responsiveness, is important because of the increasing rate of changes in the business environment within which they operate. Achieving operational flexibility is also important because it has a significant correlation with a project effectiveness and hence a firm’s turnover. It is essential for academics and practitioners to recognize that the attainment of operational flexibility involves different types namely: (i) Modification (ii) new product development and (iii) demand management requires different configurations of predictors (i.e., resources, capabilities and strategies). Construction firms should consider these relationships and implement appropriate management practices for developing and configuring the right kind of resources, capabilities and strategies towards achieving different operational flexibility types.
Resumo:
Companies are currently choosing to integrate logics and systems to achieve better solutions. These combinations also include companies striving to join the logic of material requirement planning (MRP) system with the systems of lean production. The purpose of this article was to design an MRP as part of the implementation of an enterprise resource planning (ERP) in a company that produces agricultural implements, which has used the lean production system since 1998. This proposal is based on the innovation theory, theory networks, lean production systems, ERP systems and the hybrid production systems, which use both components and MRP systems, as concepts of lean production systems. The analytical approach of innovation networks enables verification of the links and relationships among the companies and departments of the same corporation. The analysis begins with the MRP implementation project carried out in a Brazilian metallurgical company and follows through the operationalisation of the MRP project, until its production stabilisation. The main point is that the MRP system should help the company's operations with regard to its effective agility to respond in time to demand fluctuations, facilitating the creation process and controlling the branch offices in other countries that use components produced in the matrix, hence ensuring more accurate estimates of stockpiles. Consequently, it presents the enterprise knowledge development organisational modelling methodology in order to represent further models (goals, actors and resources, business rules, business process and concepts) that should be included in this MRP implementation process for the new configuration of the production system.
Resumo:
Today a number of studies are published on how organizational strategy is developed and how organizations contribute to local and regional development through the realization of these strategies. There are also many articles dealing with the success of a project by identifying the criteria and the factors that influence them. This article introduces the project-oriented strategic planning process that reveals how projects contribute to local and regional development and demonstrates the relationship between this approach and the regional competitiveness model as well as the KRAFT concept. There is a lot of research that focuses on sustainability in business. These studies argue that sustainability is very important to the success of a business in the future. The Project Excellence Model that analyses project success does not contain the sustainability criteria; the GPM P5 standard consists of sustainability components related either to the organizational level. To fill this gap a Project Sustainability Excellence Model (PSEM) was developed. The model was tested by interviews with managers of Hungarian for-profit and non-profit organizations. This paper introduces the PSEM and highlights the most important elements of the empirical analysis.
Resumo:
This study analyzes the manifestation of the dimensions of Entrepreneurial Orientation (EO) and Project Management Systems (PMS). We used a qualitative approach to conduct exploratory research through a study in literature and a pilot case in a software company. Data was collected from semi structured interviews, documents, and records on file, then triangulated and treated with content analysis. The model proposed for the relationship between the types of PMS (ad hoc, Classic PM, innovation, entrepreneurship/intrapreneurship) and the dimensions of EO (innovativeness, risk-taking, proactiveness, competitive aggressiveness, and autonomy), was partially corroborated by empirical studies. New studies are suggested to validate the applicability and setup of the model.
Resumo:
The paper proposes a Flexibility Requirements Model and a Factory Templates Framework to support the dynamic Virtual Organization decision-makers in order to reach effective response to the emergent business opportunities ensuring profitability. Through the construction and analysis of the flexibility requirements model, the network managers can achieve and conceive better strategies to model and breed new dynamic VOs. This paper also presents the leagility concept as a new paradigm fit to equip the network management with a hybrid approach that better tackle the performance challenges imposed by the new and competitive business 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:
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:
The main aim of this study was to develop the project management framework model which would serve as the new model to follow for upcoming projects at the Lappeenranta cement plant. The other goal was to execute the SNCR (selective non catalytic reduction) project successfully so that the nitrogen oxides emissions are below the stated emission limit when the new emission limit comes into effect beginning in July, 2008. Nitrogen oxides, project management aspects, SNCR and the invested system are explained in the theory part. In the practical part of the study, the SNCR project in the Lappeenranta cement plant was executed and the findings were documented. In order to reach the aim of this study, a framework of project management was made. The framework is based on the executed SNCR project, previous projects in the cement plant and on the available literature relating to the subject matter. The developed project turned out to be successful.
Resumo:
The technique of linear responsibility analysis is used for a retrospective case study of a private industrial development consisting of an extension to existing buildings to provide a warehouse, services block and packing line. The organizational structure adopted on the project is analysed using concepts from systems theory which are included in Walker's theoretical model of the structure of building project organizations (Walker, 1981). This model proposes that the process of building provision can be viewed as systems and subsystems which are differentiated from each other at decision points. Further to this, the subsystems can be viewed as the interaction of managing system and operating system. Using Walker's model, a systematic analysis of the relationships between the contributors gives a quantitative assessment of the efficacy of the organizational structure used. The causes of the client's dissatisfaction with the outcome of the project were lack of integration and complexity of the managing system. However, there was a high level of satisfaction with the completed project and this is reflected by the way in which the organization structure corresponded to the model's propositions.
Resumo:
According to the PMBOK (Project Management Body of Knowledge), project management is “the application of knowledge, skills, tools, and techniques to project activities to meet the project requirements” [1]. Project Management has proven to be one of the most important disciplines at the moment of determining the success of any project [2][3][4]. Given that many of the activities covered by this discipline can be said that are “horizontal” for any kind of domain, the importance of acknowledge the concepts and practices becomes even more obvious. The specific case of the projects that fall in the domain of Software Engineering are not the exception about the great influence of Project Management for their success. The critical role that this discipline plays in the industry has come to numbers. A report by McKinsey & Co [4] shows that the establishment of programs for the teaching of critical skills of project management can improve the performance of the project in time and costs. As an example of the above, the reports exposes: “One defense organization used these programs to train several waves of project managers and leaders who together administered a portfolio of more than 1,000 capital projects ranging in Project management size from $100,000 to $500 million. Managers who successfully completed the training were able to cut costs on most projects by between 20 and 35 percent. Over time, the organization expects savings of about 15 percent of its entire baseline spending”. In a white paper by the PMI (Project Management Institute) about the value of project management [5], it is stated that: “Leading organizations across sectors and geographic borders have been steadily embracing project management as a way to control spending and improve project results”. According to the research made by the PMI for the paper, after the economical crisis “Executives discovered that adhering to project management methods and strategies reduced risks, cut costs and improved success rates—all vital to surviving the economic crisis”. In every elite company, a proper execution of the project management discipline has become a must. Several members of the software industry have putted effort into achieving ways of assuring high quality results from projects; many standards, best practices, methodologies and other resources have been produced by experts from different fields of expertise. In the industry and the academic community, there is a continuous research on how to teach better software engineering together with project management [4][6]. For the general practices of Project Management the PMI produced a guide of the required knowledge that any project manager should have in their toolbox to lead any kind of project, this guide is called the PMBOK. On the side of best practices 10 and required knowledge for the Software Engineering discipline, the IEEE (Institute of Electrical and Electronics Engineers) developed the SWEBOK (Software Engineering Body of Knowledge) in collaboration with software industry experts and academic researchers, introducing into the guide many of the needed knowledge for a 5-year expertise software engineer [7]. The SWEBOK also covers management from the perspective of a software project. This thesis is developed to provide guidance to practitioners and members of the academic community about project management applied to software engineering. The way used in this thesis to get useful information for practitioners is to take an industry-approved guide for software engineering professionals such as the SWEBOK, and compare the content to what is found in the PMBOK. After comparing the contents of the SWEBOK and the PMBOK, what is found missing in the SWEBOK is used to give recommendations on how to enrich project management skills for a software engineering professional. Recommendations for members of the academic community on the other hand, are given taking into account the GSwE2009 (Graduated Software Engineering 2009) standard [8]. GSwE2009 is often used as a main reference for software engineering master programs [9]. The standard is mostly based on the content of the SWEBOK, plus some contents that are considered to reinforce the education of software engineering. Given the similarities between the SWEBOK and the GSwE2009, the results of comparing SWEBOK and PMBOK are also considered valid to enrich what the GSwE2009 proposes. So in the end the recommendations for practitioners end up being also useful for the academic community and their strategies to teach project management in the context of software engineering.
Resumo:
Facing the frequent failure of projects in rural areas with top-down approaches, there has been a promotion of participation of the local people in decisions that affect their territories (bottom-up approach) to promote sustainable regional development (Chambers, 1997; Lusthaus et al., 1999; Horton, 2004; Vazquez-Barquero, 2000). In fact participation was deemed necessary to ensure the success and sustainability of projects (UNDP, 2006; WRI, 2008; Davies, 2009). Hence, the progressive strengthening of the local population should be promoted so that they can acquire a range of skills and knowledge that allow them to manage resources properly and undertake productive activities in their territory (Contreras, 2000). These are intangibles and therefore difficult to measure. Hence, in this research a model of integration of intangibles in rural development projects management is proposed. The model designed supplements and enriches the conceptual framework ?Working with People? WWP (Cazorla et al, 2013).
Resumo:
La gestión de las tecnologías de la información tiene cada vez más importancia dentro de un mundo totalmente digitalizado y donde la capacidad de respuesta al cambio puede marcar el devenir de una compañía, y resulta cada vez más evidente que los modelos de gestión tradicionales utilizados en la mayoría de las compañías no son capaces de dar respuesta por si solos a estas nuevas necesidades. Aun teniendo identificado este área de mejora, son muchas las empresas reacias a abordar estos cambios, principalmente por el cambio rupturista que significa a nivel interno. De cara a facilitar esta transformación, se propone en este documento un modelo de transición controlada donde las grandes compañías puedan incorporar nuevas alternativas y herramientas ágiles de forma paulatina y asegurando que el proceso de cambio es seguro y efectivo. Mediante una modificación del ciclo de vida de proyecto dentro de la compañía, se incorporan en las áreas, equipos o dominios de la empresa que se identifiquen los nuevos modelos de gestión ágil, permitiendo así una transición gradual y controlada, y pudiendo además analizar los detalles sobre todo en etapas tempranas de la transformación. Una vez seleccionada el área o dominio objeto de la transformación, se realiza un análisis a nivel de Portfolio de proyectos, identificando aquellos que cumplen una serie de condiciones que les permiten ser gestionados utilizando modelos de gestión ágil. Para ello, se plantea una matriz de decisión con las principales variables a tener en cuenta a la hora de tomar una decisión. Una vez seleccionado y consensuado con los interesados el modelo de gestión utilizando la matriz de decisión, se plantean una serie de herramientas y métricas asociadas para que la gestión ágil del proyecto dé una visibilidad completa y detallada del estado en cada momento, asegurando un correcto proceso de gestión de proyectos para proveer visibilidad regular del progreso, riesgos, planes de contingencia y problemas, con las alertas y escalaciones adecuadas. Además de proponerse una serie de herramientas y métricas para la gestión ágil del proyecto, se plantean las modificaciones necesarias sobre las tipologías habituales de contrato y se propone un nuevo modelo de contrato: el Contrato Agile. La principal diferencia entre este nuevo modelo de contrato y los habituales es que, al igual que las metodologías ágiles, es ejecutado en segmentos o iteraciones. En definitiva, el objetivo de este documento es proveer un mecanismo que facilite la inclusión de nuevos modelos ágiles de gestión en grandes organizaciones, llevando a cabo una transición controlada, con herramientas y métricas adaptadas para tener visibilidad completa sobre los proyectos en todo momento.---ABSTRACT---The information technology management is every time more important in a totally digitized world, where the capacity to response the change could mark the future of a company, and results every time more evident that the traditional management models used in the most of the companies are not able to respond by themselves to these new necessities. Even having identified this improvement area, many companies are reluctant to address these changes, mainly due to the disruptive change that it means internally in the companies. In order to facilitate this transformation, this document proposed a controlled transition model to help the big companies to incorporate new alternatives and agile tools gradually and ensuring that the change process is safe and effective. Through a modification the project life cycle inside the company, the new agile management models are incorporated in the selected areas, teams or domains, permitting a gradual and controlled transition, and enabling further analyze the details above all in the early phases of the transformation. Once is selected the area or domain object of the transformation, a portfolio level analysis is performed, identifying those projects that meet a some conditions that allow them to be managed using agile management models. For that, a decision matrix is proposed with the principal variables to have into account at the time of decision making. Once the management model is selected using the decision matrix and it is agreed with the different stakeholders, a group of tools and metrics associated with the agile management projects are proposed to provide a regular visibility of the project progress, risks, contingency plans and problems, with proper alerts and escalations. Besides the group of tools and metrics proposed for agile project management, the necessary modifications over the traditional contract models and a new contract model are proposed: the Agile Contract. The main difference between this new contract model and the traditional ones is that, as the agile methodologies, it is executed in segments or iterations. To sum up, the objective of this document is to provide a mechanism that facilitates the inclusion of new agile management models in big companies, with a controlled transition and proposing adapted tools and metrics to have a full visibility over the project in all the phases of the project life cycle.