Hospitals are looking to industry for proven tools to manage increasingly complex operations and reduce costs simultaneously with improving quality of care. Currently, €˜lean€™ is the preferred system redesign paradigm, which focuses on removing process waste and variation. However, the high level of complexity and uncertainty inherent to healthcare make it incredibly challenging to remove variability and achieve the stable process rates necessary for lean redesign efforts to be effective. This research explores the use of an alternative redesign paradigm €“ €˜agile€™ €“ which was developed in manufacturing to optimize product delivery in volatile demand environments with highly variable customer requirements. €˜Agile€™ redesign focuses on increasing system responsiveness to customers through improved resource coordination and flexibility. System dynamics simulation and empirical case study are used to explore the impact of following an agile redesign approach in healthcare on service access, care quality, and cost; determine the comparative effectiveness of individual agile redesign strategies; and identify opportunities where lean methods can contribute to the creation of responsive, agile enterprises by analyzing hybrid lean-agile approaches. This dissertation contributes to the emerging literature on applying supply chain management concepts in healthcare, and opens a new path for designing healthcare systems that provide the right care, at the right time, to the right patient, at the lowest price.

Lean Production is a well-established concept that has been most prominent within the car manufacturing industry. It bases on the ide to remove all waste and to strip away unnecessary steps that do not add value to the customer. Agile, on the other hand, is a flexible concept, aimed to stay put during volatile circumstances. This thesis deals with the phenomena of Lean Enterprise, which is an elongation of Lean Production. Now the whole organization, on all levels, is included. The thesis also explores the concept of agile, as in agile development and not in a software focus. The purpose of this study is to identify the dispersion between lean and agile philosophies and methods of working within the Swedish textile industry. No previous research about this subject have been made, solely on Lean Production, both in the textile sector and others, or Lean Enterprise, but then not within the chosen sector. Moreover, have no study been made regarding the Swedish textile sector. In order to pursue this study the authors had to explain what characteristics that are describing the phenomena of Lean Production, Pettersens (2009) research was chosen to display these. Then, these groups of characteristics were transmitted into a suitable Lean Enterprise way of thinking, to lift lean up from solely producing environments. By using this information a quantitative survey with 33 assertions have been assembled and executed on three different companies with a total of 16 respondents. The conclusions that can be drawn from this study are that there are indications that lean do exist on an operative level, throughout whole organizations, with the most prominent group of characteristics being scientific management. The least implemented group of lean characteristics within the participated companies is defects control. The results also did indicate that agile characteristics do exist but however in various amounts and in various parts. This thesis is a pilot study which will be used as the fundament for an upcoming study, therefore the latter part of this thesis’s purpose was to conduct, test and give suggestions for improving a survey. / Program: Applied Textile Management

Context: Knowledge is the major aspect of an organization which enables the enterprise to be more productive and to deliver the high complexity services. Knowledge management plays a key role in agile software development because it supports cultural infrastructure esteems like collaboration, communication, and knowledge transfer. This research aims to explore how organizations that adopts Agile Software Development (ASD) implement knowledge management utilizing practices that supports the key process areas. Several knowledge management maturity models have been proposed over a decade ago but not all of the models that is specially stated knowledge Management Maturity Model (KMMM) for Agile software development. To fulfil this research gap, we introduce the maturity model which emphasize knowledge management in ASD among the practitioners. This maturity model helps to assess their knowledge management in organization and provides a road map to the organizations for any further improvement required in their processes.  Objectives: In this thesis, we investigate the key process areas of knowledge management maturity models that could support agile software development. Through investigation about the key process areas, we found that the organizations should emphasis on key process areas and its practices in order to improve the software process. The objectives of this research include: Explore the key process areas and practices of knowledge management in the knowledge management maturity models.  Identify the views of practitioners on knowledge management practices and key process areas for Agile software development. To propose the maturity model for Knowledge management in Agile software development among the practitioner’s opinions.  Methods: In this research, we conducted two methods: Systematic mapping and Survey to fulfil our aim and objectives. We conducted Systematic mapping study through the snowballing process to investigate empirical literature about Knowledge management maturity models. To triangulate the systematic mapping results, we conducted a survey. From the survey results, we obtained the responses and were analyzed statistically using descriptive statistics. Results: From Systematic mapping, we identified 18 articles and analyzed 24 practices of Knowledge management maturity models. These practices are indicated in key process areas such as process, people, technology. Through the systematic mapping results, 9 KM practices that were found from KMMM literature were listed in the survey questionnaire and answered by software engineering practitioners. Moreover, 5 other new practices for agile have suggested in the survey that was not found in KMMM literature. To address the systematic mapping and survey results, we propose the maturity model which emphasize knowledge management practices in ASD among the practitioners. Conclusions: This thesis lists the main elements of practices that are utilized by the organization and also show the usage of maturity levels at each practice in detail. Furthermore, this thesis helps the organization's to assess the current levels of maturity that exist to each practice in a real process. Hence, the researchers can utilize the model from this thesis and further they can improve their Km in organizations.

