"This book provides the research and instruction used to develop and implement software quickly, in small iteration cycles, and in close cooperation with the customer in an adaptive way, making it possible to react to changes set by the constant changing business environment. It presents four values explaining extreme programming (XP), the most widely adopted agile methodology"--Provided by publisher.

These days, more and more software development projects are being carried out using agile methods like Scrum. Agile software development promises higher software quality, a shorter time to market, and improved focus on customer needs. However, the transition to working within an agile methodology is not easy. Familiar processes and procedures change drastically. Software testing and software quality assurance have a crucial role in ensuring that a software development team, department, or company successfully implements long-term agile development methods and benefits from this framework. This book discusses agile methodology from the perspective of software testing and software quality assurance management. Software development managers, project managers, and quality assurance managers will obtain tips and tricks on how to organize testing and assure quality so that agile projects maintain their impact. Professional certified testers and software quality assurance experts will learn how to work successfully within agile software teams and how best to integrate their expertise. Topics include: Agile methodology and classic process models How to plan an agile project Unit tests and test first approach Integration testing and continuous integration System testing and test nonstop Quality management and quality assurance Also included are five case studies from the manufacturing, online-trade, and software industry as well as test exercises for self-assessment. This book covers the new ISTQB Syllabus for Agile Software Testing and is a relevant resource for all students and trainees worldwide who plan to undertake this ISTQB certification.

This book is written by testers for testers. In ten chapters, the authors provide answers to key questions in agile projects. They deal with cultural change processes for agile testing, with questions regarding the approach and organization of software testing, with the use of methods, techniques and tools, especially test automation, and with the redefined role of the tester in agile projects. The first chapter describes the cultural change brought about by agile development. In the second chapter, which addresses agile process models such as Scrum and Kanban, the authors focus on the role of quality assurance in agile development projects. The third chapter deals with the agile test organization and the positioning of testing in an agile team. Chapter 4 discusses the question of whether an agile tester should be a generalist or a specialist. In Chapter 5, the authors turn to the methods and techniques of agile testing, emphasizing the differences from traditional, phase-oriented testing. In Chapter 6, they describe which documents testers still need to create in an agile project. Next, Chapter 7 explains the efficient use of test automation, which is particularly important in agile development, as it is the main instrument for project acceleration and is necessary to support state-of-the-art DevOps approaches and Continuous Integration. Chapter 8 then adds examples from test tool practice extending test automation to include test management functionality. Chapter 9 is dedicated to training and its importance, emphasizing the role of employee training in getting started with agile development. Finally, Chapter 10 summarizes the results of the agile journey in general with a special focus on testing. To make the aspects described even more tangible, the specific topics of this book are accompanied by the description of experiences from concrete software development projects of various organizations. The examples demonstrate that different approaches can lead to solutions that meet the specific challenges of agile projects.

This book examines how and why collaborative quality assurance techniques, particularly pair programming and peer code review, affect group cognition and software quality in agile software development teams. Prior research on these extremely popular but also costly techniques has focused on isolated pairs of developers and ignored the fact that they are typically applied in larger, enduring teams. This book is one of the first studies to investigate how these techniques depend on and influence the joint cognitive accomplishments of entire development teams rather than individuals. It employs theories on transactive memory systems and functional affordances to provide answers based on empirical research. The mixed-methods research presented includes several in-depth case studies and survey results from more than 500 software developers, team leaders, and product managers in 81 software development teams. The book’s findings will advance IS research and have explicit implications for developers of code review tools, information systems development teams, and software development managers.

Software Quality Assurance in Large Scale and Complex Software-intensive Systems presents novel and high-quality research related approaches that relate the quality of software architecture to system requirements, system architecture and enterprise-architecture, or software testing. Modern software has become complex and adaptable due to the emergence of globalization and new software technologies, devices and networks. These changes challenge both traditional software quality assurance techniques and software engineers to ensure software quality when building today (and tomorrow's) adaptive, context-sensitive, and highly diverse applications. This edited volume presents state of the art techniques, methodologies, tools, best practices and guidelines for software quality assurance and offers guidance for future software engineering research and practice. Each contributed chapter considers the practical application of the topic through case studies, experiments, empirical validation, or systematic comparisons with other approaches already in practice. Topics of interest include, but are not limited, to: quality attributes of system/software architectures; aligning enterprise, system, and software architecture from the point of view of total quality; design decisions and their influence on the quality of system/software architecture; methods and processes for evaluating architecture quality; quality assessment of legacy systems and third party applications; lessons learned and empirical validation of theories and frameworks on architectural quality; empirical validation and testing for assessing architecture quality. - Focused on quality assurance at all levels of software design and development - Covers domain-specific software quality assurance issues e.g. for cloud, mobile, security, context-sensitive, mash-up and autonomic systems - Explains likely trade-offs from design decisions in the context of complex software system engineering and quality assurance - Includes practical case studies of software quality assurance for complex, adaptive and context-critical systems

This comprehensive reference on software development quality assurance addresses all four dimensions of quality: specifications, design, construction and conformance. It focuses on quality from both the micro and macro view. From a micro view, it details the aspect of building-in quality at the component level to help ensure that the overall deliverable has ingrained quality. From a macro view, it addresses the organizational level activities that provide an environment conducive to fostering quality in the deliverables as well as developing a culture focused on quality in the organization. Mastering Software Quality Assurance also explores a process driven approach to quality, and provides the information and guidance needed for implementing a process quality model in your organization. It includes best practices and valuable tools and techniques for software developers.Key Features • Provides a comprehensive, inclusive view of software quality • Tackles the four dimensions of quality as applicable to software development organizations • Offers unique insights into achieving quality at the component level • Deals comprehensively with all aspects of measuring software quality • Explores process quality from the standpoint of implementation rather than from the appraiser/assessor point of view • Delivers a bird's eye view of the ISO and CMMI models, and describes necessary steps for attaining conformance to those models

Crispin and Gregory define agile testing and illustrate the tester's role with examples from real agile teams. They teach you how to use the agile testing quadrants to identify what testing is needed, who should do it, and what tools might help. The book chronicles an agile software development iteration from the viewpoint of a tester and explains the seven key success factors of agile testing.