Applying an adaptation of the Prado Project Management Maturity Model in an academic context

Dissertação de mestrado integrado em Engenharia e Gestão de Sistemas de InformaçãoThe organization’s strategy of a company is determinant in its performance. Failing strategies compromise the achievement of its goals. Thus, the interest in the field of project management has been increasing and has generated several tools used by companies. The need to develop methodologies to evaluate the performance of projects in organizations has a strong contribution to the development of maturity models. Maturity models help organizations to define their organizational strategy. The lack of knowledge of these maturity models causes organizations to experience problems in the development and improvement of their project management processes. In this dissertation, it was developed an analysis of the most relevant models of project management maturity by comparing them. The main objective of this dissertation is to adapt and apply a maturity model to assess the evolution of the maturity of project management practices in development teams in the academic environment. Afterward the theoretical study of the different maturity models, it was applied the Prado Project Management Maturity Model. This simplified model assesses the performance and maturity to development teams in the IT area. The model is applied to the project teams of curricular subjects of Development of Computer Applications of the second academic year and Information Systems and Technologies Project of the fourth academic year of the Integrated Masters in Engineering and Management of Information Systems course at the University of Minho. To achieve this goal, the methodology used was the Case Study because its purpose is to gather information about the real context that allows a greater and more detailed knowledge about the topic. The Case Study was developed through questionnaires answered by the project managers of the different teams. Through the application of the model, it was possible to compare the maturity between the two curricular units and to verify the effectiveness of the learning methods and strategies, and results in project management competencies throughout the course. Observing that there is a significant evolution in maturity from the Information Systems and Technologies Project teams compared to Development of Computer Application teams.A estratégia organizacional de uma empresa é determinante no seu desempenho. Estratégias que falham põem em causa o alcance dos seus objetivos. Desta forma, o interesse na área de gestão de projetos tem vindo a aumentar e tem gerado várias ferramentas que podem ser utilizadas pelas empresas. A necessidade de metodologias de avaliação do desemprenho de projetos nas organizações contribui para o desenvolvimento de modelos de maturidade. Os modelos de maturidade auxiliam as empresas a definir a sua estratégia organizacional. A falta de conhecimento destes modelos de maturidade faz com que as organizações tenham problemas no desenvolvimento e melhoria dos seus processos de gestão de projetos. No presente trabalho foram analisados os mais relevantes modelos de maturidade de gestão de projetos, através da comparação dos mesmos. O principal objetivo desta dissertação consiste na adaptação e aplicação de um modelo de maturidade para avaliar a evolução da maturidade das práticas de gestão de projetos em equipas de desenvolvimento em ambiente académico. Após a análise teórica dos diferentes modelos de maturidade, aplicou-se o Modelo de Maturidade em Gestão de Projetos de Prado. Este modelo simplificado restringe a avaliação do desempenho e maturidade a equipas de desenvolvimento na área das TI. Este modelo foi aplicado nas equipas de projeto das unidades curriculares de Desenvolvimento de Aplicações Informáticas do segundo ano letivo e Projeto de Tecnologias e Sistemas de Informação do quarto ano letivo do curso Mestrado Integrado em Engenharia e Gestão de Sistemas de Informação da Universidade do Minho. Para concretizar o objetivo proposto, a metodologia utilizada foi o Estudo de Caso pois o seu propósito é a junção de informação sobre um contexto real que permite um maior e mais detalhado conhecimento sobre o mesmo. O Estudo de Caso foi desenvolvido através de questionários respondidos pelos gestores de projetos das diversas equipas. Através da aplicação do modelo, foi possível comparar a maturidade entre as equipas das duas unidades curriculares e verificar a eficácia dos métodos e estratégias de ensino em competências de gestão de projetos ao longo do curso. Observando-se, assim, que existe uma evolução significativa da maturidade de gestão de projetos das equipas de Projeto de Tecnologias de Sistemas de Informação em relação às equipas de Desenvolvimento de Aplicações Informáticas

