Sunday, 23 June 2013

STePIN Summit 2013

Why should we attend software testing conferences?
  1. Learn to test by networking with the learned.
  2. Get to learn what's happening in the testing world.
  3. Learn the trending techniques and tools used for testing.
  4. Share your ideas and implementation, used cases and lessons learnt.
  5. To learn how to be better/excel at what you are already doing and how you are doing it.
  6. Learn presentation skills.
  7. Question the crude ways of testing.
Excerpts from some of the talks at STePIN Summit.

Lee Copeland - Author of A Practitioner's Guide to Software Test Design.
Writes at StickyMinds 
Connect with Lee at lcopeland@sqe.com
Presented @ STePIN Summit on The Mismeasure of Software: The Last Talk on Metrics You’ll Ever Need to Hear
  1. Don't measure if you don't know what it means.
  2. Focus on reality. The map is not the territory.
  3. If something is not working for you, don’t do it just because it is in the model, template or a rule book.
  4. Don't measure effort, measure accomplishments.
  5. Don't measure the number of defects, test cases. Have someone to measure the cost saved through testing.
  6. Don't turn your measurement into a goal.
  7. What gets measured gets manipulated.
  8. Don't obey everything told and presented to you by elders blindly. Invest some time in investigating prior to approving.
  9. While testing if surprised by any behavior, examine the reason for surprise.

Keith Klain 
Writes at qualityremarks
Connect with Keith here
Presented @ STePIN Summit on Creating Dissonance Overcoming Organizational Bias towards the Value of Software Testing

If you are a change agent at your organization:
  1. Be the change.
  2. Get the team involved to understand the change.
  3. Get connected.
  4. Get educated.
  5. Get more organized.
  6. Start a movement.
  7. Understand changing culture is hard.
  8. Don't mandate a change.
  9. Don't be rigid on process. Don't be process oriented.
  10. Manage your own expectations.
  11. Be an active advisor. Take charge {not an order taker}.
  12. Be an organizational navigator.

Find answers to these questions.
  1. In case of crisis who did you reach out to?
  2. Will you suggest others to approach this person in times of their own crisis?
  3. Which is the last testing book you read? When was it written?
  4. Who are the people that are advising you?
Learn by questioning, while building the skills, build a network that would together help you achieve a common goal.

Why is it hard to support an idea?
Guess this is what differentiates many firms from the likes of many others who support and encourage their employees to dedicate a certain amount of time for working on their own projects while being associated and working on other projects.

Naveen S Yeshodara, Software Consultant, Novell Software Development and Sumanth Krishna, McAfee India two presentors at the STePIN Summit 2013 who shed light on this topic while also conveying their idea, Data Leak Prevention application on Consumer Electronic Devices.


Here’s a face book page for all idea generators to log your ideas.
This is a place holder for ideas. Any user can log in and like this page, and log your ideas here.

What Next?
Find friends who could help your idea be a reality, contribute to your idea, take it to the next level and help implement your idea.

Further reading:
  1. Map-territory error
  2. Reification error
  3. Blink – Malcolm Gladwell
  4. Satir interaction Model - Virginia Satir
  5. Jerry Weinberg's Rule of Three.
  6. How to get approval to attend conferences or training's
       Next testing conference held in Bangalore.

No comments: