O gerenciamento de projetos de forma sistematizada vem se tornando essencial para todo tipo de organização, pois os mercados a cada dia tornam-se cada vez mais competitivos, os recursos mais escassos e os clientes muito mais exigentes. É possível observar isso com o número crescente de empresas que se associam ao Project Management Institute (PMI) - referência nas melhores práticas em gerenciamento de projetos - que desde o final de 2013 possui mais de 400.000 empresas associadas em todo o planeta. Tal tendência é natural, visto que as empresas necessitam se destacar nos negócios em um mercado cada vez mais dinâmico a fim de garantir a sua sobrevivência. De acordo com Gu et al. (2013), uma questão-chave na investigação de gerenciamento de projetos gira em torno de porquê alguns projetos são bem sucedidos, enquanto outros não. Esta questão levou os pesquisadores a explorar determinantes potenciais que possam levar ao sucesso ou fracasso de um projeto. Por exemplo, o Standish Group International (2009) encontrou uma taxa global de fracasso do projeto em torno de 72% nos EUA. É certo que a cultura organizacional exerce forte influência no sucesso dos projetos, mas seria possível diagnosticá-la para com isso melhor conduzir as equipes de projeto? Deste modo, o objetivo do presente estudo foi analisar a relação entre a cultura organizacional e o gerenciamento de projetos, utilizando-se para tanto dos modelos como o Competing Values Framework (CVF) e o Organizational Culture Assessment Instrument (OCAI). O emprego dos modelos se justifica por serem os mais utilizados na literatura em gestão organizacional, embora não tenham sido encontrados estudos empíricos que os utilize no contexto brasileiro em gerenciamento de projetos. O método utilizado para obtenção do perfil cultural dominante para o sucesso em gerenciamento de projetos foi survey, na qual o modelo OCAI foi adaptado e destinado para gerentes e membros de equipe de projetos. Observou-se através da análise dos dados, que a cultura de clã foi a que apresentou forte influência para o sucesso no gerenciamento de projetos de acordo com a percepção dos respondentes da survey. É importante ressaltar que não há um perfil de cultura melhor que o outro, portanto, a cultura de gerenciamento de projetos obtida é apenas o diagnóstico de uma cultura organizacional que poderá permitir a obtenção de um desempenho superior, ou seja, sucesso no atendimento de escopo, qualidade, custo e prazo. Discute-se para estudos futuros a importância de se empregar respondentes de diferentes estados do Brasil e ainda de outros países, buscando estabelecer que não existam influências de outros fatores culturais regionais na percepção dos respondentes. / Project management in a systematic manner has become essential for any type of organization, because the markets every day become increasingly competitive, scarce resources and more demanding customers. You can see this with the growing number of companies that are associated with the Project Management Institute (PMI) - reference the best practices in project management - which since late 2013 has more than 400,000 affiliates around the world. This tendency is natural, since companies need to stand out in business in an increasingly dynamic market in order to ensure their survival. According to Gu et al. (2013), a key issue in project management research centers on why some projects are successful while others do not. This question led the researchers to explore potential determinants that can lead to success or failure of a project. For example, the Standish Group International (2009) found an overall rate of failure of the project around 72% in the US. Admittedly, the organizational culture has a strong influence on the success of the projects, but it would be possible to diagnose it for it better lead project teams? Thus, the aim of this study is to analyze the relationship between organizational culture and project management, using for both models like the Competing Values Framework (CVF) and the Organizational Culture Assessment Instrument (OCAI). The use of models is justified because they are the most used in the literature on organizational management, although we did not find empirical studies that use them in the Brazilian context in project management. The method used to obtain the dominant cultural profile for success in project management was the survey, in which the OCAI model was adapted and designed for managers and project team members. It was observed by analyzing the data, the clan culture showed the strong influence for success in project management according to the perception of the survey respondents. Importantly, there is a better culture profile than the other, so the obtained project management culture is only the diagnosis of an organizational culture that may allow obtaining superior performance, ie success in scope of service, quality, cost and schedule. It is argued for further study the importance of employing respondents from different states of Brazil and even from other countries, seeking to establish that there are no influences from other regional cultural factors in the perception of respondents.

O gerenciamento de projetos de forma sistematizada vem se tornando essencial para todo tipo de organização, pois os mercados a cada dia tornam-se cada vez mais competitivos, os recursos mais escassos e os clientes muito mais exigentes. É possível observar isso com o número crescente de empresas que se associam ao Project Management Institute (PMI) - referência nas melhores práticas em gerenciamento de projetos - que desde o final de 2013 possui mais de 400.000 empresas associadas em todo o planeta. Tal tendência é natural, visto que as empresas necessitam se destacar nos negócios em um mercado cada vez mais dinâmico a fim de garantir a sua sobrevivência. De acordo com Gu et al. (2013), uma questão-chave na investigação de gerenciamento de projetos gira em torno de porquê alguns projetos são bem sucedidos, enquanto outros não. Esta questão levou os pesquisadores a explorar determinantes potenciais que possam levar ao sucesso ou fracasso de um projeto. Por exemplo, o Standish Group International (2009) encontrou uma taxa global de fracasso do projeto em torno de 72% nos EUA. É certo que a cultura organizacional exerce forte influência no sucesso dos projetos, mas seria possível diagnosticá-la para com isso melhor conduzir as equipes de projeto? Deste modo, o objetivo do presente estudo foi analisar a relação entre a cultura organizacional e o gerenciamento de projetos, utilizando-se para tanto dos modelos como o Competing Values Framework (CVF) e o Organizational Culture Assessment Instrument (OCAI). O emprego dos modelos se justifica por serem os mais utilizados na literatura em gestão organizacional, embora não tenham sido encontrados estudos empíricos que os utilize no contexto brasileiro em gerenciamento de projetos. O método utilizado para obtenção do perfil cultural dominante para o sucesso em gerenciamento de projetos foi survey, na qual o modelo OCAI foi adaptado e destinado para gerentes e membros de equipe de projetos. Observou-se através da análise dos dados, que a cultura de clã foi a que apresentou forte influência para o sucesso no gerenciamento de projetos de acordo com a percepção dos respondentes da survey. É importante ressaltar que não há um perfil de cultura melhor que o outro, portanto, a cultura de gerenciamento de projetos obtida é apenas o diagnóstico de uma cultura organizacional que poderá permitir a obtenção de um desempenho superior, ou seja, sucesso no atendimento de escopo, qualidade, custo e prazo. Discute-se para estudos futuros a importância de se empregar respondentes de diferentes estados do Brasil e ainda de outros países, buscando estabelecer que não existam influências de outros fatores culturais regionais na percepção dos respondentes. / Project management in a systematic manner has become essential for any type of organization, because the markets every day become increasingly competitive, scarce resources and more demanding customers. You can see this with the growing number of companies that are associated with the Project Management Institute (PMI) - reference the best practices in project management - which since late 2013 has more than 400,000 affiliates around the world. This tendency is natural, since companies need to stand out in business in an increasingly dynamic market in order to ensure their survival. According to Gu et al. (2013), a key issue in project management research centers on why some projects are successful while others do not. This question led the researchers to explore potential determinants that can lead to success or failure of a project. For example, the Standish Group International (2009) found an overall rate of failure of the project around 72% in the US. Admittedly, the organizational culture has a strong influence on the success of the projects, but it would be possible to diagnose it for it better lead project teams? Thus, the aim of this study is to analyze the relationship between organizational culture and project management, using for both models like the Competing Values Framework (CVF) and the Organizational Culture Assessment Instrument (OCAI). The use of models is justified because they are the most used in the literature on organizational management, although we did not find empirical studies that use them in the Brazilian context in project management. The method used to obtain the dominant cultural profile for success in project management was the survey, in which the OCAI model was adapted and designed for managers and project team members. It was observed by analyzing the data, the clan culture showed the strong influence for success in project management according to the perception of the survey respondents. Importantly, there is a better culture profile than the other, so the obtained project management culture is only the diagnosis of an organizational culture that may allow obtaining superior performance, ie success in scope of service, quality, cost and schedule. It is argued for further study the importance of employing respondents from different states of Brazil and even from other countries, seeking to establish that there are no influences from other regional cultural factors in the perception of respondents.