Capability Maturity Model Integration (Cmmi) for Small Organizations

Software Process Improvement (SPI) is a large area of expertise that deals with software development standard processes and is a progression of proven methods of process improvement from many different methodologies. Personal Software Process (PSP) and Team Software Process (TSP) complement the implementation of Capability Maturity Model Implementation (CMMI) and can be applied gradually from the individual, to the team, and then to the organization. These solutions from Carnegie Melon\u27s Software Engineering Institute (SEI) are leading edge for the field of process improvement. Solutions like this consume many resources, are very complex, require years to implement, and can be costly. The SEI solutions offer an industry standard for SPI. Three case studies were analyzed to provide insight into the benefits of CMMI for small organizations. Decisions that steer these solutions generally involve scheduling, quality, and cost. Depending on the individual needs of an organization, the CMMI technology can fulfill what is required. The example case studies were examined and concluded that given favorable conditions, implementing CMMI is feasible for small organizations

Using grounded theory to understand software process improvement: A study of Irish software product companies

Software Process Improvement (SPI) aims to understand the software process as it is used within an organisation and thus drive the implementation of changes to that process to achieve specific goals such as increasing development speed, achieving higher product quality or reducing costs. Accordingly, SPI researchers must be equipped with the methodologies and tools to enable them to look within organisations and understand the state of practice with respect to software process and process improvement initiatives, in addition to investigating the relevant literature. Having examined a number of potentially suitable research methodologies, we have chosen Grounded Theory as a suitable approach to determine what was happening in actual practice in relation to software process and SPI, using the indigenous Irish software product industry as a test-bed. The outcome of this study is a theory, grounded in the field data, that explains when and why SPI is undertaken by the software industry. The objective of this paper is to describe both the selection and usage of grounded theory in this study and evaluate its effectiveness as a research methodology for software process researchers. Accordingly, this paper will focus on the selection and usage of grounded theory, rather than results of the SPI study itself

Maturity Models in Information Systems Research: Literature Search and Analysis

This article collects and analyzes seventy-six maturity model articles that have been published in leading Information Systems (IS) journals and conference proceedings during the past fifteen years. We study the IS literature on maturity models from three different perspectives: a research perspective, which is particularly relevant for scholars who are interested in the design and adoption of maturity models; a publication perspective, which reflects the interests of authors and reviewers of maturity model articles; and a practitioner’s perspective, which is especially relevant for maturity model users and consultants. The results are interesting in several respects. From the research perspective, the Capability Maturity Model (CMM) is the most dominant foundation of past IS research on maturity models. In contrast, theories on the design and adoption of maturity models are distinctly rare in our sample. The publication outlets that are considered feature quantitative and qualitative empirical research alike, but―with a decreasing number―purely conceptual research as well. Of late, past maturity model research can mainly be located in the area of IT and organizations, while the formerly very popular domain of IS development is of less interest today. As for the publication perspective, we find that the level of publication activity in the field has generally been increasing over the last fifteen years, with North American and European researchers dominating the academic discussion. Finally, with regard to the practitioner’s perspective, we compile advice on the practical application of maturity models from a critical analysis of the literature. It is hoped that the results can stimulate and guide future research in the field and inform the development and usage of theoretically sound maturity models in practice

Introducing a PMO in XYZ Company

The purpose of this field project is to explore and build awareness about the main aspects—types, hierarchies, maturity models, and competency frameworks—related to establishing a Project Management Office (PMO) in a company. This study, inspired by a real case, examines a failed attempt to create a PMO in XYZ Company, which operates in the IT industry providing e-services. Through this analysis, the main elements needed for a successful PMO are identified and explained along with the steps needed to implement related theories. Furthermore, potential reasons for the failure of the initial PMO are investigated and recommendations for better alternatives are suggested. As a result, the lessons learned from this research can assist with making more informed decision when creating PMOs in the future

Political Maneuvering During Business Process Transformation: A Pluralist Approach

