Conference Overview


  1. Keynotes
  2. Concurrent Break Out Sessions
  3. Expo

QA IS NOT DEAD


Presented by:
Melinda Turner
Amber Buckley




 Better Software Conference West

Break OUt Session 1

This is not your fathers career:  Advice for the modern information worker.  
James Whittaker 








He also told us "Testing is Dead."  
He also wore a shirt that said: "Do Epic Shit"
  1. Sell
  2. Clairvoyance
    1. Ambition
    2. Passion
    3. Specialization
    4. Imitation
    5. Derivation
    6. Leadership
    7. Stage Presence

Break Out session 2

The Secrets of Mobile App Testing by Jason Arbon of Applause
Takeaways =
    1. utest community exists
    2. App testing is really interesting because it's the first time that any software item has quantified quality from the user perspective (in the form of app scores)
    3. Users consistently have only regularly use 10 apps.
    4. Each App category has most important features, order varies (Satisfaction, Usability, Interoperability, Content, Pricing, Stability, Performance, Elegance, Security, Privacy).  
    5. Free e-book for me = App Quality by Jason Arbon
  

 

Git Branching for Agile Teams

Dan Radigan, Atlassian

*Men vs Female count:  16:2

(After Mr. Whittaker's talk, it was quiet and slow, not as much of a stage presence)


Why Git and Agile?  - They are BFFs 


At Atlassian, they release 1-2x a day

In a SaaS team: master branch with multiple dev branches:


 Master always protects Master


*Basically, they are doing what are implementing

Break Out Session 3

Speed-reading your colleagues and bosses for understanding by Jennifer Bonine
    1. She basically did a little rundown of the Meyers Briggs assessment but she called them "Color energies" and had a matrix of red, blue, yellow, and green.
    2. Biggest takeaway = people typically takeaway only 7% of what you say from an interaction the rest is all non-verbal
  

Specification by Example: Stop Testing at the End

-Nate Oster, CodeSquads, LLC

I left this chat early due to not introducing me to anything new or relevant for our team.  

I have a copy of his PDF if anyone is interested.


Later, I ran into him in the elevator and he recognized me and wanted to know why I left early.

Tell him the truth or not hurt his feelings…?


 

After leaving Nate's chat, I jumped over here..only to find they were already wrapping up and the talk was more to present and promote their tool.

http://www.axosoft.com/


Expo

    1. Sales People
    2. Food
    3. Free Stuff



 An Agile Throwdown: Munich takes on the columbus Agile Benchmark Study

Michael Mah, QSM Associates

 

Presented a study that was done to show the global phenomena of agile and its successes. 

I have a  PDF copy of the report. 


 

Break out Session 4

From Good to Great:  Combining Session and Thread Based Test Management 

- Michael Albrecht



  • Should I use SBTM or TBTM? = Why not use both?!
  • AND include Models = Greatness ("xBTM")
  • Free tool called SBTExecute


The Workflow of this QA process:




Risk Based Testing in Agile Projects

- Erik Van Veenendaal, Improve Quality IT Services BT

Testing Challenges : Effectiveness and Efficiency
Risk based testing can deal with both

His focus of the talk is Risk Poker using the MoSCoW priority in theory to determine priority and  a Product Risk Management matrix to differentiate the "could test" and the "must test". 
likelihood vs impact


Break OUt Session 5

Spice up your test plans with Mind Maps
 -Jeanne Peng, Cisco Video Technologies 

    1. Everything is Complex and testing is infinitive
    2. Remember to ask questions
    3. Using Mindmaps for test planning
    4. Recommended Test Idea Meetings to make sure everyone is on the same page and get testing plan signoff
      • sync info about feature
      • share test strategy
      • gather new ideas and improvements
      • review the integration maturity level and priority
      • assign actions

Break Out Session 6

Session-Based Exploratory Testing in Agile Projects 
- Bob Galen

    1. Test Fests with Pair testing
  • Pairs = qa + opps; qa + devs; dev + dev; qa +qa
  •  execute two context based exploratory charters
  • Ran SBET for 9 months while building test documentation
  • Doesn't recommend SBET for long term regression
    • Not the core intent of exploring - controls exploration
    • Derails endgame from a defect discovery perspective
    • Better for test idea generation - ET is not repeatable
  • Test Idea Generation=
    •                      (1) Brainstorming (2) Formation (3) Prioritization (4) Execution (5) Retrospective


    • Helping Others Take Ownership of Conflict Resolution

    - Tricia Broderick, Santeon Group

    "Can I give you feedback?" triggers the same thing in the brain as "There's a bear!". 
    Things to think about if in a conflict:

    • Allow time for cooling off & reflection 
    • Engage curiosity and problem solving tendencies 
    • Maintain ownership 
    • Acknowledge  PERCEPTIONS don’t always match INTENTIONS 
    • Create  environment for effective communication

     Double Loop Learning
        • What they did
        • Effect/Reaction
        • Why we Think they did it
        • Why They did it


    Made with Slides.com