This research focuses on the role that polychronic Communication (PC) plays in the productivity and project success of Information Technology (IT) Project Managers (PMs). PC refers to a communication style where the communicator switches rapidly between several conversations, irrespective of topic similarity, instead of completing one conversation before starting another. An online questionnaire collected data from Information Technology workers in multiple industries across the globe. The data consisted out of two distinct groups: IT PMs (n = 202) and IT project team members (n = 122). Statistical analysis on the dataset considered the perspectives of both participant groups, first separately and then combined. The results showed relationships between: 1. IT PMs’ individual polychronicity and their PC. 2. IT PMs’ PC and their opinion of the influence of PC on the success of the projects that they are managing. 3. IT PMs’ PC and their opinion of the influence of PC on their productivity. 4. IT PMs’ PC and the corporate polychronicity of their employers. In addition, when IT PMs rate their PC, the rating is lower than when other IT project team members rate the IT PMs’ PC. By contrast, there was no difference between IT PMs rating the influence of their PC on their project success and productivity versus IT project teams rating the influence of the IT PMs’ PC on their project success and productivity. These findings contribute to the factors that a corporation has to consider in hiring new IT PMs or training their current IT PMs. / Information Science / M. Sc. (Information Systems)

The diploma paper introduces and, consequently, compares the worldwide accepted project management standards PMBOK Guide and CzNCB and ASAP Methodology for Implementation. Project management standards were presented by PMI and IPMA organizations, ASAP Methodology for Implementation was developed by SAP organization. The theoretical background is further applied on real situations within projects of implementations of SAP solutions that are realized by the company NESS Czech s.r.o.. Possible difficulties, which may arise during every implementation of SAP solutions, are being identified due to knowledge and experience of project managers and solution architects of NESS Czech s.r.o., not only during each phase of ASAP Methodology for Implementation but also during pre-implementation project phase. After settling the role and responsibilities of the supplier's project manager, the solutions how to avoid and/or react on possible difficulties, in charge of supplier's project manager, are being indicated.

本研究在探討專案經理管理專案逐步完善的過程 (Progressive Elaboration)中，面對接踵而來的專案變更 (Change) 以及不確定性 (Uncertainty)，如何能以客戶觀點來看待專案管理的利害得失 ( Advantage / Disadvantage / Gain / Lost )，滿足客戶需求以創造客戶價值。 本研究認為專案管理的重點在於專案變更管理。藉由策略行銷4C架構的思維，將能有效彌補專案經理在企管知識與經驗上落差，將專案管理的重點聚焦在客戶關心的專案管理重點上，透過行銷交換上四個成本問題的解決，來為客戶與專案創造價值。本研究透過以客戶與專案經理的不同觀點來回顧與檢討兩個實務個案，建議在管理專案時以策略行銷4C架構思維作為和客戶溝通的思考架構，聚焦於如何兼顧三重限制下，把專案管理的價值提升到同時滿足專案與商業的成功。換言之，藉由行銷交換四大成本問題的解決來“作對的事”(Do the right thing)以滿足客戶的期望，而讓專案管理方法論聚焦於專案管理團隊如何管理專案，來解決“把事作對”(Do the thing right) 的問題。

