This thesis deals with the subject of project management, primarily from the viewpoint of the development of a tool for project management support using the PRINCE2 methodology and the Unicorn Universe information system. The subject of the theoretical part is the definition of a project and project management and a description and a comparison of the most widely used project management standards, PRINCE2, PMI and IPMA. Subsequently, the emphasis is put on a detailed description of PRINCE2 with regard to its use in the next parts of the work. At the end of the theoretical part of the thesis the chapters are devoted to Unicorn Universe and to Unicorn Enterprise System Powered Company, which is a methodology used for company management. In the practical part, the author followed the recommended 4-phases process of the development of a new methodology set defined by the UESPC methodology; inception, elaboration, construction and transition. By means of the analysis in inception and elaboration stages and creation of A4 and High Level Concept documents, which describe specific ways how to implement various elements of PRINCE2into the Unicorn Universe, and the subsequent production of project management tool prototype, the author worked his way up to the construction stage, in which he designed and created definitions of meta artifacts and scripts for their later implementation in the final phase, called transition. In this phase metaartifacts were set up. They are templates for management and control artifacts and for other items necessary for the production of the methodological set, a final product of the thesis. At the end of thesis, the automation scripts, as proposed in the previous stage to verify the practical use of the thesis product, were assigned for implementation.

The goal of this thesis is creation of methodology for repeatable transformation of customer business needs and goals resulting from company IT strategy to system functionality and process implementation in Business/IT Service Management projects using BMC Atrium and Remedy products. This methodology will be based on existing project management methodologies PRINCE2 and SCRUM. In the thesis I also refer to parts of ITIL v3 process framework. The aim of the thesis is to provide a project delivery framework for IT Consultancy organizations. The framework will foster efficient planning, tracking and communication of requirements and deliverables between IT Consultancy and their customer during entire project lifecycle and will therefore enable repeatable and consistent high quality delivery of customer success.

This master's thesis deals with the area of risk management in project management. The aim is to create a complex risk management methodology and a functional prototype of the system that complements and supports it. The methodology is based on the fundamental principles of these areas and the analysis of currently used project and risk management approaches in practice. Selected were PRINCE2, Agile Approach and ITIL. The advantages of the methodology are its complexity, no bound to any standard but based on methodology's positive  features. Based on the methodology, a web application for management and visualization of projects and risks has been developed and supports work with it.

Diploma thesis deals with project management methodology and its application into enterprise environment. The theoretical part describes exact methods of project management and it’s standards and structure. The analytical part describes the situation in company A.S., its corporate structure and the methodology used by management. The practical part follows the previous chapters, describes project management according to the chosen methodology and the results are interpreted both in terms of project success and as compared to the existing methodology.

La presente investigación abunda en los conceptos relacionados a los retrasos que ocurren en una obra y a las causas del ineficiente seguimiento y control realizado al cronograma contractual de proyectos de construcción de la ciudad de Lima Metropolitana. Asimismo, se recaudó información de metodologías y herramientas a la vanguardia y se levantó la información de 3 proyectos de construcción de edificaciones multifamiliares. A partir de la información de estos proyectos, se identificaron los principales problemas de cada metodología que terminaron causando retrasos sobre los plazos contractuales de los mismos. Estos problemas pudieron ser agrupados en tres principalmente: la inadecuada planificación, la inadecuada programación y el vínculo débil o inexistente entre ambos. A partir de lo mencionado, se propuso una metodología con el principal objetivo de brindar una guía hacia los contratistas para realizar un seguimiento efectivo al plazo contractual de sus proyectos y prevenir todo retraso. / This investigation reviews the concepts related to the delays that occur in construction projects and the causes of the inefficient monitoring and control made to the contractual schedule in multi-family building projects developed in the city of Lima, Peru. Information was collected on methodologies and tools being used worldwide as well as from 3 multi-family constriction building projects. From the information of these projects, the main problems of each methodology that ended up causing delays over their contractual schedule were identified. Problems identified were grouped into three: inadequate planning, inadequate programming and a weak or non-existent link between the two. Based on this analysis, a methodology was proposed with the main purpose of providing a guide to contractors to effectively monitor the contractual schedule of their projects and prevent any delay. / Tesis

