WOPR8: Call for Presentations (CFP)
Submitted by rstens on Wed, 20/12/2006 - 05:59.
context-driven testing | industry recognition | performance testing | performance testing patterns | performance testing tools | reliability testing | stress testing
Theme: Critical Incidents in Effective Performance Testing
Conference Location and Time
MITRE Bedford MA, USA
April 12 – 14, 2008
Major Questions of Interest
Questions we are interested in exploring at WOPR8 include:
What critical Incidents lead to effective performance testing? By sharing and attempting to understanding the critical incidents leading to effective performance testing we will explore how our craft can make an important contribution to all IT and Development projects.
A critical incident is an event, or incident, that forever changes the way an individual thinks about or conducts a task. For example, a critical incident in performance testing may be the time that you learned, by way of an embarrassing failure on go-live day, the importance of validating the available network bandwidth, even if the IT staff assures you that it is sufficient.
WOPR8 will be exploring all aspects of performance testing, including process, technologies, teams, tools, status reporting and stakeholder engagement. Some questions we are likely to address include:
In which experiences did performance testing made a difference?
In which experiences did performance testing fail to make a difference?
* How were performance problems discovered?
* What was their cause?
* How did performance testing uncovered problems?
* Was performance modeling effective?
* Were performance testing tools an influence factor?
* What has performance testing influenced and why?
o Software Requirements, Design, Development?
o System, Integration or Unit Testing?
o Customer Service, Support or Maintenance?
o Commercial success?
Exploring tester skills in performance testing?
* Which testing skills lead to effective performance testing?
Exploring organizational and business aspects of performance testing?
* How did the organization of the performance testing team lead to effective performance testing?
* What about communicating results?
* Influence of business context on performance testing?
* Awareness?
* Did terrible failures lead to effective testing?
* What is the story?
* How did you get business to support performance testing?
* When performance testing could have been effective but the results were either not used or misunderstood?
WOPR8 will give working practitioners (testers) a chance to examine, discuss and brainstorm these questions.
About WOPR
In the view of knowledgeable observers, WOPR attracts the best and the brightest performance testers and managers as participants. In fact, many participants have world-class reputations.
WOPR conferences are invitation-only, and generally are heavily over-subscribed. We have sometimes had to turn away two or more applicants for every one we invite.
Submitting a proposal to present at WOPR increases your chances of being invited.
We strive to make every conference an exquisite opportunity for learning and professional growth. They are intimate – we restrict attendance to less than 25 people per conference.
One of the important goals of WOPR is community building among performance and reliability test professionals.
WOPR conferences and tutorials are priced as close to free as we can make them, as we are a self-funded non-profit organization.
Read more on the about WOPR page.
Our Objectives (What we are Seeking in this CFP)
WOPR8 is seeking experience reports (ERs) of your relevant experiences and innovations from past projects and from your current initiatives (as-yet unfinished and unproven projects). For a description and samples of ERs, see the Paper Guidance and Case Studies & Papers pages.
We are more interested in effective presentations and enlightening exchanges than in formal papers. A detailed paper is welcome though not required. For your presentation, an organized outline is enough. We are looking for informative, in-depth storytelling by experienced practitioners. Your proposal to present should contain enough substance for us to understand and evaluate it. Content is more important than format. Your presentation should omit any confidential data (anything that requires an NDA).
Reports and presentations are welcome over a broad range of topics related to performance testing. The test domain is broad and may include real-time embedded devices, web sites, and international telecom networks.
Logistics
These topics are explained at http://www.performance-workshop.org:
* How to submit your proposal.
* Preparing your presentation and writing your paper.
* Qualities of a good experience report.
Detailed logistics with regards to the location, travel and hotels will follow shortly.
Dates
* Submit your proposal by: January 15, 2007
* Selections will be completed by: February 15, 2007,
* Submit your paper / presentation by: March 15, 2007.
Conference Location and Time
MITRE Bedford MA, USA
April 12 – 14, 2008
Major Questions of Interest
Questions we are interested in exploring at WOPR8 include:
What critical Incidents lead to effective performance testing? By sharing and attempting to understanding the critical incidents leading to effective performance testing we will explore how our craft can make an important contribution to all IT and Development projects.
A critical incident is an event, or incident, that forever changes the way an individual thinks about or conducts a task. For example, a critical incident in performance testing may be the time that you learned, by way of an embarrassing failure on go-live day, the importance of validating the available network bandwidth, even if the IT staff assures you that it is sufficient.
WOPR8 will be exploring all aspects of performance testing, including process, technologies, teams, tools, status reporting and stakeholder engagement. Some questions we are likely to address include:
In which experiences did performance testing made a difference?
In which experiences did performance testing fail to make a difference?
* How were performance problems discovered?
* What was their cause?
* How did performance testing uncovered problems?
* Was performance modeling effective?
* Were performance testing tools an influence factor?
* What has performance testing influenced and why?
o Software Requirements, Design, Development?
o System, Integration or Unit Testing?
o Customer Service, Support or Maintenance?
o Commercial success?
Exploring tester skills in performance testing?
* Which testing skills lead to effective performance testing?
Exploring organizational and business aspects of performance testing?
* How did the organization of the performance testing team lead to effective performance testing?
* What about communicating results?
* Influence of business context on performance testing?
* Awareness?
* Did terrible failures lead to effective testing?
* What is the story?
* How did you get business to support performance testing?
* When performance testing could have been effective but the results were either not used or misunderstood?
WOPR8 will give working practitioners (testers) a chance to examine, discuss and brainstorm these questions.
About WOPR
In the view of knowledgeable observers, WOPR attracts the best and the brightest performance testers and managers as participants. In fact, many participants have world-class reputations.
WOPR conferences are invitation-only, and generally are heavily over-subscribed. We have sometimes had to turn away two or more applicants for every one we invite.
Submitting a proposal to present at WOPR increases your chances of being invited.
We strive to make every conference an exquisite opportunity for learning and professional growth. They are intimate – we restrict attendance to less than 25 people per conference.
One of the important goals of WOPR is community building among performance and reliability test professionals.
WOPR conferences and tutorials are priced as close to free as we can make them, as we are a self-funded non-profit organization.
Read more on the about WOPR page.
Our Objectives (What we are Seeking in this CFP)
WOPR8 is seeking experience reports (ERs) of your relevant experiences and innovations from past projects and from your current initiatives (as-yet unfinished and unproven projects). For a description and samples of ERs, see the Paper Guidance and Case Studies & Papers pages.
We are more interested in effective presentations and enlightening exchanges than in formal papers. A detailed paper is welcome though not required. For your presentation, an organized outline is enough. We are looking for informative, in-depth storytelling by experienced practitioners. Your proposal to present should contain enough substance for us to understand and evaluate it. Content is more important than format. Your presentation should omit any confidential data (anything that requires an NDA).
Reports and presentations are welcome over a broad range of topics related to performance testing. The test domain is broad and may include real-time embedded devices, web sites, and international telecom networks.
Logistics
These topics are explained at http://www.performance-workshop.org:
* How to submit your proposal.
* Preparing your presentation and writing your paper.
* Qualities of a good experience report.
Detailed logistics with regards to the location, travel and hotels will follow shortly.
Dates
* Submit your proposal by: January 15, 2007
* Selections will be completed by: February 15, 2007,
* Submit your paper / presentation by: March 15, 2007.