Η ΒΥΠ διαθέτει αντίτυπο της διατριβής σε έντυπη μορφή στο βιβλιοστάσιο διδακτορικών διατριβών που βρίσκεται στο ισόγειο του κτιρίου της. / Στα πλαίσια της παρούσας Μεταπτυχιακής Διπλωματικής Εργασίας, προτείνουμε (α) μια ταξινόμηση των πιο σημαντικών ερευνητικών αποτελεσμάτων για την επιστημονική περιοχή του Web Engineering και (β) μια μεθοδολογία για την αξιολόγηση εργαλείων για τον ίδιο χώρο τα οποία θα ενσωματωθούν στο WEP (WEB-Engineering Resources Portal). Στην συγκεκριμένη εργασία αναλύονται οι επιστημονικές έννοιες Body of Knowledge(BOK), Software Engineering, Web Engineering, Software Engineering Body of Knowledge (SWEBOK) και γίνεται μια πρώτη προσπάθεια θεμελίωσης ενός Σώματος Γνώσης (Body of Knowledge) για το Web Engineering, που θα εμπεριέχεται στο WEP. Για την ταξινόμηση των ερευνητικών αποτελεσμάτων του WEP βασιστήκαμε στη δομή του SWEBOK (Software Engineering Body of Knowledge), το οποίο αποτελεί μια προσπάθεια της IEEE (Institute of Electrical and Electronics Engineers) για τον καθορισμό και τη μελέτη ενός Σώματος Γνώσης της Επιστήμης Λογισμικού, μια επιστημονική περιοχή που συγγενεύει άμεσα με το Web Engineering. Όσο αφορά την εύρεση και αξιολόγηση εργαλείων για το WEP προτείνουμε έναν αλγόριθμο επιλογής και αξιολόγησης ο οποίος βασίζεται κυρίως στην κατηγοριοποίηση και αξιολόγηση εφαρμογών από τους Ιστότοπους http://www.tucows.com και http://www.download.com, οι οποίοι επιλέχτηκαν βάσει της δημοτικότητά τους και της πληθώρας και καλής οργάνωσης των εργαλείων τους. Τα αποτελέσματα από την εφαρμογή αυτού του αλγορίθμου αξιολόγησης εργαλείων ήταν αρκετά ικανοποιητικά, ενώ υπάρχουν περιθώρια βελτίωσης τόσο με τη χρήση επιπλέον παραμέτρων από τους δύο παραπάνω βασικούς Ιστότοπους όσο και με τη συνεισφορά στοιχείων και από άλλους Ιστότοπους. / In this Master Thesis, we suggest (a) A methodology of classification of the most important research results in Web Engineering (b) A methodology of selection and evaluation web development tools. These tools would be in included in WEP (WEB-Engineering Resources Portal). During this Master Thesis the following definitions are explained: Body of Knowledge (BOK), Software Engineering, Web Engineering, Software Engineering Body of Knowledge (SWEBOK). Moreover, it is suggested a solution of building a “Body of Knowledge” in the field of Web Engineering. This Body of Knowledge would be included in WEP. The basis for the classification of the research results is WEP was the SWEBOK (Software Engineering Body of Knowledge). SWEBOK is an effort of IEEE, in order to establish a baseline for the “Body of Knowledge” for the field of Software Engineering, which is close related with the field of Web Engineering. As far is concerned the selection and evaluation of web development tools, we suggest an algorithm which is based on the classification and evaluation of web development tools by the web sites http://www.tucows.com and http://www.download.com. These web sites have been selected, due to their credibility, popularity and the large number of tools which are presented. Although this algorithm has quite good results, there are some open issues by including more parameters from the 2 main web sites and by investigating other similar web sites, too.

This research focuses on the role that polychronic Communication (PC) plays in the productivity and project success of Information Technology (IT) Project Managers (PMs). PC refers to a communication style where the communicator switches rapidly between several conversations, irrespective of topic similarity, instead of completing one conversation before starting another. An online questionnaire collected data from Information Technology workers in multiple industries across the globe. The data consisted out of two distinct groups: IT PMs (n = 202) and IT project team members (n = 122). Statistical analysis on the dataset considered the perspectives of both participant groups, first separately and then combined. The results showed relationships between: 1. IT PMs’ individual polychronicity and their PC. 2. IT PMs’ PC and their opinion of the influence of PC on the success of the projects that they are managing. 3. IT PMs’ PC and their opinion of the influence of PC on their productivity. 4. IT PMs’ PC and the corporate polychronicity of their employers. In addition, when IT PMs rate their PC, the rating is lower than when other IT project team members rate the IT PMs’ PC. By contrast, there was no difference between IT PMs rating the influence of their PC on their project success and productivity versus IT project teams rating the influence of the IT PMs’ PC on their project success and productivity. These findings contribute to the factors that a corporation has to consider in hiring new IT PMs or training their current IT PMs. / Information Science / M. Sc. (Information Systems)

