Human Factors in Agile Software Development

Through our four years experiments on students' Scrum based agile software development (ASD) process, we have gained deep understanding into the human factors of agile methodology. We designed an agile project management tool - the HASE collaboration development platform to support more than 400 students self-organized into 80 teams to practice ASD. In this thesis, Based on our experiments, simulations and analysis, we contributed a series of solutions and insights in this researches, including 1) a Goal Net based method to enhance goal and requirement management for ASD process, 2) a novel Simple Multi-Agent Real-Time (SMART) approach to enhance intelligent task allocation for ASD process, 3) a Fuzzy Cognitive Maps (FCMs) based method to enhance emotion and morale management for ASD process, 4) the first large scale in-depth empirical insights on human factors in ASD process which have not yet been well studied by existing research, and 5) the first to identify ASD process as a human-computation system that exploit human efforts to perform tasks that computers are not good at solving. On the other hand, computers can assist human decision making in the ASD process.Comment: Book Draf

Towards a taxonomy of reusable CRM requirements for the Not for Profit sector

This thesis was submitted for the degree of Doctor of Philosophy and awarded by Brunel University.Traditional (or commercial) CRM is a well-defined domain but there is currently no generally accepted definition of what constitutes CRM in the not for profit (NfP) sector. Not for profit organisations are organisations which exist for a social purpose, are independent of the State, and which re-invest all of their financial surpluses in the services they offer or in the organisation itself. This research aims to answer the question “What exactly is CRM as applied to the NfP sector, what are its boundaries and what functions should an NfP CRM information system perform?” Grounded Theory Method (GTM) within a Design Science framework was used to collect, analyse, categorise, generalise and structure data from a number of NfP organisations and NfP information systems suppliers. An NfP CRM model was constructed from this data in the form of three multi-level taxonomies. The main taxonomy relates to generic and reusable information system requirements both functional and non-functional. Within this taxonomy the high-level categorisations of commercial CRM, namely “Marketing, “Sales” and “Service”, are greatly extended to reflect the special needs of the NfP sector and in particular a much broader definition of “customer”. The two minor taxonomies relate to issues of CRM strategy and CRM systems architecture which need to be considered alongside the system requirements. In addition to and resulting from the taxonomies, an over-arching definition of NfP CRM was developed. NfP organisations now have a framework that will enable them to know what to expect of CRM systems and from which they can select requirements to build their own specification of information system needs. Using the requirements taxonomy for this task will make the process of requirements analysis and specification easier, quicker, cheaper and more complete than using traditional methods. The framework will also allow NfP system suppliers to know what NfP organisations expect of their systems and will assist them with the specification of new system features. The minor taxonomies will provide NfP organisations with a series of strategic issues and systems architecture options that should be considered when implementing a CRM system. This research also demonstrates how GTM can be utilised: as the development phase of Design Research, as a general method of domain analysis, and as a tool to develop a taxonomy of reusable information system requirements

Towards a taxonomy of reusable CRM requirements for the Not for Profit sector

Traditional (or commercial) CRM is a well-defined domain but there is currently no generally accepted definition of what constitutes CRM in the not for profit (NfP) sector. Not for profit organisations are organisations which exist for a social purpose, are independent of the State, and which re-invest all of their financial surpluses in the services they offer or in the organisation itself. This research aims to answer the question "What exactly is CRM as applied to the NfP sector, what are its boundaries and what functions should an NfP CRM information system perform?" Grounded Theory Method (GTM) within a Design Science framework was used to collect, analyse, categorise, generalise and structure data from a number of NfP organisations and NfP information systems suppliers. An NfP CRM model was constructed from this data in the form of three multi-level taxonomies. The main taxonomy relates to generic and reusable information system requirements both functional and non-functional. Within this taxonomy the high-level categorisations of commercial CRM, namely "Marketing, "Sales" and "Service", are greatly extended to reflect the special needs of the NfP sector and in particular a much broader definition of "customer". The two minor taxonomies relate to issues of CRM strategy and CRM systems architecture which need to be considered alongside the system requirements. In addition to and resulting from the taxonomies, an over-arching definition of NfP CRM was developed. NfP organisations now have a framework that will enable them to know what to expect of CRM systems and from which they can select requirements to build their own specification of information system needs. Using the requirements taxonomy for this task will make the process of requirements analysis and specification easier, quicker, cheaper and more complete than using traditional methods. The framework will also allow NfP system suppliers to know what NfP organisations expect of their systems and will assist them with the specification of new system features. The minor taxonomies will provide NfP organisations with a series of strategic issues and systems architecture options that should be considered when implementing a CRM system. This research also demonstrates how GTM can be utilised: as the development phase of Design Research, as a general method of domain analysis, and as a tool to develop a taxonomy of reusable information system requirements.EThOS - Electronic Theses Online ServiceGBUnited Kingdo

DATA QUALITY BY DESIGN: A GOAL-ORIENTED APPROACH (Research-in-Progress) IQ in Databases, the Web, and e-Business

Abstract: We present a design process for incorporating data quality requirements into database schemas that is rooted in goal-oriented requirements analysis techniques, developed in the Requirement Engineering community over last 15 years. Goal-oriented approaches (i) offer a body of notations, techniques and processes for modeling, analyzing and operationalizing quality requirements; (ii) support representation and evaluation of alternatives in goal fulfillment; and (iii) provide automated reasoning tools for various analysis and design tasks. This paper extends existing proposals for addressing data/information quality issues during database requirements analysis and design in two ways. First, we consider a broader range of quality assurance data requirements, which can be classified as restrictive, descriptive, supportive and reflective. Second, we offer a systematic way to operationalize high-level, abstract quality goals into operational, concrete quality assurance data requirements plus standard operating procedures, based on a risk-based analysis. In an earlier paper, we presented a goal-oriented conceptual database design approach, focusing on deriving an ordinary conceptual schema from application-specific goals. In this paper, we take the next step to incorporate quality goals into the design process. The proposed quality design process is illustrated step-by-step using a meeting expense database example. We also show how this process fits into the overall goal-oriented conceptual database design approach to offer an integrated framework for analyzing both application-specific and quality assurance data requirements