"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.
Academic Paper from the year 2018 in the subject Computer Science - Software, grade: 3.5, Shaheed Zulfikar Ali Bhutto Institute of Science & Technology (Dubai Campus), course: Independent Study, language: English, abstract: Quality Assurance activities, in software development, are the backbone of any software development. Quality Assurance activities are not only responsible of product quality, but also for process development quality. In conventional software development Quality Assurance is looked after by a separate team. As the trends of software development moved towards Agile development, Quality Assurance activities also got changed. In Agile development developers perform most of the activities such as close collaboration among developer team; onsite customer and Test Developers. Test Driven Development is the approaches in agile development to achieve better product quality. In this study I highlighted the importance of Quality Assurance in different Agile methodologies. Mindset of Agile development always revolves around product quality but there is much work to be done to impart quality of process in agile development to get it standardized and more organized product. Quality Assurance activities remain centric and focused to testing. In this study I have compared different Agile methodologies and also highlighted the factors of Quality Assurance in each Agile method which can be improve overall software development of any product using Agile method. I proposed to add an extra layer of Quality Assurance in Agile projects. Purpose of inserting an extra layer, is to use the knowledge of Quality Assurance experts to achieve quality product in development process which will results in higher level of product quality.
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.
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.
Software development continues to be an ever-evolving field as organizations require new and innovative programs that can be implemented to make processes more efficient, productive, and cost-effective. Agile practices particularly have shown great benefits for improving the effectiveness of software development and its maintenance due to their ability to adapt to change. It is integral to remain up to date with the most emerging tactics and techniques involved in the development of new and innovative software. The Research Anthology on Agile Software, Software Development, and Testing is a comprehensive resource on the emerging trends of software development and testing. This text discusses the newest developments in agile software and its usage spanning multiple industries. Featuring a collection of insights from diverse authors, this research anthology offers international perspectives on agile software. Covering topics such as global software engineering, knowledge management, and product development, this comprehensive resource is valuable to software developers, software engineers, computer engineers, IT directors, students, managers, faculty, researchers, and academicians.
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.
This open access book, published to mark the 15th anniversary of the International Software Quality Institute (iSQI), is intended to raise the profile of software testers and their profession. It gathers contributions by respected software testing experts in order to highlight the state of the art as well as future challenges and trends. In addition, it covers current and emerging technologies like test automation, DevOps, and artificial intelligence methodologies used for software testing, before taking a look into the future. The contributing authors answer questions like: "How is the profession of tester currently changing? What should testers be prepared for in the years to come, and what skills will the next generation need? What opportunities are available for further training today? What will testing look like in an agile world that is user-centered and fast-paced? What tasks will remain for testers once the most important processes are automated?" iSQI has been focused on the education and certification of software testers for fifteen years now, and in the process has contributed to improving the quality of software in many areas. The papers gathered here clearly reflect the numerous ways in which software quality assurance can play a critical role in various areas. Accordingly, the book will be of interest to both professional software testers and managers working in software testing or software quality assurance.
This book contains the refereed proceedings of the 17th International Conference on Agile Software Development, XP 2016, held in Edinburgh, UK, in May 2016. While agile development has already become mainstream in industry, this field is still constantly evolving and continues to spur an enormous interest both in industry and academia. To this end, the XP conference attracts a large number of software practitioners and researchers, providing a rare opportunity for interaction between the two communities. The 14 full papers accepted for XP 2016 were selected from 42 submissions. Additionally, 11 experience reports (from 25 submissions) 5 empirical studies (out of 12 submitted) and 5 doctoral papers (from 6 papers submitted) were selected, and in each case the authors were shepherded by an experienced researcher. Generally, all of the submitted papers went through a rigorous peer-review process.
Quality is not the sole responsibility of QA. If the whole team doesn't take quality seriously, the release of new features will always be delayed or worse, buggy software gets released. I have heard many people referring to QA as just a testing entity, which possibly means QA does nothing within the agile environment other than testing. In addition, speaking of agile software development QA, some people may also think that it is just for monitoring agile software development processes, or doing testing only on the project. In Agile Quality Assurance, Anthony Baah shows clear evidence of the benefits for using agile QA in the software development concept and the Quality. QA acts as a liaison between the agile team and the business to ensure agile development policy and practices are adhered to. The agile QA provides the agile system engineering lifecycle expertise and guidance to the business people, release management and stakeholders. The team ensures that all the systems of the project go through the agile system engineering lifecycle process successfully. - PART I: Overview: Transitioning into Agile Transformation o Chapter 1 Agile Software Development Approach Transformation o Chapter 2 What QA Team Stands For in Agile Software Development o Chapter 3 The Evolving Role of QA o Chapter 4 QA and the Agile Development o Chapter 5 Scaling Agile QA o Chapter 6 QA - Risks And Cost Reduction in Agile Software Development - PART II: Agile Methodology: The Big Picture of Agile QA o Chapter 7 The Whole Team Approach o Chapter 8 Agile QA vs Test Plans or Test Cases o Chapter 9 Agile QA to Determine if Testing Is Done o Chapter 10 Agile QA vs Acceptance Criteria Development and Review o Chapter 11 Tracking Production Defects - Agile QA o Chapter 12 Improving Communication between Agile QA and Development Teams This book will help you clearly understand the benefits obtained from Agile QA. QA team has the ability to contribute to improving agile work practices within the team environment, ensuring software development efficiency that helps to bring about competitive advantage within the agile software development organization. All these are accomplished by the team's techniques utilized in finding escaped defects before they get into production environment. There are three hats QA wears which determine the type of helpful roles played in the agile software development. These include quality analyst to know the right things, quality assurer to build quality in, and quality ambassador to indicate if the whole agile team cares
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.
