Quality Assurance in Agile Methodology


Book Description

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.




Agile Software Development Quality Assurance


Book Description

"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.




Testing in Scrum


Book Description

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.




Agile Testing


Book Description

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.




Agile Quality Assurance


Book Description

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




Agile Testing


Book Description

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.




Software Quality


Book Description

The book presents a comprehensive discussion on software quality issues and software quality assurance (SQA) principles and practices, and lays special emphasis on implementing and managing SQA. Primarily designed to serve three audiences; universities and college students, vocational training participants, and software engineers and software development managers, the book may be applicable to all personnel engaged in a software projects Features: A broad view of SQA. The book delves into SQA issues, going beyond the classic boundaries of custom-made software development to also cover in-house software development, subcontractors, and readymade software. An up-to-date wide-range coverage of SQA and SQA related topics. Providing comprehensive coverage on multifarious SQA subjects, including topics, hardly explored till in SQA texts. A systematic presentation of the SQA function and its tasks: establishing the SQA processes, planning, coordinating, follow-up, review and evaluation of SQA processes. Focus on SQA implementation issues. Specialized chapter sections, examples, implementation tips, and topics for discussion. Pedagogical support: Each chapter includes a real-life mini case study, examples, a summary, selected bibliography, review questions and topics for discussion. The book is also supported by an Instructor’s Guide.




Agile Processes in Software Engineering and Extreme Programming


Book Description

The XP conference series established in 2000 was the first conference dedicated to agile processes in software engineering. The idea of the conference is to offer a unique setting for advancing the state of the art in the research and practice of agile processes. This year’s conference was the ninth consecutive edition of this international event. The conference has grown to be the largest conference on agile software development outside North America. The XP conference enjoys being one of those conferences that truly brings practitioners and academics together. About 70% of XP participants come from industry and the number of academics has grown steadily over the years. XP is more of an experience rather than a regular conference. It offers several different ways to interact and strives to create a truly collaborative environment where new ideas and exciting findings can be presented and shared. For example, this year’s open space session, which was “a conference within a conference”, was larger than ever before. Agile software development is a unique phenomenon from several perspectives.




Agile Software Development Quality Assurance Complete Self-Assessment Guide


Book Description

How do you determine the key elements that affect Agile Software Development Quality Assurance workforce satisfaction? how are these elements determined for different workforce groups and segments? How will the Agile Software Development Quality Assurance team and the organization measure complete success of Agile Software Development Quality Assurance? Is a fully trained team formed, supported, and committed to work on the Agile Software Development Quality Assurance improvements? Will team members perform Agile Software Development Quality Assurance work when assigned and in a timely fashion? How do we maintain Agile Software Development Quality Assurance's Integrity? Defining, designing, creating, and implementing a process to solve a business challenge or meet a business objective is the most valuable role... In EVERY company, organization and department. Unless you are talking a one-time, single-use project within a business, there should be a process. Whether that process is managed and implemented by humans, AI, or a combination of the two, it needs to be designed by someone with a complex enough perspective to ask the right questions. Someone capable of asking the right questions and step back and say, 'What are we really trying to accomplish here? And is there a different way to look at it?' For more than twenty years, The Art of Service's Self-Assessments empower people who can do just that - whether their title is marketer, entrepreneur, manager, salesperson, consultant, business process manager, executive assistant, IT Manager, CxO etc... - they are the people who rule the future. They are people who watch the process as it happens, and ask the right questions to make the process work better. This book is for managers, advisors, consultants, specialists, professionals and anyone interested in Agile Software Development Quality Assurance assessment. All the tools you need to an in-depth Agile Software Development Quality Assurance Self-Assessment. Featuring 618 new and updated case-based questions, organized into seven core areas of process design, this Self-Assessment will help you identify areas in which Agile Software Development Quality Assurance improvements can be made. In using the questions you will be better able to: - diagnose Agile Software Development Quality Assurance projects, initiatives, organizations, businesses and processes using accepted diagnostic standards and practices - implement evidence-based best practice strategies aligned with overall goals - integrate recent advances in Agile Software Development Quality Assurance and process design strategies into practice according to best practice guidelines Using a Self-Assessment tool known as the Agile Software Development Quality Assurance Scorecard, you will develop a clear picture of which Agile Software Development Quality Assurance areas need attention. Included with your purchase of the book is the Agile Software Development Quality Assurance Self-Assessment downloadable resource, which contains all questions and Self-Assessment areas of this book in a ready to use Excel dashboard, including the self-assessment, graphic insights, and project planning automation - all with examples to get you started with the assessment right away. Access instructions can be found in the book. You are free to use the Self-Assessment contents in your presentations and materials for customers without asking us - we are here to help.




Guide to the Software Engineering Body of Knowledge


Book Description

The purpose of the Guide to the Software Engineering Body of Knowledge is to provide a validated classification of the bounds of the software engineering discipline and topical access that will support this discipline. The Body of Knowledge is subdivided into ten software engineering Knowledge Areas (KA) that differentiate among the various important concepts, allowing readers to find their way quickly to subjects of interest. Upon finding a subject, readers are referred to key papers or book chapters. Emphases on engineering practice lead the Guide toward a strong relationship with the normative literature. The normative literature is validated by consensus formed among practitioners and is concentrated in standards and related documents. The two major standards bodies for software engineering (IEEE Computer Society Software and Systems Engineering Standards Committee and ISO/IEC JTC1/SC7) are represented in the project.