Measuring and tracking quality factors in Free and Open Source Software projects

Free and Open Source Software (FOSS) has gained increased interest in the computer software industry, but assessing its quality remains a challenge. FOSS development is frequently carried out by globally distributed development teams, and all stages of development are publicly visible. Several product and process-level quality factors can be measured using the public data. This thesis presents a theoretical background for software quality and metrics and their application in a FOSS environment. Information available from FOSS projects in three information spaces are presented, and a quality model suitable for use in a FOSS context is constructed. The model includes both process and product quality metrics, and takes into account the tools and working methods commonly used in FOSS projects. A subset of the constructed quality model is applied to three FOSS projects, highlighting both theoretical and practical concerns in implementing automatic metric collection and analysis. The experiment shows that useful quality information can be extracted from the vast amount of data available. In particular, projects vary in their growth rate, complexity, modularity and team structure.

Collecting data from distributed FOSS projects

A key trait of Free and Open Source Software (FOSS) development is its distributed nature. Nevertheless, two project-level operations, the fork and the merge of program code, are among the least well understood events in the lifespan of a FOSS project. Some projects have explicitly adopted these operations as the primary means of concurrent development. In this study, we examine the effect of highly distributed software development, is found in the Linux kernel project, on collection and modelling of software development data. We find that distributed development calls for sophisticated temporal modelling techniques where several versions of the source code tree can exist at once. Attention must be turned towards the methods of quality assurance and peer review that projects employ to manage these parallel source trees. Our analysis indicates that two new metrics, fork rate and merge rate, could be useful for determining the role of distributed version control systems in FOSS projects. The study presents a preliminary data set consisting of version control and mailing list data.

Collecting data from distributed FOSS projects

A key trait of Free and Open Source Software (FOSS) development is its distributed nature. Nevertheless, two project-level operations, the fork and the merge of program code, are among the least well understood events in the lifespan of a FOSS project. Some projects have explicitly adopted these operations as the primary means of concurrent development. In this study, we examine the effect of highly distributed software development, is found in the Linux kernel project, on collection and modelling of software development data. We find that distributed development calls for sophisticated temporal modelling techniques where several versions of the source code tree can exist at once. Attention must be turned towards the methods of quality assurance and peer review that projects employ to manage these parallel source trees. Our analysis indicates that two new metrics, fork rate and merge rate, could be useful for determining the role of distributed version control systems in FOSS projects. The study presents a preliminary data set consisting of version control and mailing list data.

Developing a Multidisciplinary Process View of IFC Standardization

The industry foundation classes (IFC) file format is one of the most complex and ambitious IT standardization projects currently being undertaken in any industry, focusing on the development of an open and neutral standard for exchanging building model data. Scientific literature related to the IFC standard has dominantly been technical so far; research looking at the IFC standard from an industry standardization per- spective could offer valuable new knowledge for both theory and practice. This paper proposes the use of IT standardization and IT adoption theories, supported by studies done within construction IT, to lay a theoretical foundation for further empirical analysis of the standardization process of the IFC file format.

Use of Document Management Systems - a Case Study of the Finnish Construction Industry

Triggered by the very quick proliferation of Internet connectivity, electronic document management (EDM) systems are now rapidly being adopted for managing the documentation that is produced and exchanged in construction projects. Nevertheless there are still substantial barriers to the efficient use of such systems, mainly of a psychological nature and related to insufficient training. This paper presents the results of empirical studies carried out during 2002 concerning the current usage of EDM systems in the Finnish construction industry. The studies employed three different methods in order to provide a multifaceted view of the problem area, both on the industry and individual project level. In order to provide an accurate measurement of overall usage volume in the industry as a whole telephone interviews with key personnel from 100 randomly chosen construction projects were conducted. The interviews showed that while around 1/3 of big projects already have adopted the use of EDM, very few small projects have adopted this technology. The barriers to introduction were investigated through interviews with representatives for half a dozen of providers of systems and ASP-services. These interviews shed a lot of light on the dynamics of the market for this type of services and illustrated the diversity of business strategies adopted by vendors. In the final study log files from a project which had used an EDM system were analysed in order to determine usage patterns. The results illustrated that use is yet incomplete in coverage and that only a part of the individuals involved in the project used the system efficiently, either as information producers or consumers. The study also provided feedback on the usefulness of the log files.

Essays on Managing Knowledge and Work Related Wellbeing

