1. Copyright 2003-2005, Rally Software Development Corp Synchronizing Software Testing with Agile Requirements Practices Jean McAuliffe, Dean Leffingwell May 2005

2. Slide 2 Copyright 2003-2005, Rally Software Development Corp Background on Speakers Jean McAuliffe Product Manager, Rally Software Development 2 years Agile Development, Certified Scrum Master Former Senior QA Manager for Rational RequisitePro. Over 15 years experience in all aspects of software development (defining, developing, testing, training and supporting) for Software Development, Bio- Engineering and Aerospace companies Dean Leffingwell Advisor and coach to a number of developmental- stage software businesses. Former Senior VP of Rational Software Corporation where he was responsible for the commercial introduction of the Rational Unified Process. Lead author of the text Managing Software Requirements: Second Edition: A Use Case Approach, Addison Wesley, 2003

3. Slide 3 Copyright 2003-2005, Rally Software Development Corp Abstract Agile requirements practices generally defer commitment to artifacts such as requirements until the last responsible moment. This challenges the test team to stay continuously synchronized with the product owners and developers as they have little lead time, if any, from the time requirements are available until the time the test artifacts must be in place. This presentation describes the organizational and technical challenges associated with just-in-time agile requirements practices and techniques test teams can use to address them.

4. Copyright 2003-2005, Rally Software Development Corp Agenda Context for Agile Testing Technical Challenges Organizational Challenges Keys for Success

5. Slide 5 Copyright 2003-2005, Rally Software Development Corp Popular Agile Methods Dynamic System Development Method (Dane Faulkner) XP (Kent Beck) Adaptive Software Development (Jim Highsmith) Lean Software Development (Mary Poppendieck) Crystal (Alistair Cockburn)Feature Driven Development (Jeff DeLuca) Scrum (Ken Schwaber)Agile Rational Unified Process (RUP)

6. Slide 6 Copyright 2003-2005, Rally Software Development Corp Excerpts from the Agile Manifesto Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Working software is the primary measure of progress. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. http://agilemanifesto.org/principles.html

7. Slide 7 Copyright 2003-2005, Rally Software Development Corp A Generalized Agile Release Process Release Iteration 1Iteration 2 Iteration 3Iteration … Do Feature 1 Do Feature 2 Do Feature 3a Do Feature 3b Do Feature 4a Do Feature 4b Do Feature 5 Do Feature 4c Do Feature 6 Do Feature 7 Backlog Feature 8 Feature 9 Feature 10 …. Backlog Feature 1 Feature 2 Feature 3 …. Feature 9

8. Slide 8 Copyright 2003-2005, Rally Software Development Corp Agile Iteration Cadence Demo & Retro Iteration N Iteration N+1Iteration N-1 Detailed Iteration Planning & Design Dev Feature Priority 1 Auto. Tests Feature 1 Dev Feature Priority 2 Dev Feature Priority 3 Auto. Tests Feature 3 Dev Feature Priority 4 Auto. Tests Feature 4 Dev Feature Priority 5 Auto. Tests Feature 5 Accept Auto. Tests Feature 2 Accept Requirements Are Refined Initial Elaboration Requirements With Tests

9. Slide 9 Copyright 2003-2005, Rally Software Development Corp Whats Different about Testing in Agile? Just-In Time Requirements Elaboration No SRS-level waterfall documents to drive testing plan Requirements and Test Cases developed in parallel or test first strategy More Frequent Iterations, More Frequent Releases Testing needs to happen Early and Often Frequent to continuous regression testing High need to automate nearly everything Everyone needs to Test Two Levels of Testing Iteration Vs. Release testing patterns

10. Copyright 2003-2005, Rally Software Development Corp Technical Challenges Requirements are changing fast. How does test keep up? Test early and often. How exactly do we move testing forward? Need to move off manual testing and more into automation. How does this happen? Different kinds of testing need to happen at different times. How do these get managed?

11. Slide 11 Copyright 2003-2005, Rally Software Development Corp Requirements are Changing Code & Deliver Generate TCs UC/SR Update TCs Run TCs Fail TCs Code & Deliver Pass & Accept Code & Deliver Updates

12. Slide 12 Copyright 2003-2005, Rally Software Development Corp Requirements Changing is a Good Thing? Probably the hardest agile principle for the team to embrace. Need to elaborate the feature ahead of time There is minimal time to have the team review before the start. Sometimes you have to rewrite Bottom-line: everyone collaborates to make the feature as useful for the customer as possible.

13. Slide 13 Copyright 2003-2005, Rally Software Development Corp Requirements to Test Cases Use Case Scenario Tests are perfect Acceptance Tests Use Case A Scenario 1 Test Case 1 Scenario 2 Test Case 2 Declarative Requirements that further refine the Use Case may be better suited to going directly to automation Have one Test Case be the container for all of the automation results. All automated tests have to pass before the Test Case passes.

14. Slide 14 Copyright 2003-2005, Rally Software Development Corp Need to Test early and often Need to test early in the Iteration – do not want mini-waterfalls Need to test on check-in – Dont break the build Need to test nightly – Dont wait for a Regression Iteration