For years, managers have tried to improve organizational performance through business process transformation (BPT), and their experiences have informed IS research and practice. Although extant theory acknowledges the political nature of these dynamic transformation initiatives, researchers have yet to empirically investigate and theorize how organizational politics impacts BPT behaviors and outcomes. Drawing on a pluralist methodology, we present an embedded case study of a company-wide BPT project across four business units at the high-tech firm Terma. First, we apply different perspectives on organizational politics to develop detailed accounts of each business unit\u27s response to the transformation initiative, which reveals four distinct patterns of BPT politics: “applying the hammer”, “struggling to engage”, “walking the talk”, and “keeping up appearances”. Next, we combine the empirical findings with extant literature to theorize how transformation agents and process users engage in politics during BPT implementation. As a result, our research leverages a pluralist approach to show how alternative political perspectives and forms of politics can help managers maneuver BPT initiatives in their roles as transformation agents and process users

Improving software project management quality through the use of analytics on project management data

Abstract in EnglishSoftware project management has been less effective as a result of being focused on resource management and the completion of projects within allocated resources and other confines. There has not been much focus on improving software project management quality through improved decision-making, software project management standards and methodologies, hence the focus of this study to explore the possibility of using data analytics with project management standards and methodologies to improve software project management quality. The main question to be addressed in this study is: Can data analytics use in software project management improve decision-making and project management quality? This study, therefore, explores and provides insight on data analytics use, by means of a survey that was completed by software project managers. A questionnaire was used to collect data from software project managers. The gathered data was captured and analysed using the Statistical Package for the Social Sciences (SPSS), and the analysed data was used for validity testing, while the reliability of the measurement items was tested using Cronbach’s Alpha. A hypothesis was used to evaluate the effect of data analytics use on software project management quality. The research made use of the positivist research method. The study established that data analytics has not yet been widely adopted by software project managers and organisations alike, as both the project managers and organisations have not done enough to promote the training in, and the adoption of data analytics. The research also established that data analytics can improve software project management quality through improved decision-making and in complementing software project management standards. The study findings will be beneficial to software project managers, researchers and organisations as it reveals the factors that are necessary to effectively use data analytics in software project management, as well as highlighting how data analytics improves software project management qualitySchool of ComputingM.Sc. (Computing

Mapping CMMI process areas to agile best practices

Dissertation presented as the partial requirement for obtaining a Master's degree in Information Management, specialization in Information Systems and Technologies ManagementTo maintain competitiveness, software development companies are pressured to deliver products in less time, without compromising on quality and budget. To meet this demand, companies often adopt Agile software development techniques that enable shorter delivery times through constant smaller deliveries and shorter interactive cycles in software development processes. Although the innovation and the decrease of development time provided by these techniques, companies have perceived that quality is a differentiated factor and feel the urge to maintain the quality of their software to stand out from the competitors. At this point CMMI is presented as a reference model that contains a set of practices which lead to the maturity of organizations with focus on the improvement of organization processes and reduction of processes risk of failure increasing quality. In contrast with Agile, that puts individuals and their interactions in higher importance than processes and tools and where being adaptable to changes is more important than following strictly what was planned, CMMI it is a strict traditional approach that implies extensive formalism and focus on the processes. Derived of those apparent opposite beliefs, Agile development methods and CMMI best practices are frequently perceived to be at odds with each other. There is a great discussion about CMMI ability to be Agile and Agile methods to adapt to CMMI requirements without losing agility. This study aims to map CMMI for development process areas to Agile best practices to help in the understanding of the compatibilities and incompatibilities regarding the integration of CMMI and Agile. That will guide companies into the successful integration of Agile and maturity models together taking full advantage of their capabilities leading to enhanced software development. With the integration of those two approaches it is expected that Agile practices can help mature organizations to become more flexible, and CMMI could help Agile organizations to increase processes quality, fulfilling their goals and having their competitiveness sustained