Context. Scrum is one of the most common used Agile method. It is based on empiricism. Scrum only provides a framework but the detailed implementations in practice are very different. and the environment has a big influence on it. National culture is proven to have an impact on Agile methodology. The implementation of Scrum practices should be influenced by national culture as well. Objectives. This paper reveals the relationship between national culture and Scrum implementation. It explores in which aspects that national culture has an influence on the implementation of Scrum practices and how the different national culture dimensions affect the implementations. Methods. A literature review is used to build a theoretical framework. This framework includes the potential relationships between national culture and Scrum practices, which are our hypotheses. Afterward, interview is used in a company that has Scrum teams in both Sweden and China. Their implementations of Scrum practices are interviewed and analyzed based on our hypotheses. Results. A framework of deducted relationship between Hofstede’s national culture dimensions and Scrum practices is built. National culture is found to have an influence on the implementations of five Scrum practices. Conclusions. National culture is found to have an influence on Scrum implementations. National culture through power distance dimension has the most impact on implementations of no title practice, manage burn down chart practice and no interference practice. National culture differences in the aspect of individualism dimension also affect the practice like no title in teams. Uncertainty avoidance degree in different nations also has the most impact on Scrum implementation such as using burn down chart practice and time-boxed dimensions. Moreover, influence from national culture in China makes the Scrum implementations more consistency than the influence from national culture in Sweden.

Through a case study, I wanted to find out what advantages and disadvantages local companies consider with scrum and what they think about its future. To find out what scrum is, I read the literature and scientific articles and then wrote surveys based on my thoughts. Further, I also wanted to find out if it’s possible to use scrum in a school environment and therefore I visited a high school class who used scrum in one of their projects. The result was good but could have been better as it requires more training of scrum to understand everything. The surveys were distributed to various local companies. After having received a lot of answers, I concluded that the clear priority was the most positive feature of scrum and the most negative was that it was difficult to get the rest of the organization to understand scrum, which creates problems. Both high school class and local companies believe in scrum’s future, even if they think scrum will be partially modified to adapt to the software-development in the future. According to the survey responses, the most important to get the projects to be successful both now and in the future is that everyone who work with scrum is right educated. / Genom en fallstudie ville jag ta reda på vilka fördelar respektive nackdelar de lokala företagen ser med scrum och vad de anser om dess framtid. För att ta reda på vad scrum är har jag läst litteraturstudier och vetenskapliga artiklar för att sedan kunna skriva enkäter som bygger på mina funderingar. Fortsättningsvis ville jag även ta reda på om man kan använda scrum i skolmiljön och har därför besökt en gymnasieklass som använt sig utav scrum i deras projekt. Resultatet blev bra, men hade kunnat bli bättre då det krävs mer utbildning av scrum för att förstå allt. Enkäterna lämnades ut till olika lokala företag. Efter att ha fått in en hel del svar kom jag fram till att klara prioriteringar var den mest positiva egenskapen med scrum och den mest negativa var att det var svårt att få den övriga organisationen att förstå scrum, vilket skapar problem. Både gymnasieklassen och de lokala företagen tror på scrums framtid, även om de tror att scrum kommer att vara till viss del modifierad för att anpassa sig till hur mjukvaru-utvecklningen sker framöver. Enligt enkätsvaren så är det viktigaste för att få projekten att bli framgångsrika både nu och i framtiden att alla som arbetar med scrum som arbetsmetod är rätt utbildade.

Software products can be categorized into three types namely bespoke, market driven and customizable generic products. Each of these products is facing different problems in their development and to address these problems different software process models have been introduced. The use and validation of different software process models for bespoke and market driven products have been discussed in earlier work. On the other hand, less attention was paid to the customizable generic products. Our thesis will fill this gap by conducting a case study on evolutionary prototyping (EP) for customizable generic products. The main aim of the thesis is to make an initial validation of EP for customizable generic products. In order to fulfill the aforementioned aim we performed a literature study on prototyping and EP, together with development of two customizable generic products. During this development process, we used approach of EP. The results from our investigation will provide researchers and practitioners with a deep insight to the EP and also to guide them in making decision regarding the use of EP. The main findings from our investigation are as follows: • EP is not used standalone as a software process model. Rather it is used as a concept that can be augmented with some iterative software process model. • Negative and positive aspects of EP were highlighted by discussing situations where it could be a better choice, with its advantages and disadvantages. • An initial validation was performed on EP for customizable generic products. Reported results from this case study show that the selected approach is a good choice when you want to have innovative product, clear ambiguous and sketchy requirements, discover new requirements, save resources of software testing, involve and satisfy customer. EP shows vulnerabilities in documentation of product and quality of code. / Mobile number : 0046762183249

