Submitted in fulfilment of the requirements for the degree of Doctor of Technology: Information Technology, Durban University of Technology, Durban, 2015. / Agile approaches have proliferated within the software development arena over the past decade. Derived mainly from Lean manufacturing principles, agile planning and control mechanisms appear minimal and fluid when compared to more traditional software engineering approaches. Scrum ranks among the more popular permutations of agile. Contemporary literature represents a rich source of contributions for agile in areas such as practice guidelines, experience reports, and methodology tailoring; but the vast majority of these publications focus on the individual project level only, leaving much uncertainty and persistent questions in the multi-project space. Questions have recently been raised, by both academics and practitioners alike, concerning the ability of Scrum to scale from the individual project level to the multi-project space. Program management is an area encompassing practice and research areas concerned mainly with harmonizing the existence of competing simultaneous projects. Existing literature on program management essentially perceives projects as endeavours that can be carefully planned at the outset, and controlled in accordance with strong emphasis placed on economic and schedule considerations. This complexion seems to be mostly a result of well-established and ingrained management frameworks like Project Management Institute (PMI), and is largely at odds with emerging practices like Scrum. This disparity represents a gap in the literature and supports the need for deeper exploration. The conduit for this exploration was found in two South African software development small to medium sized enterprises (SMMEs) practicing Scrum. The practical realities and constraints faced by these SMMEs elicited the need for more dynamic program management practices in support of their quest to maximize usage of limited resources. This thesis examines these practices with the aim of providing new insights into the program management discourse in the context of Scrum software development environments. The research approach is qualitative and interpretive in nature. The in-depth exploratory case study research employed the two software SMMEs as units of analysis. Traditional ethnographic techniques were commissioned alongside minimal researcher participation in project activities. Activity Theory honed the data analysis effort and helped to unearth the interrelationships between SMME characteristics, program management practices, and Scrum software development. The results of the data analysis are further refined and fashioned into eleven knowledge areas that represent containers of program management practices. This is the product of thematic analysis of literature and data generated from fieldwork. Seeing as the observed practices were highly dynamic in nature, concept analysis provided a mechanism by which to depict them as snapshots in time. As a theoretical contribution, proposed frameworks were crafted to show how program management practices might be understood in the context of organizations striving towards agile implementation. Furthermore, representations of the mutually influential interfaces of SMME characteristics and Scrum techniques that initiate the observed fluid nature of program management practices, are brought to the fore.

A substantial amount of IT projects fail or stay challenged in meeting their targets based on project schedule, budget and system requirements.  Leading global surveys in the last decade barely indicate any improvement in the statistical performance of IT projects in spite of the fact that a lot of effort has been taken in the past to identify and fix those critical factors on which the success and failure of IT projects are generally based on. The poor trend and the underperformance of IT projects still continue. Different researches based on different approaches identify different critical factors but to a very large extent people and processes are blamed. This thesis is under taken to understand the impact of Information Systems (IS) processes and methodologies in the success and failure of IT projects. Major challenges within IS processes, such as their initial identification, implementation and organizational process awareness are identified through qualitative research methods. ‘Identification and selection of IS process and methodologies’ is identified as a major challenge within IT projects and is discussed in detail as, why and what difficulties organizations face in the process of  selecting processes and methodologies on a given IT project. A couple of methodology selection frameworks to overcome these difficulties are presented along side with their critical review and improvement. We come to a conclusion that there is a growing need for more efficient and competent methodology selection frameworks as the ones which exist today are barely complete and efficient and if they do then only to a limited and partial degree.

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)