Quality on agile projects what it means to you as a tester

  • 100 views
Uploaded on

Delivered as a lightening talk (10 mins) at the ANZTB Testing conference, Canberra, Australia, June 2013

Delivered as a lightening talk (10 mins) at the ANZTB Testing conference, Canberra, Australia, June 2013

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
100
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Quality on Agile ProjectsWhat it means to you as a testerEdwin DandoConsulting Manager@assuritynz
  • 2. Better education. By practitionersEdwin DandoConsulting Manager+ Originally a developer+ Active in agile movement since 2002+ Founded innovate agile consulting firm Clarus+ Professional Scrum Trainer with Scrum.org+ Approve all Australian trainer applications for Scrum.org+ Helped many companies adopt agile practices+ Passionate about improving the software industrySLIDE | 2
  • 3. Why is quality so important?SLIDE | 3Variability is intrinsic in Complex work.When it arises, what shifts in your organisation?
  • 4. Why is quality so important?SLIDE | 4For every $1 of competitive advantage gainedby cutting quality, it costs $4 to restore it
  • 5. Why is quality so important?SLIDE | 5Poor quality software inhibits businessagility. We want to respond but we cant.
  • 6. Why is quality so important?SLIDE | 6Which of these is the hardest to measure?
  • 7. SLIDE | 7
  • 8. Enemy = hidden undone work+ We think we are done, but we arentSLIDE | 8
  • 9. Total Cost of OwnershipSLIDE | 9+ 80-90% of the cost of typicalsoftware product happens afterit goes live.+ Minimise functionality to onlythat which is valuable. The bestcode is no codeo no cost, no bugs, nomaintenance, no support, nodecommissioningo ROI is infinite+ Develop the product so costs ofmaintainability, sustainability, and enhance-ability are minimised
  • 10. Cost of poor quality over timeSLIDE | 10020,000,00040,000,00060,000,00080,000,000100,000,000120,000,0001 2 3 4 5 6 7 8 9 10TCO Over TimeTypical QualityGood QualityYears
  • 11. Agile Approach = Transparency+ Transparency – empiricism, honesty.+ Inspect – to know exactly where we are Whats done and whats not done? What’s the state of the code base?+ Adapt - make informed decisions aboutwhat to do next+ Pre-requisite: CourageSLIDE | 11
  • 12. Your role on an agile team+ We are all accountable for quality+ Apply your skills to help us approach, define and measure quality+ Build quality in Teams understanding of the requirements Teams sizing of the work The design (testability, extendibility) The code quality (resilience, robustness)SLIDE | 12
  • 13. Fast feedback removes waste+ Automate low value work (regression, harnesses, mocks, stubs etc)+ Work with the developers “How are you going to develop it?” “Here’s how I am going to test it”+ Shorten feedback loops to developers Reduce context switching and knowledge fading+ Do less (only high value items), do fewer at once and do each well (done)SLIDE | 13
  • 14. Move from Gatekeeper to GuideSLIDE | 14
  • 15. Testing on agile projects is fun+ All in it together+ No more shrinking walls+ Differing viewpoints welcome :-)+ Give it a go!SLIDE | 15
  • 16. Questions?SLIDE | 16