|
|
A venture of
![]() |
|
![]() |
| HOME > QA for Agile Projects | NEXT STEPS | ||||||
|
QA for Agile Projects Because QA and testing in an agile environment is fundamentally different from QA and testing in a traditional environment. You need to understand the differences. This course focuses on practical issues faced by increasing numbers of testers and their managers. These issues arise because most corporations are still fairly traditionally structured even though many software development teams are heading full steam into modern iterative, incremental, component based, agile software development techniques. This leaves testers assigned to an agile team stuck coping with an organizational and technical paradigm shift that traditional policies and practices are inadequate to handle. The highly iterative environment characteristic of these modern development projects has a dramatic and comprehensive effect on all aspects of testing including test planning, scheduling, budgeting, risk assessment, overall test asset allocation and fundamental organizational issues. This course presents a disciplined approach of how to integrate testing processes with iterative/incremental software engineering practices. The course is founded on the philosophy that mature agile approaches to software development, while markedly unique, are as disciplined as any other mature software development approach. You need to learn this new discipline. If you are an IT, quality, or project manager, you need to understand the radically different approach to test and QA metrics in a truly agile environment. After the completion of this two-day tutorial, participants will be able to: Set up an appropriate test process for an iterative project Set up an appropriate organizational structure for an iterative project Determine which agile concepts are appropriate for any iterative project Use risk analysis to allocate testing effort Optimally coordinate the test team with the development team Plan, create and execute effective tests for modern iterative software systems Know how to develop system test cases from stories and acceptance criteria How to interact with developers in a Scrum environment Know when and how to automate testing Help product owners slice requirements and develop good acceptance criteria Help the team clarify and develop quality requirements An essential course for any member of an agile project – since all agile team members have testing responsibilities. The course is especially targeted to agile team members specializing in testing and QA Ideal for those looking to improve the value and effectiveness of testing on an Agile project or how to implement Agile methods within a test practice Test Leads, Test Managers and IT Leadership, who are responsible for leading and managing an organization’s Quality Assurance program as the organization transitions to an agile framework. 1. How is QA and testing in an agile environment different from QA and testing in a traditional environment? a. Different organization structure b. Different metrics c. Different skills d. Different tools e. Different set of persons involved 2. Is test planning different? a. YES! There is still planning, but it is done incrementally 3. Are mature agile approaches to software development as disciplined as any other mature software development approach? a. Yes, but the way we approach testing is different. It is just as rigorous, but different. 4. Will I still collect the same metrics? a. No. Instead of measuring defects found and test cases run, you will focus your metrics on delivered defects, and minimizing elapsed time between defect insertion and defect removal. 5. Will I still have traceability from requirements to test cases? a. Yes! All product backlog items will have acceptance criteria that are directly traceable to test cases 6. Will the QA department be in charge of Quality? a. No. The development will be in charge of quality. The QA department will evolve towards becoming a center of excellence. 7. Will the organizational structure for an iterative project be the same as for a traditional project? a. No, but there are a variety of organizational structures that can work in an agile environment. 8. Will I still use risk analysis to allocate testing effort. a. Absolutely, but it will be done more organically and less numerically. 9. I’ve heard agile teams automate all of their test cases. Is manual testing still needed? a. Yes. Mature agile teams use a lot of manual testing, but it tends to be more exploratory in nature and less “scripted” 10. Given the amount of Automated testing required on an agile team, will I need to learn QTP scripting? a. Probably not, most agile automation is “under the interface” and uses tools like Fitness or a native programming language. 11. Will I need to work with the product owner to help them specify good acceptance criteria for product backlog items? a. Yes, the product owner will need the help of someone with test design skills. 12. Will I need to help product owners slice requirements into appropriately sized PBIs. a. Yes, test design skills are needed for this activity. 13. Will I learn the details and “why” behind the answers to the questions above? a. Yes. That is why we are running this 2-day course. Introductions (09:00 – 09:30) Facilitator Introduction Participant Introductions and Expectations Overview of Day Day 1 Underlying Philosophy and Implications on Testing Process spectrum Agile Manifesto Scrum Agile testing fundamentals Stories and test cases Coordinating between embedded testing and independent testing Bug reporting and tracking Progress and quality assessment reports Identifying and quantifying risk Mapping risk to requirements and test cases Test case automation Agile metrics Retrospectives and testing Day 2 Definition of Done and impact on velocity EXtreme Programming (XP) and technical practices Mixed culture projects Fitting process to projects Creating and Executing System Test Cases Use cases vs. stories Stakeholder identification and Risk Analysis Value to the client Tracing requirements to test cases Finding test cases from stories Role of test Scripting in Agile projects Role of Exploratory testing in Agile projects Business facing vs technology facing tests Automated testing through the interface Automated testing under the interface Consulting Hour (16:15 – 17:15) Q&A Timothy Korson Qualifications: PhD , Information Systems from Georgia State University Certification: Certified Scrum Practitioner, Certified ScrumMaster at Scrum Alliance. Registered Education Provider for the Project Management Institute. (PMI REP) Experience Timothy has over 25 years of experience in Agile project management, SCRUM and Agile and Lean development techniques and processes. Dr. Korson has helped numerous organizations configure and implement new software processes and adapt their testing techniques, project management practices and corporate culture to these new agile strategies. Consulting Expertise Timothy has rich experience in Agile training and consulting for various organizations across the globe. He served as Consultant at IIST, Director at COMSOFT Consortium for the Management of emerging Software technologies, Consultant at many leading international organizations including: NASA Goddard Space Flight Center, AT&T, Nortel Networks, and IBM Global Services. He has also been an Affiliate Scientist at the Software Engineering Institute where CMMI was developed. Training Expertise SCRUM Agile Software Development including XP Managing the Test Process in Iterative and Incremental Projects Managing Quasi-Agile Projects Object-Oriented Design, Architectures, and Patterns Agile Project Management Fundamentals of Testing Testing Centers of Excellence Exploratory Testing SQL for Testers Requirements Slicing Test Design Selecting and Executing the most important tests Education/ Publications/ Achievements Dr. Korson is a frequent speaker at the major international Software Conferences. Tim has given over 100 keynotes and tutorials in Europe, Asia, and the US. For the first three months of 2012, Tim is scheduled to speak at Quest, Chicago; STC, Mumbai; and Code PaLOUsa, Louisville. In addition to speaking, Tim has published numerous articles on Agile software development. The more recent is titled: Dancing with Pigs and is available online at http://www.scrumalliance.org/articles/364-dancing-with-pigs CPE CREDITS For more information please visit www.softwarecertifications.org Rs. 25,000 for Single Nomination + Service Tax Task force of 4 participants: INR 95,000 Plus Taxes The price includes the course material, lunch & breaks each day. Hotel and travel arrangements are the responsibility of the attendee. Instructor Led Training with exercises and discussions on real life situations. Registration: 8:30 - 9:30 a.m. Morning Session 8:30 a.m. - 01:00 p.m. Lunch 01:00 - 1:45 p.m. Afternoon Session 1:45 - 5:00 p.m. This is a typical daily schedule. Please confirm the program schedule at registration.
|
UPCOMING EVENTS Security Testing May 25- May 26. Chennai Jun 07-Jun 08. Bangalore. Jun 26-Jun 27. Hyderabad Effective Test Management - Upping Your Game Jun 04- Jun 05. Bangalore Jun 06- Jun 07. Chennai MainframeTesting May 22- May 25. Hyderabad May 15- May 18. Bangalore Jun 11-Jun 14. Chennai Test Architecture Jun 14- Jun 15. Bangalore QA for Agile Projects Jun 19- Jun 20. Chennai Jun 21- Jun 22. Hyderabad |
|
|||||
| Edista Testing
Institute - A venture of QAI Global Institute Privacy Policy | Terms of Service © 2011 All Rights Reserved. |
TEST REPUBLIC - COMMUNITY OF SOFTWARE
TESTING PROFESSIONALS 9700+ Members | 210 Countries | Register Today! |