<p>No organisation has an endless and unlimited supply of money, especially in a recessive economy, and therefore decisions have to be made as to which areas an organisation will invest in. As organisations, such as YZ1 financial services organisation, are focused on seeing returns on investment (ROI), implementing software that is not being used&nbsp / will not render any benefits to the organisation. Research problem: Project Managers (PMs) in YZ organisation&rsquo / s IT department need to perform mandated processes, as&nbsp / defined in their centralised repository. PMs need to use Financial and Planning Software (FPS)2 software to perform certain project management activities, as required by their&nbsp / job function. However, it was found that MPP3 software, another tool, was used for more detailed project schedules, as well as activities that were not strictly enforced by&nbsp / management, the Project Office or the Quality Assurance team. Therefore, from this discovery, it was not clear whether the intended benefit of implementing this mandatory&nbsp / software (FPS) was being realised &ndash / since implementing software that is not being utilised fully would not deliver the intended benefits to the IT department (Devaraj &amp / Kohli&nbsp / 2003), even if the software is termed &lsquo / mandatory&rsquo / . Objective: The primary objective of this research was to explore and optimise the key success factors for an effective&nbsp / implementation of mandatory software in a department, in order to derive the intended business benefits. Literature Review: Literature was reviewed in the search for models or&nbsp / theories that explore the relationship between the use of mandatory software and the achievement of business benefits. The Information Management Body of Knowledge&nbsp / (IMBOK) was selected as this framework defines the relationship between IT and the realisation of business benefits, and ultimately the achievement of any business strategy. The literature review focused predominantly on the level of user involvement, change management, as well as factors that influence the usage of mandatory software by&nbsp / individuals. 1. The name of the organisation utilised has been changed. Refer to Ethical Consideration 2. The name of the tools utilised has been changed. Refer to Ethical&nbsp / Consideration and list of acronyms 3. The name of the tools utilised has been changed. Refer to Ethical Consideration and list of acronyms. Focus was given to organisational factors affecting usage, such as top management support and organisational processes. A model was compiled using unique constructs in the Technology Acceptance Model&nbsp / (and TAM2), the Motivational Model (MM) and the Model of PC Utilisation (MPCU) &ndash / in order to test user acceptance of mandatory software. The literature study concludes with a&nbsp / review of an approach to benefits management including five stages, namely: identifying and structuring benefits, planning for the realisation of benefits, executing the plan, in&nbsp / addition to the evaluation and the review. Research design and methodology: A case study was used in this research, as it examined the phenomenon in its natural setting,&nbsp / &nbsp / &nbsp / employing multiple methods of data collection to gather information from a few entities (groups and data sources). In this way, it was not limited to only qualitative or quantitative&nbsp / approaches, but utilised mixed methods instead. A mixed methods approach was used in order to elaborate, enhance and clarify the results from the qualitative research&nbsp / through the results of the quantitative analysis. Findings: The main finding, based on the compilation of three models of user acceptance, proved that FPS was not being utilised&nbsp / as intended. There was also no evidence of an improvement in business operations. Therefore, benefits management was negatively impacted. Organisational processes were&nbsp / dentified as the most important organisational factor, influencing the usage of FPS software. Own technological capability was considered to be the least important factor,&nbsp / as respondents believed that they had sufficient IT skills in order to learn how to use FPS software. Change management was rated negatively / and as a result, it impacted the&nbsp / usage of FPS, as users were not involved in the decision to implement, and had limited interaction in the implementation process. In addition, there was no evidence found that&nbsp / benefits management was conducted in the IT department / and therefore, the impact of using alternative software could not be quantitatively assessed. Recommendations: In concluding this research, it is recommended that the &ldquo / best practice&rdquo / , derived from the pertinent literate should be followed more diligently if YZ organisation is to benefit from the&nbsp / implementation of mandatory software. For example, in this research, it was found that top management&rsquo / s support of FPS (second most important organisational factor influencing use) was lacking, despite the literature suggestion that senior management involvement in changing technology is crucial for organisational commitment. It is&nbsp / suggested that a more formal approach to benefits management should be implemented. It is also recommended that further study should be conducted &ndash / in order to explore&nbsp / the applicability of the Japanese framing (achieving benefits from IT software through the concept of strategic instinct, rather than strategic alignment) in the context of a&nbsp / developing country (such as South Africa).</p>