Purpose – This research aims to explore the effectiveness of utilising Benefits Realisation Management (BRM) as part of comprehensive success measures, emphasising the stage in-between appraisal and evaluation of projects in the UK public sector. Design/methodology/approach – The study is constructed as a qualitative case study. Semi-structured interviews are used as part of the inductive, exploratory approach to achieve the study's objectives. It employs an approach based on grounded theory for its analysis. Findings – This paper suggests that Benefits Realisation Management is not used effectively in the UK public sector during projects lifetime to control and monitor projects and ensure their success. The current reviews of projects and programmes, through their execution, may not be sufficient. Research limitations/implications – This study offers contributions to the project success literature and benefits management literature by adding empirically supported insights about BM utilisation during project reviews. The research may be limited primarily by the research method – predominantly the snow-balling data collection. The assumptions made about the UK public sector may limit the broader generalisation of the findings. Practical implications – This research may be used to advise the practising managers of the need to maintain benefits orientation after appraisal throughout a project's lifetime and after delivery. Project governance structures are advised to update and improve their current project review practices. The study additionally identifies possible obstacles to the process and biases. Originality/value – This paper attempts to fill a literature gap by providing empirical results that explore the success definition and measures and the effectiveness of BRM during project execution and gate reviews. Keywords: Benefits Management; Project Success; Project Performance; Performance Measurement; Public Sector. Paper type: Research Thesis

The aim of this study is to investigate whether a combination of agile system development methodologies (ASDMs) and project management methodologies (PMMs) can be used to develop a hybrid APMM that will have the ability to deliver information technology (IT) projects successfully in a constantly changing business and project environment. To achieve this objective, a literature review was conducted on the relatively well–established ASDMs by firstly defining a SDM and an ASDM. Each ASDM and its effectiveness are described, after which ASDMs in general are evaluated by considering their area of application, advantages and disadvantages. A comparison is then done of the seven different ASDMs using the four elements of an SDM (Huisman & Iivari, 2006:32) to emphasise some of the main similarities and differences amongst the different ASDMs. The seven ASDMs investigated in this study are Dynamic System Development Methodology, Scrum, Extreme Programming, Feature Driven Development, Crystal ASDMs ? Crystal Clear and Crystal Orange in particular, Adaptive Software Development and Lean Development. A literature review was also conducted on two structured and relatively well–established PMMs, PMBOK and PRINCE2, and a relatively new PMM called Agile Project Management. Each PMM is evaluated by considering their area of application, advantages, disadvantages and integration with other methodologies, after which a comparison is made of the different PMMs. The research was conducted by following a mixed methods research plan, which included the mixed methods research paradigm (combination of the interpretive research paradigm and the positivistic research paradigm), research methods (design science, case study and survey), quantitative and qualitative data–collection techniques (interviews and questionnaires), and dataanalysis techniques (cross–case and statistical). The reasons that projects fail and critical project success factors were studied and summarised to form the critical project success criteria, which were used to create the agile project success criteria. The ASDM best practice and PMM best practice frameworks were created by identifying whether a certain ASDM or PMM would satisfy a specific agile project success factor (APSF) of the agile project success criteria. The findings of each APSF in the respective frameworks were used as a foundation to develop a hybrid APMM (ver. 0) that would address the agile project success criteria. The hybrid APMM (ver. 0) was developed interpretively using design science (research approach) and constructivism by combining the strengths, addressing the weaknesses and bridging the gaps identified in the frameworks. The hybrid APMM (ver. 0) was then evaluated and improved by conducting an interpretive case study, which entailed interviewing participants from large and small organisations. Once the qualitative data collected had been analysed using cross–case analysis, the findings were incorporated in order to create an improved hybrid APMM (ver. 1). The hybrid APMM (ver. 1) too was evaluated and improved by conducting a survey, which entailed administering questionnaires to various respondents in order to collect quantitative and qualitative data. The findings of the statistical analysis of the data were also used to improve the hybrid APMM (ver. 1), resulting in the final hybrid APMM (ver. 2). This study demonstrates that a combination of ASDMs and PMMs can be used to develop a hybrid APMM with the ability to deliver IT projects in a constantly changing project and business environment. / Thesis (Ph.D. (Computer Science))--North-West University, Potchefstroom Campus, 2012.