This thesis presents the findings of a research project to develop and implement a Lean and agile Construction System on a case study project. The aim of the research project, for the sponsor company, was to improve its projects site operations, making them safer for the worker and improving effectiveness and productivity. The findings have shown that the Construction System has proved to be a successful set of countermeasures that act as an antidote to the health, safety and productivity problems that exist in UK construction and that face the sponsor company. The System has been implemented on a large and complex mechanical and electrical case study project in the healthcare sector of UK construction. The outcome of this case study project shows that 37% less onsite labour was needed, meaning fewer workers were exposed to health and safety risks from site operations, leading to zero reportable accidents. Good ergonomics was achieved by focussing on workplace design, thus improving workers wellbeing, together with an improved quality of work for those required on site carrying out simpler assembly tasks. Productivity gains resulted by eliminating process waste, therefore reducing the risk of labour cost escalation that could otherwise have occurred. A 7% direct labour cost reduction was made meaning the labour budget allocation was maintained. Significantly, an overall productivity of 116% was achieved using the Construction System, which compares favourably to BSRIA's findings of an average overall productivity of only 37% when compared to observed best practice for the projects in that case study research. The results include the benefits found from the use of an innovative method to assemble, transport, and install frameless, preassembled mechanical and electrical services modules, where a 93% reduction in onsite labour was achieved together with an 8.62% cost benefit. No time slippage was experienced during onsite assembly to delay or disrupt other trades and the commissioning programme was not compressed that could otherwise have caused problems in handing over the facility to the customer. From a customer's perspective, the built facilities were handed over on-time, to their satisfaction and to budget. The research has achieved two levels of innovation, one at a process level and one at a product level. The process innovation is the development and successful implementation of the Construction System, which is a combination of methods acting together as an antidote to the research problem. The product innovation is the development of the innovative method for assembling, transporting and installing frameless mechanical and electrical corridor modules, whereby modularisation can be achieved with or without an offsite manufacturing capability. The System is built on Lean principles and has been shown to standardise the work, process and products to create flow, pull and value delivery. It is transferable across the sponsor company's business as well as the wider industry itself. The transformation that has occurred is the creation of a step-change in undertaking mechanical and electrical construction work, which has realised a significant improvement in performance for CHt that has "Transformed Traditional Mechanical and Electrical Construction into a Modern Process of Assembly".

Pair programming is a software development method which describes two programmers working together on the same computer, sharing one keyboard. This approach requires programmers to communicate frequently, which can lead the pair to experience certain benefits over solo programming, such as faster problem solving and a greater enjoyment of their work (Cockburn and Williams, 2001, Bryant et al., 2006). Many programmers approach their first pairing experience with scepticism, having doubts about their partner’s working habits and programming style, and about the additional communication aspects that this programming style entails (Williams et al., 2000). Despite a significant amount of research into pair programming of over 15 years, it is not evident what communication between the pair contributes to the task of pair programming. This work presents an analytic coding scheme which was derived from the observation of the communication of expert pairs working in industry. Over 35 hours of communication across 11 different pairs was analysed. This coding scheme was further refined to produce industry-inspired pair programming guidelines that assist novice pair programmers to improve their experience of pair communication. Findings indicate that introducing these guidelines to novice student pairs can have a positive impact on their perception of intra-pair communication, and on their perception of their partner’s contribution. Feedback received from expert pairs was used to add detail to the guidelines, which have been made publically available through an online resource.

Agile development is a software development methodology that originated in 2001 (Beck, et al.). It has since gained wide recognition and use in the software industry, and is characterized by iterative development cycles. Organizations outside of the software industry are also finding ways to adapt Agile development to their contexts. BYU Independent Study (BYUIS) is an online education program at Brigham Young University that provides online courses at the high school and university levels. In April 2016, BYUIS implemented the Agile development process to the design and development of online courses. This thesis is a case study that looks specifically at the adoption of Agile at BYUIS, from its implementation in April 2016 to the time of this study in summer of 2017. The question this qualitative study seeks to answer is as follows: how and why did the adoption of the Agile development methodology to instructional design practices at BYUIS reflect or differ from the 12 principles of Agile development? To answer this research question, the researcher used multiple data sources: semi-structured interviews with three administrators, two production team managers, and three instructional designers; surveys for BYUIS student employees (i.e., scrum team members) after each week of observation; and field note observations of three Agile scrum teams for two weeks each. The data from each of these sources was analyzed through a descriptive coding process and then organized into a thematic network analysis. The Results section analyzes evidence from the interviews, surveys, and observations that reflect or differ from each of the 12 principles of Agile. The Discussion addresses three main issues of implementing Agile at BYUIS: how to accommodate for part-time schedules, the complexity of working on different projects, and how to facilitate communication in scrum teams if co-location is not possible. It also looks at how these three issues could be manifest in other organizations and introduces potential solutions. The researcher then presents suggestions for future research on Agile in instructional design or other contexts.

