NIMBLE: the Next Best Agile Method since Sliced Bread

Transcription

1 NIMBLE: the Next Best Agile Method since Sliced Bread John Watkins IBM Client Technical Architect 2012 IBM Corporation

2 The NIMBLE Method NIMBLE is a Light Weight testing process Each NIMBLE Test Project is bounded by a CRUST (Common Retrospective User/Stakeholder Talk) Tasks in NIMBLE are organised into Slices Slice durations/effort expended/cash spent are bounded using a Bread-Box technique If a NIMBLE process is not correctly followed it is likely that MOLD (Major Outage Level Defects) will start to appear 2

3 The NIMBLE Method The quality control aspect of NIMBLE involves CRUMBs (Correlated Requirement to Usecase Mapping Baselines) being gathered together once each NIMBLE Slice is complete A sufficiently large pile of CRUMBs can be taken as proof of a successful NIMBLE slice and progress can me made towards the CRUST NIMBLE is not without risks and a lack of proper governance could ultimately lead to the project becoming ToA/ST (Terminated on Acceptance/Suitability Terms) 3

4 Overview Recap of the NIMBLE Method Why do we see So Many New Methods? Agile Experiences in Real World Agile Projects A Proposal for a Starter Set of Agile Best Practices Summary and Conclusions Its Difficult to make software Idiot Proof, because Idiots can be so Ingenious 4

5 Why do we see So Many New Methods?

6 Why do we see So Many New Methods? NIH Not Invented Here Syndrome Practitioner Ego! Lack of Time to perform Research Google Conferences & Special Interest Groups Books, Courses, Webinars Laziness is nothing more than the habit of having a rest before you get tired Jules Renard 6

7 Agile Experiences in Real World Agile Projects

8 Real World Agile Research - Overview Based on a review of 30+ Agile Case Studies Covers Many Different Agile Methods Covers a Variety of Different Project Environments Conducted as Research Towards a book on Agile Testing Reports Varied Views on the Successes and Failures of Agile Projects Somewhere, something incredible is waiting to be known, Dr Carl Sagan on the subject of research 8

9 Agile Practice Check-List from the Book 10

10 A Proposal for a Starter Set of Agile Best Practices

11 Overview Review a set of Synergistic Agile Practices: 12 Ensure Everyone has access to Test Process Details Adopt Test Driven Development Employ Pair Testing Follow a Continuous Integration & Test Approach Strongly Consider the Role of Test Automation Employ Effective Reporting & Visualisation of Defects Fix All Defects Immediately Don t Forget the Lessons of History Those who forget the lessons of history are doomed to repeat its mistakes, George Santanaya

12 Provide Access to Test Process Details Everyone must have access to the process Can be as simple as reference cards (e.g. EssUP) Can be an on-line distributed solution (e.g. RUP) Can be enforced through tool use (e.g. RTC & RQM) Process enforcement tools very useful for off-shoring DON T Forget Good Training and Process Nurturing Pair Testing / Visualisation / Lessons 13

13 Adopt Test Driven Development This is a virtuous circle of behavior The developer writes the test Develops the code Tests Refactors the code Kent Beck claims TDD Encourages simple designs and inspires confidence In practice, results are good Integrate & Test / Visualisation / Fix Defects Immediately 14

14 Employ Pair Testing Two Heads are Better than one! Analogous to the XP practice of Pair Programming Has a number of possible implementations: Tester & Tester Tester & Programmer Process / Lessons / TDD Tester & User Tester & Analyst Encourages Team Working & Empathy But, beware Bean Counters & the QA Police Syndrome 15

15 Continuous Integration & Test Approach Code added to code base as it is developed Build performed and Automated Tests executed Detected Defects Highlighted Immediately Cause of Defect Localised and Easily Identified Defects are Corrected as development progresses Requires a moderate level of automation Test Automation / Visualisation / Fix Defects Immediately 16

16 Consider the Role of Test Automation Case studies report the value of test automation Developer level test tools virtually ubiquitous Continuous Build, Integration and Test Relies on effective Automation Capture Replay tools can save time, effort & cost Not the universal test panacea (still a role for Laser Guided Testing ) Smaller projects may not justify the use of tools Integrate & Test / Visualisation / Fix Defects Immediately 17

17 Effective Reporting & Visualisation of Defects Detected Defects must be Highlighted All Team Members must be Informed Speed of Reporting is Key Innovative Solutions can be very Valuable: Real-time on-line dashboards Instant messaging and SMS Lava Lamps!!! Used Correctly, Ensures Defects are Fixed Quickly Integrate & Test / Test Automation / Fix Defects Immediately 18

18 Fix All Defects Immediately Do not Allow a Backlog of Defects to Build Once a Defect is Detected, all Activity Stops The Focus is on Understanding the Defect Tracking down the cause Correcting the defect and re-testing Prevents Late Project Detection of Defects Integrate & Test / Test Automation / Visualisation 19

19 Don t Forget the Lessons of History Make Sure You Learn From Experience! Hold Sprint / Task / Project Retrospectives Use Good Communications Techniques (everyone s perspective is important) Modify your process as required (& document why) And, make sure everyone knows about the improvements Synergy with all of the above practices! 20

20 Summary & Conclusions

21 REMEMBER There is NO One Size Fits All Test Process Everyone is Different: different sized projects different code complexity different budgets, timescales and/or resources different team members of varying experience different project politics different purposes; in-house, bespoke, commercial, etc Tailor Your Approach with Knowledge, Experience & Sense 22

22 Summary Testers are under Increasing Pressure to be as Effective & Efficient as Possible; so please avoid re-inventing the wheel!!! There are Many Agile Approaches that Need to be Considered; Do your research, avoid letting ego get in the way, & don t limit your choices there are some excellent old school practices to reuse too There are a Number of Agile Practices that the Case Study Analysis Suggests as being Successful; seriously consider using the agile best practices covered in this presentation and in my Agile book on your projects Introduction, Roll-out and Adoption of Agile Practices can be Challenging, but the Results can be Rewarding Persevere! 23

23 John Watkins, IBM Client Technical Architect IBM Corporation