841 resultados para software project management
Resumo:
Traditional business approaches do not take account of the rapid technological developments underpinning today's world. Further understanding the role of technology and its efficient management to build and maintain a competitive edge in business can allow project managers to more successfully manage organisations, and to adapt to and capitalise on, today’s rapidly changing environment. Strategic Technology Management links engineering, science and management principles to identify, choose, and implement the most effective means of attaining compatibility between internal skills and resources of an organisation and its competitive, economic and social environment. This paper reviews the rationale and the development of a new Strategic Technology Management subject in QUT’s Master of Project Management program. It discusses recent developments in the area of technology management from an international perspective, provides details of the curriculum developed and discusses the experience of completing two years of teaching the new program.
Resumo:
The purpose of this paper is to investigate the Japanese answer to the 90’s depression by (i). presenting a case study of the framework developed to address the new business challenges and value creation in complex, ambiguous and uncertain environment, i.e., Development of Project and Programme Management for Enterprise Innovation (P2M) and Project Management Association Japan (PMAJ) in Japan; and (ii). Exposing what in our view are the underlying theoretical bases supporting this framework and from this drawing some theoretical lessons learnt which could be helpful to the development of sound PM standards and PM competence model. This theoretical approach is assumed to be useful to transpose the Japanese experience to other analogical contexts and situations.
Resumo:
Management of project knowledge is a critical factor for project success. Project Management Office (PMO) is a unit within organisations to centrally facilitate, manage and control organisational project for improving the rate of project success. Due to increasing interest of developing PMO, the Project Management Maturity Model (PMMM) has been proposed to develop PMOs gradually. The PMMM contributes to evolvement of PMO from immature to mature level through addressing appropriate PM practices. Despite the importance of project knowledge, it has not been extensively investigated in project environments. In addition, the existing PMMMs not only do not address management of project knowledge, but also they recommend little criteria to assess the maturity of PMO from KM point of view. The absence of KM discussion in current PMMMs was defined as the subject of a research project in order for addressing KM practices at various maturity levels of PMO. In order to address the mentioned gap, a framework has been developed based on the current discussions of both PM and KM. The proposed framework comprises three premises: KM processes and practices, PMMM, and KM Maturity Model (KMMM). The incorporation of KMMM practices at various maturity levels of PMO is one of the significance of this framework. It proposes numbers of KM strategies, processes, and practices to address project knowledge management at various levels PMO. This framework shall be useful guidance for developing PMOs from KM perspective. In other words, it contributes to management of project knowledge, as a key for project success. The proposed framework follows the process-based approach and it could be employed alongside the current PMMMs for PMO development. This paper presents the developed framework, theoretical background, premises, proposed KM practices, and processes to be employed in Project-based Organisations and PMOs. This framework has been examined at numbers of case studies with different maturity levels. The case studies outcomes, which will be subjects for future papers, have not shown any significant contradiction yet, however, more investigations are being conducted to validate the proposed framework.
Resumo:
Knowledge Management (KM) is vital factor to successfully undertake projects. The temporary nature of projects necessitates employing useful KM practices to reduce any issues such as knowledge leakiness and rework. The Project Management Office (PMO) is a unit within organisations to facilitate and oversee organisational projects. Project Management Maturity Models (PMMM) show the development of PMOs from immature to mature levels. The existing PMMMs have focused on discussing Project Management (PM) practices, however, the management of project knowledge is yet to be addressed, at various levels of maturity. A research project was undertaken to investigate the mentioned gap for addressing KM practices at the existing PMMMs. Due to the exploratory and inductive nature of this research, qualitative methods using case studies were chosen as the research methodology to investigate the problem in the real world. In total, three cases selected from different industries: research; mining and government organisations, to provide broad categories for research and research questions were examined using the developed framework. This paper presents the findings from the investigation of the research organisation with the lowest level of maturity. From KM process point of view, knowledge creation and capturing are the most important processes, while knowledge transferring and reusing received less attention. In addition, it was revealed that provision of “knowledge about client” and “project management knowledge” are the most important types of knowledge that are required at this level of maturity. The results also revealed that PMOs with higher maturity level have better knowledge management, however, some improvement is needed. In addition, the importance of KM processes varies at different levels of maturity. In conclusion, the outcomes of this paper could provide powerful guidance to PMOs at lowest level of maturity from KM point of view.
Resumo:
Knowledge Management (KM) is vital factor to successfully undertake projects. The temporary nature of projects necessitates employing useful KM practices for tackling issues such as knowledge leakiness and rework. The Project Management Office (PMO) is a unit within organizations to facilitate and oversee organizational projects. Project Management Maturity Models (PMMM) shows the development of PMOs from immature to mature levels. The existing PMMMs have focused on discussing Project Management (PM) practices, however, the management of project knowledge is yet to be addressed, at various levels of maturity. This research project was undertaken to investigate the mentioned gap for addressing KM practices at the existing PMMMs. Due to the exploratory and inductive nature of this research, qualitative methods were chosen as the research methodology. In total, three cases selected from different industries: research; mining and government organizations, to provide broad categories for research and research questions were examined using the developed framework. This paper presents the partial findings of undertaken investigation of the research organisation with the lowest level of maturity. The result shows that knowledge creation and capturing are the most important processes, while knowledge transferring and reusing are not as important as the other two processes. In addition, it was revealed that provision of “knowledge about client” and “project management knowledge” are the most important types of knowledge that are required at this level of maturity. In conclusion, the outcomes of this paper shall provide powerful guidance to PMOs at lowest level of maturity from KM point of view.
Resumo:
Atualmente não é possível pensar em gestão de projetos sem uma boa ferramenta apoiada em Tecnologia da Informação. Este trabalho estudou o processo de implantação e personalização do Microsoft Project Server na Câmara dos Deputados com o objetivo de avaliar se essa implantação se deu de maneira adequada segundo as melhores práticas de gestão de projetos, além de levantar as principais lições aprendidas no processo. Para tanto foi realizada uma pesquisa documental, em que, na primeira parte fez-se um apanhado em nível teórico das melhores práticas de gestão de projetos, notadamente PMBOK do PMI e a consulta a autores relevantes no contexto da gestão de projetos e da aprendizagem organizacional. Em um segundo momento foram pesquisados documentos relacionados ao processo de implantação como o edital de licitação, atas de reunião, atos normativos, dentre outros. Dos dados levantados foram identificadas falhas por parte da Câmara dos Deputados tais como elevado número de exigências de personalizações no ambiente e conhecimento limitado, a priori, da ferramenta, de suas capacidades e limitações. Por parte da contratada, observou-se falhas como desorganização, planejamento ruim, descumprimento de prazos, pendências, grandes atrasos e mudanças na equipe técnica do projeto. Pela análise dessas falhas, levantaram-se diversas lições aprendidas no processo. Por fim, concluiu-se que o processo de implantação do Microsoft Project Server na Câmara dos Deputados foi parcialmente adequado, pois apesar de ao final estar implantado de acordo com o escopo requerido, o processo como um todo apresentou muitas falhas.
Resumo:
O contexto da era da informação exige novas habilidades para competir com sucesso, tanto para empresas industriais como para as de serviços. Desde o seu surgimento, a Engenharia de Software tem enfrentado o desafio em estimar, controlar e gerenciar custos no processo de desenvolvimento de software. Os custos são parte de um projeto de software e nem sempre são claramente mensurados. Algumas desenvolvedoras de software são caracterizadas como prestadoras de serviços e as organizações que prestam serviços possuem as mesmas dificuldades em termos gerenciais que as indústrias, elas precisam de sistemas de gestão adequados para gerir seus custos, logo seus recursos. Nesse contexto é que os sistemas de informações contábeis estão inseridos, fornecendo respostas que os gestores necessitam para tomar decisões. Os custos são exemplos desse tipo de informação, pois o seu conhecimento é indispensável para uma boa gerência dos recursos organizacionais. O Custeio Baseado em Atividades (ABC) é uma ferramenta contábil útil para o gerenciamento estratégico dos custos uma vez que os sistemas de custeio tradicionais já não atendem essa necessidade das organizações. Diante desse cenário, o objetivo geral dessa dissertação é aplicar a metodologia de custeio baseado em atividades em um projeto de desenvolvimento de software com a finalidade de gestão de custos. Este pesquisa caracteriza-se como qualitativa descritiva e faz uso do método do estudo de caso. Através desse estudo foi possível comprovar a utilidade do ABC como instrumento de auxílio na gestão de custos nas organizações que prestam serviços em desenvolvimento de software, pois possibilita a visualização da maneira que os recursos são consumidos pelas atividades que agregam e não agregam valor ao negócio e ao cliente.
Resumo:
For any proposed software project, when the software requirements specification has been established, requirements changes may result in not only a modification of the requirements specification but also a series of modifications of all existing artifacts during the development. Then it is necessary to provide effective and flexible requirements changes management. In this paper, we present an approach to managing requirements changes based on Booth’s negotiation-style framework for belief revision. Informally, we consider the current requirements specification as a belief set about the system-to-be. The request of requirements change is viewed as new information about the same system-to-be. Then the process of executing the requirements change is a process of revising beliefs about the system-to-be. We design a family of belief negotiation models appropriate for different processes of requirements revision, including the setting of the request of requirements change being fully accepted, the setting of the current requirements specification being fully preserved, and that of the current specification and the request of requirements change reaching a compromise. In particular, the prioritization of requirements plays an important role in reaching an agreement in each belief negotiation model designed in this paper.
Resumo:
Few studies to date have paid attention to relationship management when addressing performance problems. To bridge the knowledge gap, a questionnaire survey is conducted to analyze the impact of relationship management on project performance in construction. The analysis reveals that the deterioration of working relationships may increase the likelihood of poor performance. Poor performance can be effectively reduced by improving some aspects of working relationships. Collaborative working contributes to performance improvement, in which long-term collaboration is more effective than short-term collaboration. In addition to the questionnaire survey, a series of expert interviews provide a deeper insight into effective relationship management.
Resumo:
Risk management in software engineering has become a recognized project management practice but it seems that not all companies are systematically applying it. At the same time, agile methods have become popular, partly because proponents claim that agile methods implicitly reduce risks due
to, for example, more frequent and earlier feedback, shorter periods of development time and easier prediction of cost. Therefore, there is a need to investigate how risk management can be usable in iterative and evolutionary software development processes. This paper investigates the gathering of empirical data on risk management from the project environment and presents
a novel approach to manage risk in agile projects. Our approach is based on a prototype tool, Agile Risk Tool (ART). This tool reduces human effort in risk management by using software agents to identify, assess and monitor risk, based on input and data collected from the project environment and by applying
some designated rules. As validation, groups of student project data were used to provide evidence of the efficacy of this approach. We demonstrate the approach and the feasibility of using a lightweight risk management tool to alert, assess and monitor risk with reduced human effort.
Resumo:
The term commercial management has been used for some time, similarly the job title commercial manager. However, as of yet, little emphasis has been placed on defining. This paper presents the findings from a two-year research initiative that has compared and contrasted the role of commercial managers from a range of organisations and across industry sectors, as a first step in developing a body of knowledge for commercial. It is argued that there are compelling arguments for considering commercial management, not solely as atask undertaken by commercial managers, but as a discipline in itself: a discipline that, arguably, bridges traditional project management and organisational theories. While the study has established differences in approach and application both between and within industry sectors, it has established sufficient similarity and synergy in practice to identify a specific role of commercial management in project-based organisations. These similarities encompass contract management and dispute resolution; the divergences include a greater involvement in financial and value management in construction and in bid management in defence/aerospace.
Resumo:
This paper aims to bring more information related to the critical question "how IT areas of insurance companies are defining and delivering their strategic initiatives Portfolios?" and make conclusions based on the collected data. To reach these interpretations, it is composed of a theoretical investigation on the theme, a strategy delineation for the research methodology and a conclusion presentation based on the findings. In this last part, this study concluded that explored organization does not applied a sufficient number of best practices answering the critical question as "the company is not mature on this subject".