The aim of this study is to investigate whether a combination of agile system development methodologies (ASDMs) and project management methodologies (PMMs) can be used to develop a hybrid APMM that will have the ability to deliver information technology (IT) projects successfully in a constantly changing business and project environment. To achieve this objective, a literature review was conducted on the relatively well–established ASDMs by firstly defining a SDM and an ASDM. Each ASDM and its effectiveness are described, after which ASDMs in general are evaluated by considering their area of application, advantages and disadvantages. A comparison is then done of the seven different ASDMs using the four elements of an SDM (Huisman & Iivari, 2006:32) to emphasise some of the main similarities and differences amongst the different ASDMs. The seven ASDMs investigated in this study are Dynamic System Development Methodology, Scrum, Extreme Programming, Feature Driven Development, Crystal ASDMs ? Crystal Clear and Crystal Orange in particular, Adaptive Software Development and Lean Development. A literature review was also conducted on two structured and relatively well–established PMMs, PMBOK and PRINCE2, and a relatively new PMM called Agile Project Management. Each PMM is evaluated by considering their area of application, advantages, disadvantages and integration with other methodologies, after which a comparison is made of the different PMMs. The research was conducted by following a mixed methods research plan, which included the mixed methods research paradigm (combination of the interpretive research paradigm and the positivistic research paradigm), research methods (design science, case study and survey), quantitative and qualitative data–collection techniques (interviews and questionnaires), and dataanalysis techniques (cross–case and statistical). The reasons that projects fail and critical project success factors were studied and summarised to form the critical project success criteria, which were used to create the agile project success criteria. The ASDM best practice and PMM best practice frameworks were created by identifying whether a certain ASDM or PMM would satisfy a specific agile project success factor (APSF) of the agile project success criteria. The findings of each APSF in the respective frameworks were used as a foundation to develop a hybrid APMM (ver. 0) that would address the agile project success criteria. The hybrid APMM (ver. 0) was developed interpretively using design science (research approach) and constructivism by combining the strengths, addressing the weaknesses and bridging the gaps identified in the frameworks. The hybrid APMM (ver. 0) was then evaluated and improved by conducting an interpretive case study, which entailed interviewing participants from large and small organisations. Once the qualitative data collected had been analysed using cross–case analysis, the findings were incorporated in order to create an improved hybrid APMM (ver. 1). The hybrid APMM (ver. 1) too was evaluated and improved by conducting a survey, which entailed administering questionnaires to various respondents in order to collect quantitative and qualitative data. The findings of the statistical analysis of the data were also used to improve the hybrid APMM (ver. 1), resulting in the final hybrid APMM (ver. 2). This study demonstrates that a combination of ASDMs and PMMs can be used to develop a hybrid APMM with the ability to deliver IT projects in a constantly changing project and business environment. / Thesis (Ph.D. (Computer Science))--North-West University, Potchefstroom Campus, 2012.

Goal of this thesis is to provide a summary of information connected to cloud project management. The thesis describes, what cloud is, what types of cloud there are and also describes project management methodologies and their specifics. In the practical part of this thesis one of the methodologies is applied to a practical project. The thesis contains also a summary of practical information about cloud projects and risks associated with cloud projects.

This thesis describes project management methodology implementation in a consulting company and examines the impact of this methodology on key success factors of the company. The theoretical part deals with issues related to project management implementation in a company and describes well-known methods and standards in this area while focusing on PRINCE2 methodology, which has been chosen for the implementation. The theoretical part continues by describing the process of creating system dynamics models, which allowed the key success factor models to be created as tools for evaluation of the methodology implementation impacts. The practical part of this thesis describes the background for the methodology implementation project and then the implementation itself in detail. The practical part continues by showing and describing the created key success factor models. In the end, the methodology impacts evaluation is carried out, analyzing changes in separate elements of the model breakdown.