The purpose of this dissertation was to explore critical issues and challenges that might arise in agile software development processes with Scrum. It also sought to provide management guidelines to help organizations avoid and overcome barriers in adopting the Scrum method as a future software development method. A qualitative research method design was used to capture the knowledge of practitioners and scrutinize the Scrum software development process in its natural settings. An in-depth case study was conducted in two organizations where the Scrum method was fully integrated in every aspect of two organizations' software development processes. One organization provides large-scale and mission-critical applications and the other provides small- and medium-scale applications. Differences between two organizations provided useful contrasts for the data analysis. Data were collected through an email survey, observations, documents, and semi-structured face-to-face interviews. The email survey was used to refine interview questions; all of the interviews were audio-taped and transcribed, and later coded for analysis. Triangulation in the data collection process provided useful information for different perspectives on the issues, allowed for cross-checking, and yielded stronger substantiation of concepts and common categories. The research presented four common categories of issues and challenges of the Scrum method, and management guidelines to help organizations that are already using the Scrum method or planning to employ it in the future. The framework for a hybrid software development model is then proposed as a future study.

Software engineering techniques have been employed for many years to guide software product creation. In the last decade the appropriateness of many techniques has been questioned, given unacceptably high rates of software project failure. In light of this, there have emerged a new set of agile software development methodologies aimed at reducing software projects risks, on the basis that this will improve the likelihood of achieving software project success. Recent studies show that agile methods have been gaining increasing industry attention. However, while the practices recommended by agile methodologies are said to reduce risks, there exists little evidence to verify this position. In addition, it is posited that the very processes recommended by agile methodologies may themselves introduce other risks. Consequently, this study addresses the risks inherent in the human collaboration practices that are central to agile methods. An analysis of the risk management literature reveals that personality conflicts and customer-developer disagreements are social risks that occur through human collaboration. These risks negatively affect team cohesion and software project success. Personality conflicts are said to be mostly influenced through poor team formation, whereas customer-developer disagreements are induced through excessive customer direct interaction. However, these risks are not adequately addressed by standard risk management theories. Furthermore, an evaluation reveals that these risks are also not considered by existing software tools.This study therefore designs and implements a web-based solution to lessen the social risks that may arise in agile projects. The Agile Social-Risk Mitigation Tool (ASRMT) offers support for personnel capability assessment and management and for remote customer feature management, extending the customer's access through an interface. Using software engineering experts to evaluate ASRMT, the tool is shown to effectively address social risk management theories, and is considered likely to assist agile developers in their handling of social risks. In addition, above and beyond its intended purpose, ASRMT is also likely to assist agile teams with general project management. The findings of the ASRMT user evaluations demonstrate sufficient proof of concept to suggest that such a tool could have value in live software projects.

The objective of this thesis is to obtain knowledge regarding how effective user centred evaluation methods are and how user centred evaluations are conducted by IT professionals. This will be achieved by exploring user centred evaluation in experimental and practical settings. The knowledge gained in these studies should inspire suggestions for further research and suggestions for improvements on the user centred evaluation activity. Two experimental studies were conducted. One compares the results from using three user centred evaluation methods, and the other examines two factors while conducting heuristic evaluation. The results show that the think-aloud evaluation method was the most effective method in finding realistic usability problems of the three methods. The number of critical problems found during think-aloud evaluation increases, if heuristic evaluation is conducted prior to the think-aloud evaluations. Further, two studies of user centred evaluation in practical settings were performed. The IT professionals participating in those studies were using the software development process Scrum to plan their work. The results show that user centred evaluation is infrequently conducted in Scrum projects, compared to testing activities like acceptance testing. The main type of evaluation is qualitative. Few participants measure user performance or use surveys to gather quantitative results on the usability and the user experience. IT professionals get feedback from users in an informal way and gather informal feedback from peers. Many participants use a mixture of methods for gathering feedback on their work. The outcome of this thesis shows that IT professionals should be encouraged to include users whenever possible when evaluating software, for example by using the think-aloud method. Using heuristic evaluation prior to conducting think-aloud evaluations is also recommended. In addition, IT professionals are encouraged to evaluate their software in an informal way frequently, rather than waiting for the right time to conduct a thorough quantitative evaluation. To advance this field further, researchers who want to improve the evaluation activity for the IT professionals should study how user centred evaluation methods could be combined in an efficient way and how the use of qualitative evaluation methods could be made more effective. / QC 20120522

In this thesis, we have identified the difference between Agile and Lean methodsbased on stakeholder’s perspectives. To achieve the goal we have dealwith only Agile and Lean principles. In addition, in order to identify thestakeholders from Agile and Lean principles we have used the relevant practicesfrom both sides. As the principles of Agile manifesto are directly followedby most of the organizations, we have also used Agile principles directlyin this research. On the other hand lean methods have no pure principles,as a result we have used the most common and popular lean principlesderived from different authors. We have only considered the mostrelevant principles that might be useful in software development. To achievea stronger result of this thesis we have also considered stakeholder theory.Moreover we have identified the stakeholder’s involvement with Agile/Leanprinciples and stakeholder theory.