<p>No organisation has an endless and unlimited supply of money, especially in a recessive economy, and therefore decisions have to be made as to which areas an organisation will invest in. As organisations, such as YZ1 financial services organisation, are focused on seeing returns on investment (ROI), implementing software that is not being used&nbsp / will not render any benefits to the organisation. Research problem: Project Managers (PMs) in YZ organisation&rsquo / s IT department need to perform mandated processes, as&nbsp / defined in their centralised repository. PMs need to use Financial and Planning Software (FPS)2 software to perform certain project management activities, as required by their&nbsp / job function. However, it was found that MPP3 software, another tool, was used for more detailed project schedules, as well as activities that were not strictly enforced by&nbsp / management, the Project Office or the Quality Assurance team. Therefore, from this discovery, it was not clear whether the intended benefit of implementing this mandatory&nbsp / software (FPS) was being realised &ndash / since implementing software that is not being utilised fully would not deliver the intended benefits to the IT department (Devaraj &amp / Kohli&nbsp / 2003), even if the software is termed &lsquo / mandatory&rsquo / . Objective: The primary objective of this research was to explore and optimise the key success factors for an effective&nbsp / implementation of mandatory software in a department, in order to derive the intended business benefits. Literature Review: Literature was reviewed in the search for models or&nbsp / theories that explore the relationship between the use of mandatory software and the achievement of business benefits. The Information Management Body of Knowledge&nbsp / (IMBOK) was selected as this framework defines the relationship between IT and the realisation of business benefits, and ultimately the achievement of any business strategy. The literature review focused predominantly on the level of user involvement, change management, as well as factors that influence the usage of mandatory software by&nbsp / individuals. 1. The name of the organisation utilised has been changed. Refer to Ethical Consideration 2. The name of the tools utilised has been changed. Refer to Ethical&nbsp / Consideration and list of acronyms 3. The name of the tools utilised has been changed. Refer to Ethical Consideration and list of acronyms. Focus was given to organisational factors affecting usage, such as top management support and organisational processes. A model was compiled using unique constructs in the Technology Acceptance Model&nbsp / (and TAM2), the Motivational Model (MM) and the Model of PC Utilisation (MPCU) &ndash / in order to test user acceptance of mandatory software. The literature study concludes with a&nbsp / review of an approach to benefits management including five stages, namely: identifying and structuring benefits, planning for the realisation of benefits, executing the plan, in&nbsp / addition to the evaluation and the review. Research design and methodology: A case study was used in this research, as it examined the phenomenon in its natural setting,&nbsp / &nbsp / &nbsp / employing multiple methods of data collection to gather information from a few entities (groups and data sources). In this way, it was not limited to only qualitative or quantitative&nbsp / approaches, but utilised mixed methods instead. A mixed methods approach was used in order to elaborate, enhance and clarify the results from the qualitative research&nbsp / through the results of the quantitative analysis. Findings: The main finding, based on the compilation of three models of user acceptance, proved that FPS was not being utilised&nbsp / as intended. There was also no evidence of an improvement in business operations. Therefore, benefits management was negatively impacted. Organisational processes were&nbsp / dentified as the most important organisational factor, influencing the usage of FPS software. Own technological capability was considered to be the least important factor,&nbsp / as respondents believed that they had sufficient IT skills in order to learn how to use FPS software. Change management was rated negatively / and as a result, it impacted the&nbsp / usage of FPS, as users were not involved in the decision to implement, and had limited interaction in the implementation process. In addition, there was no evidence found that&nbsp / benefits management was conducted in the IT department / and therefore, the impact of using alternative software could not be quantitatively assessed. Recommendations: In concluding this research, it is recommended that the &ldquo / best practice&rdquo / , derived from the pertinent literate should be followed more diligently if YZ organisation is to benefit from the&nbsp / implementation of mandatory software. For example, in this research, it was found that top management&rsquo / s support of FPS (second most important organisational factor influencing use) was lacking, despite the literature suggestion that senior management involvement in changing technology is crucial for organisational commitment. It is&nbsp / suggested that a more formal approach to benefits management should be implemented. It is also recommended that further study should be conducted &ndash / in order to explore&nbsp / the applicability of the Japanese framing (achieving benefits from IT software through the concept of strategic instinct, rather than strategic alignment) in the context of a&nbsp / developing country (such as South Africa).</p>

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.