This study explores the relationship between Intellectual Capital and Maintenance of Work Ability. Intellectual Capital is the central framework for analysing the increasing knowledge-intensiveness of business life. It is characteristic of Intellectual Capital that the intersection of human capital, internal structures and external structures is essential. Maintenance of Work Ability, on the other hand, has been the leading paradigm for Finnish occupational health and safety activities since the late 1980s. It is also a holistic approach that emphasises the interdependence of competence, work community, work environment and health as the key to work-related wellbeing. This thesis consists of five essays that scrutinise the focal phenomena both theoretically and empirically. The conceptual model that results from the first research essay provides a general framework for the whole thesis. The case study in the second essay supports a division of intangible assets into generative and commercially exploitable intangibles introduced in the first essay and further into the primary and secondary dimension of generative intangibles. Further scrutiny of the interaction of generative intangible assets in essay three reveals that employees’ wellbeing enhances the readiness to contribute to the knowledge creation process. The fourth essay shows that the MWA framework could benefit knowledge-intensive work but this would require a different approach than has been commonly adopted in Finland. In essay five, deeper analysis of the MWA framework shows that its potential results from comprehensive support of the functioning of an organisation. The general conclusion of this thesis is that organisations must take care of their employees’ wellbeing in order to secure innovativeness that is the key to surviving in today’s competitive business environment.

Managing in the “Golden Cage” An Ethnographic Study of Work, Management and Gender in Parliamentary Administration

Parliaments are political institutions, but they are also places where people work; the MPs and the people who are employed there work, albeit in rather different ways. In this research the focus is on those in a Parliament who work there as employees and managers, and thereby, in some senses, run the organisation. Accordingly, this involves seeing the Parliament as a working environment, for MPs and employees, for men and women. The institution of Parliament is thus here examined by looking at it from a different and new angle. Instead of the usual focus on politicians the focus is on the administration of this institution. The aim is, amongst other things, to increase knowledge and offer different perspectives on democracy and democratic institutions. Unpacking the nearly mythical institution into smaller, more digestible, graspable realities should at the very least help to remind the wider society that although nations, to a certain extent, do need national institutions they should not become mystified or seen as larger than life. Institutions should work on behalf of people and thus be accountable to these same people. The main contribution of this work is to explore and problematise how managing and working is done inside an institution that both largely fulfils the characteristics of a bureaucracy and yet also has added special features that seem to be rather far removed from clear bureaucratic structures. This research offers a new kind of information on working life inside this elite institution. The joys and the struggles of working and managing in this particular public sector organisation are illustrated here and offer a view, a glimpse, into the experiences of managing and working in this House.

Managing Project Business Development: an Inter-Organizational and Intra-Organizational Perspective (summary section only)

The driving force behind this study is the gap between the reality of the firms engaged in project business and the available studies covering project management and business process development. Previous studies show that project-based organizations were ‘immature’ in terms of the project-management ‘maturity model’, as few firms were found to be optimizing processes. Even within those, very little attention was paid to combine inter-organizational and intra-organizational perspectives. In this study an effort is made to elaborate some thoughts and views on project management, which interrelate firms’ external and internal activities. In line with the integration, the dissertation uses an approach to the management of project-business interdependencies in the networks of actors, activities and resources. Firstly, the study develops an understanding for inter-organizational perspectives by exploring the complementarities of process activities in the basic development of project business. It presents a framework that is elaborated on the basis of the reciprocal interactions of activities within and outside the organization—thus providing a coherent basis for continuous business-process improvement. In addition, the study presents new tools that can be used to develop project-business processes in each of its functional areas. The research demonstrates how project-business activities can be optimized using the right resources at the right time with the right actors and the right actions. The selected five articles included in this dissertation explain the basic framework for the development of project business. Each paper covers various aspects of inter-organizational and intra-organizational perspectives for project management. The study develops a valuable and procedural model for business-process improvement using the Delphi method that can be used not only in academia but also as a guide for practitioners that takes them through a series of well-defined steps when making informed, consistent and efficient changes to their business processes.

Lean Thinking in Software Development : Impacts of Kanban on Projects

The history of software development in a somewhat systematical way has been performed for half a century. Despite this time period, serious failures in software development projects still occur. The pertinent mission of software project management is to continuously achieve more and more successful projects. The application of agile software methods and more recently the integration of Lean practices contribute to this trend of continuous improvement in the software industry. One such area warranting proper empirical evidence is the operational efficiency of projects. In the field of software development, Kanban as a process management method has gained momentum recently, mostly due to its linkages to Lean thinking. However, only a few empirical studies investigate the impacts of Kanban on projects in that particular area. The aim of this doctoral thesis is to improve the understanding of how Kanban impacts on software projects. The research is carried out in the area of Lean thinking, which contains a variety of concepts including Kanban. This article-type thesis conducts a set of case studies expanded with the research strategy of quasi-controlled experiment. The data-gathering techniques of interviews, questionnaires, and different types of observations are used to study the case projects, and thereby to understand the impacts of Kanban on software development projects. The research papers of the thesis are refereed, international journal and conference publications. The results highlight new findings regarding the application of Kanban in the software context. The key findings of the thesis suggest that Kanban is applicable to software development. Despite its several benefits reported in this thesis, the empirical evidence implies that Kanban is not all-encompassing but requires additional practices to keep development projects performing appropriately. Implications for research are given, as well. In addition to these findings, the thesis contributes in the area of plan-driven software development by suggesting implications both for research and practitioners. As a conclusion, Kanban can benefit software development projects but additional practices would increase its potential for the projects.