Efectividad de los lineamientos del Project Management Institute, en la implementación del sistema de Relacionamiento con el Cliente (CRM) Siebel, caso UNE Telecomunicaciones sede Medellín

En la actualidad, las empresas de telecomunicaciones, con el gran avance de la tecnología, son conscientes de que la mejor manera de cautivar y retener a los clientes es proporcionando productos y servicios que satisfagan las necesidades de éstos de una manera rápida y oportuna -- En consecuencia, estas empresas, centran su atención en los sistemas de relacionamiento con el cliente (CRM) que están enfocados en gestionar y conservar a los clientes de una manera eficiente -- En atención a lo expuesto, se vuelve fundamental que la implementación de este tipo de sistemas se realice cumpliendo con los alcances propuestos, con el costo estipulado y en el tiempo establecido -- Esto con el fin de desarrollar ventajas competitivas en el mercado -- El objetivo principal de esta investigación, es medir la efectividad de los lineamientos propuestos por el Project Management Institute (PMI) de gestión de proyectos, en la implementación del sistema de relacionamiento con el cliente (CRM) en la compañía colombiana de telecomunicaciones UNE EPM Telecomunicaciones

Diseño de gestión de proyectos bajo la guía metodológica del Project Management Institute, INC. - PMI® para la empresa MABEGO S.A.S.

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

Project management: evaluation of the problems in the portuguese construction industry

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).

An Analysis Of The Recommended Knowledge For The Software Project Management Discipline

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.

Definition of an it project portfolio management methodology for a pharmaceutical company

Con la creciente popularidad de las soluciones de IT como factor clave para aumentar la competitividad y la creación de valor para las empresas, la necesidad de invertir en proyectos de IT se incrementa considerablemente. La limitación de los recursos como un obstáculo para invertir ha obligado a las empresas a buscar metodologías para seleccionar y priorizar proyectos, asegurándose de que las decisiones que se toman son aquellas que van alineadas con las estrategias corporativas para asegurar la creación de valor y la maximización de los beneficios. Esta tesis proporciona los fundamentos para la implementación del Portafolio de dirección de Proyectos de IT (IT PPM) como una metodología eficaz para la gestión de proyectos basados en IT, y una herramienta para proporcionar criterios claros para los directores ejecutivos para la toma de decisiones. El documento proporciona la información acerca de cómo implementar el IT PPM en siete pasos, el análisis de los procesos y las funciones necesarias para su ejecución exitosa. Además, proporciona diferentes métodos y criterios para la selección y priorización de proyectos. Después de la parte teórica donde se describe el IT PPM, la tesis aporta un análisis del estudio de caso de una empresa farmacéutica. La empresa ya cuenta con un departamento de gestión de proyectos, pero se encontró la necesidad de implementar el IT PPM debido a su amplia cobertura de procesos End-to-End en Proyectos de IT, y la manera de asegurar la maximización de los beneficios. Con la investigación teórica y el análisis del estudio de caso, la tesis concluye con una definición práctica de un modelo aproximado IT PPM como una recomendación para su implementación en el Departamento de Gestión de Proyectos.

Resource-allocation capabilities of commercial project management software. An experimental analysis

When project managers determine schedules for resource-constrained projects, they commonly use commercial project management software packages. Which resource-allocation methods are implemented in these packages is proprietary information. The resource-allocation problem is in general computationally difficult to solve to optimality. Hence, the question arises if and how various project management software packages differ in quality with respect to their resource-allocation capabilities. None of the few existing papers on this subject uses a sizeable data set and recent versions of common software packages. We experimentally analyze the resource-allocation capabilities of Acos Plus.1, AdeptTracker Professional, CS Project Professional, Microsoft Office Project 2007, Primavera P6, Sciforma PS8, and Turbo Project Professional. Our analysis is based on 1560 instances of the precedence- and resource-constrained project scheduling problem RCPSP. The experiment shows that using the resource-allocation feature of these packages may lead to a project duration increase of almost 115% above the best known feasible schedule. The increase gets larger with increasing resource scarcity and with increasing number of activities. We investigate the impact of different complexity scenarios and priority rules on the project duration obtained by the software packages. We provide a decision table to support managers in selecting a software package and a priority rule.

Computer software management : a primer for project management and quality control /

Includes bibliographical references (p. 48-49).

The international diffusion of project management

This paper examines the international diffusion of one business practice, project management, through the prism of prior literature and data on the diffusion of ISO 9000. The study took an inductive approach, building theory through the iterative collection and analysis of quantitative and qualitative data. The findings problematise the central position accorded to the S-curve model and neo-institutional theory in explaining technology diffusion. The research posits three distinct processes driving the diffusion process: utility, institutional isomorphism, and competitive isomorphism, with the latter consisting of three primary mechanisms: competitive imitation, trendslators and fashion retailers. Contrary to prior literature, national, quasi-professional associations are found to be central to the diffusion process and play a key role in advocating and containing management technologies.

And then came Complex Project Management

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.

Standardization of project management processes

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.

An essay on agile project management practices

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.

The importance of risk assessment in the context of investment project management: a case study

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.