15. Slide 15 Copyright 2003-2005, Rally Software Development Corp Mike Cohns Testing Pyramid GUI Acceptance Tests FitNesse Unit Tests Small number Automate many Find the right ones Largest numbers Foster Test Driven Design StartStop?StartStopLook

16. Slide 16 Copyright 2003-2005, Rally Software Development Corp Break the Manual Testing Paradigm Manual GUI Acceptance Tests Unit Tests Automated GUI Tests Easy to Create Very familiar – what we always do Typically tedious How do we know coverage? Need Automation specialists Automation good for performance Seems like we always rewrite Sometimes fragile What is Dev testing? How do we know what these are? How do we know when they fail? StartStop?StartStopLook

17. Slide 17 Copyright 2003-2005, Rally Software Development Corp Manual Testing Conundrum You can never have too many manual acceptance tests Manual tests are cute little bunnies, before you know it you have hundreds or thousands in your regression suite You inadvertently dig a hole you can never get out of Whole team had to help run regression suite Defect count typically is high Most defects were found as manual tests were elaborated Regression tests typically didnt find many defects Commonly found defects – things we didnt think of

18. Slide 18 Copyright 2003-2005, Rally Software Development Corp Better, But Not Perfect Testing Architecture Unit Tests Manual GUI Acceptance Tests Automated GUI Tests & FitNesse Still too many here Add FitNesse Increase Coverage Increase Capability StartStopLook

19. Slide 19 Copyright 2003-2005, Rally Software Development Corp Testing Types and Scheduling Acceptance – GUI? Minimize Manual Generate off of Use Cases to get scenario tests. During the Iteration Acceptance - Functional Combination of Unit tests, FitNesse Build Verification and Run Nightly Load & Performance Profiling and Simulation Automation Do it periodically Dont wait till the end of the Release cycle Regression Acceptance and Functional tests from previous Iterations Run Nightly Exploratory Manual Group Explore Roles and Personas Before Releasing

20. Slide 20 Copyright 2003-2005, Rally Software Development Corp Keys to Overcome the Technical Challenges Continuous Builds Nightly Regression testing Find a way to increase FitNesse testing at the application layer http://fitnesse.orghttp://fitnesse.org Make Unit Testing a priority From found defects – create automated tests that go into Regression

21. Copyright 2003-2005, Rally Software Development Corp Organizational Challenges Dev as Testers and Testers as Dev – how does that happen? Resistance to Change – how do we get the team to welcome and embrace changes and not feel threatened? Testers are an integral part of the team- do we need to re-organize to make this happen?

22. Slide 22 Copyright 2003-2005, Rally Software Development Corp Im a Developer, Not a Tester Pretty typical to hear push back from developers that they Dont have time to do all of this testing Number of features delivered will go down Dont really want to do all this testing Testers can help Provide guidance on how to break software, art of creative destruction Pair testing with developers works well Have developers help out with manual regression testing. Cant I write a test for this instead of running it manually?

23. Slide 23 Copyright 2003-2005, Rally Software Development Corp Im a Tester Not a Developer Pretty typical to hear from testers That they dont feel comfortable or knowledgeable about coding That they maybe wont be needed anymore Developers can help Developers can create the fixtures (code running the test) needed to make FitNesse testing work To make it easier to auto test the code at the GUI level

24. Slide 24 Copyright 2003-2005, Rally Software Development Corp Resisting Change Resistance is common It is easier to do what is familiar, than risk something new Time-challenges may keep you doing the old way Fear of failing keeps you in the status quo Get the whole team involved in trying to change Team needs to figure what works best Dont feel like you have to do everything all at once Keep learning and adapting

25. Slide 25 Copyright 2003-2005, Rally Software Development Corp Testers on the Team Your organization may have testing as a separate group – look for ways to integrate them into the team Creating feature or component teams comprised of all disciplines is one way Co-location is a great way to hear and share information Daily stand-ups with the whole team keeps the information current

26. Slide 26 Copyright 2003-2005, Rally Software Development Corp Keys to Overcome the Organizational Challenges Have Dev help run manual Regression tests Pair Dev and Test on Unit and FitNesse Testing Co-location of all the team Daily Standups Do Retrospectives

27. Slide 27 Copyright 2003-2005, Rally Software Development Corp Summary Agile Pulls Testing Forward You need to change your tools and approaches to move it forward You might need to change the model/structure of your team With Agile, you will create faster Release cycles, shorter Iterations, more satisfied customers, and team members that enjoy what they are doing

28. Slide 28 Copyright 2003-2005, Rally Software Development Corp Useful References Beck, Kent, Test-Driven Development By Example, Addison Wesley, 2003 Cohn, Mike, User Stories Applied For Agile Software Development, Addison Wesley, 2003 Crispin, Lisa, House, Tip, Testing Extreme Programming, Addison Wesley, 2003 Leffingwell, Dean, Widrig, Don, Managing Software Requirements: Second Edition: A Use Case Approach, Addison Wesley, 2003

29. Slide 29 Copyright 2003-2005, Rally Software Development Corp Thank You Contact Info Jean: jean.mcauliffe@rallydev.com Dean: dleffing@earthlink.net Questions?jean.mcauliffe@rallydev.comdleffing@earthlink.net Copyright 2003-2005, Rally Software Development Corp