Security is today considered as a basic foundation in software development and therefore, the modelling and implementation of security requirements is an essential part of the production of secure software systems. Information technology organisations are moving towards agile development methods in order to satisfy customers' changing requirements in light of accelerated evolution and time restrictions with their competitors in software production. Security engineering is considered difficult in these incremental and iterative methods due to the frequency of change, integration and refactoring. The objective of this work is to identify and implement practices to extend and improve agile methods to better address challenges presented by security requirements consideration and management. A major practices is security requirements capture mechanisms such as UMLsec for agile development processes. This thesis proposes an extension to the popular Scrum framework by adopting UMLsec security requirements modelling techniques with the introduction of a Security Owner role in the Scrum framework to facilitate such modelling and security requirements considerations generally. The methodology involved experimentation of the inclusion of UMLsec and the Security Owner role to determine their impact on security considerations in the software development process. The results showed that overall security requirements consideration improved and that there was a need for an additional role that has the skills and knowledge to facilitate and realise the benefits of the addition of UMLsec.

Rapporten beskriver framtagandet av en webbshop för glasögonförsäljning. Läsaren får ta del av lärdomar om hur det fungerar att arbeta efter den agila projektmodellen Scrum i praktiken och förslag till hur metodiken kan anpassas för effektiv användning i ett utvecklingsteam. Vidare diskuteras även hur sammanslagning av flera projektmodeller kan ske för att skapa en mer produktiv projektmiljö.  Lösningar till tekniska problem som uppstått under projektets gång presenteras och diskuteras utifrån ett utvecklarprespektiv. Vidare presenteras en marknadsundersökning där kundsegmentet identifieras och analyseras för utformning av slutprodukten. Utmärkande för slutprodukten är en smidig och enkel köpprocess uppdelad i tre enkla steg.

The increasing technological advancement and globalization has seen a rise in offshoring of IT-development, also known as Global Software Development (GSD). One of the most common countries for offshoring has been India with its increasingly competent population.The use of GSD to leverage highly skilled and low-cost labor also creates challenges in three main categories; Coordination, Control and Communication. These challenges arise due to socio-cul-tural, geographical and temporal distances.The use of the Scrum development framework is claimed by scholars to mitigate these issues. This study is grounded on Hossain, Bannerman & Jeffery’s (2011) research framework, which summa-rizes the current body of literature on Scrum’s mitigating effect on commonly occurring challenges in a GSD environment. Due to the scarcity of empirical data on the research framework, the authors of this thesis conducted an ethnographical study on location in India at Indpro, a company founded in Sweden and studied two projects. The purpose of this study is to both evaluate and provide suggestions for expansion of the Hossain et al. (2011) framework with ethnographically collected empirical support, which prior to this was primarily based on experience reports. This study also aims to identify GSD challenges and mitigation strategies that occur in the setting of an experi-enced organization conversant with Scrum methodology in a GSD context.The purpose of this study is to contribute to an increased empirical understanding of how Scrum is being used in a GSD environment, what challenges are prevalent in a distributed GSD environ-ment and how those challenges might be addressed or mitigated. In this study, parts of Hossain et al. (2011) framework are evaluated and suggestions for expanding it through mitigation strategies such as Planning, high quality ICT-Mediate Synchronous and asynchronous communication are specified. Implications for practitioners include the proposal to follow Scrum Practices more me-ticulously to receive all of Scrums inherent mitigating effects.

The thesis focuses on concrete application of the selected agile methodologies on the designed new software development methodology in the company Firma 2.0. The theoretical section briefly characterizes agile methodologies in general and then focuses on their representative sample, and thus Scrum, Kanban, SAFe and LeSS and the DevOps movement, which build a framework for the practical section. The selected components, which are used in the second part, are emphasized. Importantly, all of the methodologies are based on the agile manifesto and thanks to that are mutually combinable. The practical section introduces the company Firmy 2.0 together with its existing software development methodology, which is currently insufficient. The shortages are described as bottlenecks of the methodology itself as well as issues of process management of the company. The newly designed software methodology eliminates those drawbacks and integrates new elements and terminology in order to better correspond with the current processes in the company. The main contribution of the thesis is seen in the new design of software development methodology for a small company, which can also be potentially used outside of the company Firma 2.0, associated with a sound theoretical background.

El presente Proyecto Profesional realiza el análisis de la Arquitectura Empresarial, para la Organización “Colegio Trener de Monterrico”, haciendo especial énfasis en el proceso de Negocio “Seguimiento Académico”, este análisis se desarrolla con las herramientas más destacadas del mercado; como el esquema de Marco TOGAF, Metodología de trabajo SCRUM y la gestión de Servicios ITIL v3. La necesidad de analizar este proceso, es determinada por la Dirección del Colegio, la cual busca administrar mejor los flujos de trabajo y gestionar los recursos de la empresa de la forma más eficiente posible a través de la automatización de procesos. El objetivo principal es el desarrollo de una Propuesta de Arquitectura Empresarial, utilizando el marco de trabajo TOGAF el cual analiza la situación actual del “AS IS” del proceso de negocio Seguimiento Académico, con la finalidad de proponer el enfoque deseado “TO BE”, el cual se basa en el análisis de brechas encontrado, que culmine con la propuesta de un Proyecto de desarrollo de Software, utilizando la metodología ágil SCRUM. El proceso de negocio Seguimiento Académico, tiene una necesidad de disponer de información académica e incidencias de los estudiantes, para que sean consultadas por los estudiantes, padres y la organización; es por ello que el presente proyecto profesional propone con el enfoque “TO BE”; disminuir los procesos manuales, reducir la duplicidad de información y reducir los costos de operación; con ello optimizar los tiempos de respuesta a través de la automatización de procesos. Todo ello se encuentra en la presente propuesta de Arquitectura Empresarial, la cual define el camino a seguir de la organización para el logro de sus objetivos. / Tesis

To achieve innovative performance in team-based working environments there are several factors which determine how well a team operate. It is crucial for business leaders to identify the clues of the innovation process in order to exploit the potential of creative solutions in IT-based product development. This study presents the project framework Scrum, which has gained popularity in recent years and has been adopted all over the world in delivering fast, and incremental IT-solutions. The framework consists of cross-functional teams, rules, artifacts and is based on routine events throughout the developmental process. Although the intended purpose of this framework is not for innovative performance, several researchers have found the framework being used in both managing innovative activities and to produce innovative results. Without specifying where in the process it occurs and how it facilitates innovative behaviour. By examining today's most used agile framework for developing, delivering and sustaining complex IT-products we aim to understand how organizations can utilize this framework in achieving innovative product development. The core methodology consists of interview studies with employees as well as executives in daily contact to the Scrum framework.  The literature study finds that the activities found in the Scrum framework bears resemblance to activities found regarding innovative product development. Mainly in the areas regarding learning and the width of cross-functional competency that resides in the development team.  Furthermore the study suggests that the Scrum framework allows the team a high degree of agency within the developmental process, which allows for creative development alongside the project goal. In regards to this dynamic the study finds that the innovativeness is then mainly dependent on the individuals consisting in the project group, and the work ethic, competence and willingness to be transparent in a group setting is what decides the capability to capture learning as a part of innovation. Further, we discovered that events such as Dailies and Retro to have a big impact in innovative aspects moving the project development process forward.

The Agile methodologies have attracted the software development industry's attention due to their capability to overcome the limitations of the traditional software development approaches and to cope with increasing complexity in system development. Scrum is one of the Agile software development processes broadly adopted by industry. Scrum promotes frequent customer involvement and incremental short releases. Despite its popular use, Scrum’s requirements engineering stage is inadequately defined which can lead to increase development time and cost, along with low quality or failure for the end products. This research shows the importance of activity planning of requirements engineering in improving the product quality, cost, and scheduling as well as it points out some drawbacks of Agile practices and available solutions. To improve the Scrum requirements engineering by overcoming its challenges in cases, such as providing a comprehensive understanding of the customer’s needs and addressing the effects of the challenges in other cases, such as frequent changes of requirements, the Design Thinking model is integrated into the Scrum framework in the context of requirements engineering management. The use of the Design Thinking model, in the context of requirements engineering management, is validated through an in-depth scientific study of the IBM Design Thinking framework. In addition, this research presents an Items Prioritization dEcision Support System (IPESS) which is a tool to assist the Product Owners for requirements prioritization. IPESS is built on information collected in the Design Thinking model. The IPESS tool adopts Analytic Hierarchy Process (AHP) technique and PageRank algorithm to deal with the specified factors and to achieve the optimal order for requirements items based on the prioritization score. IPESS is a flexible and comprehensive tool that focuses on different important aspects including customer satisfaction and product quality. The IPESS tool is validated through an experiment that was conducted in a real-world project / Includes bibliography. / Dissertation (PhD)--Florida Atlantic University, 2021. / FAU Electronic Theses and Dissertations Collection