WOPR13 Call for Proposals (CFP)
<h1 style="text-align: center;"><span style="color: rgb(255, 102, 0);">WOPR13 Call for Proposals (CFP) </span></h1>
The content owner, Eric Proegler, along with the <span style="color: rgb(255, 102, 0);"><span style="font-weight: bold;">WOPR</span> </span>organizers, invites you to submit your proposal(s) for our next <span style="font-weight: bold; color: rgb(255, 102, 0);">WOPR </span>meeting. WOPRs are invitation-only mini-conferences, with attendance limited to 25.
<h2><span style="font-weight: bold;">Theme:</span> Performance Rules of Thumb </h2><h3>Conference Location and Dates </h3><ul>[*]WebMD, Portland, Oregon[*]WOPR13: Thursday-Saturday, October 15 - 17, 2009[*]Pre-WOPR Dinner: Wednesday, October 14, 2009[*]Pre-WOPR Training: Monday-Wednesday, October 12 - 14, 2009[/list]Immediately preceding WOPR13, Collard and Company will conduct a session of Ross Collardís Performance, Load and Stress Testing class. Some of the seats in this session will be offered to the public. Ross will be assisted by other WOPR organizers, creating a Performance Testing training experience hard to match at any price.
Thanks to the generosity of WebMD, our WOPR13 host, this session will be offered at well below standard rates. Please watch the <span style="font-weight: bold; color: rgb(255, 102, 0);">WOPR </span>Web Site for more information.
<h3>WOPR13 Theme Description </h3>Many testers develop job aids such as models, frameworks and tools. These aids often incorporate rules of thumb, or heuristics, which help monitor progress and quickly identify and resolve problems. Rules of thumb are similar to what have been called "Testing Smells"; practitioners use them to plan and conduct performance tests, analyze test results, and examine live systems.
We encounter familiar situations in our work every day, repeatedly deploying pre-determined solutions without thinking much about them. Our biases (often unrecognized) and our experiences drive our actions. Since these rules seem to be correct, or at least rarely proven wrong, we maintain them as valuable artifacts.
How well do these types of rules work for you? Where do you trust your rules-based judgment to solve problems without undue anxiety? Equally important, where have you been surprised? How do you decide what and how to test, your priorities, and when you are done?
At WOPR13, we will discuss these questions with professionals and experts in software and hardware performance, scalability, reliability, etc. We will review specific first-person experiences, compare findings and share intuitions.
We hope to learn more about how to conduct effective, credible and timely performance testing. We encourage insightful, talented people of varied experience levels and backgrounds to apply. Even if you do not believe you have a relevant experience, we welcome people who work in performance and reliability testing disciplines to contribute to the discussion.
Please bring us your first-person experience report that addresses one or more of these questions:
Depending on what emerges during the workshop, WOPR may publish content developed for and during the workshop on the WOPR website, as part of an ongoing effort to support and grow the community of performance testing.
- What rules do you use to plan and conduct performance testing?
- How reliable are your rules, and what are the exception cases?
- How do they help predict how systems scale - or fail?
- What happens if we apply them incorrectly?
- What are the characteristics of situations you have encountered where you have seen them before and neatly step ahead to plan, diagnose, an/or solve?
- Are there a limited number of ways response time and other measurements change as load increases?
- How many failures invalidate a performance test?
- What do you know before you start?
- What rules are you developing right now?
- What rules have you recently abandoned?
<h3>About WOPR </h3>In the view of knowledgeable observers, <span style="font-weight: bold; color: rgb(255, 102, 0);">WOPR </span>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 <span style="font-weight: bold; color: rgb(255, 102, 0);">WOPR </span>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.
<span style="font-weight: bold; color: rgb(255, 102, 0);">WOPR </span>conferences and tutorials are priced as close to free as we can make them, as we are a self-funded not-for-profit organization.
Read more on the about <span style="font-weight: bold;">WOPR</span> page.
<h3>Our Objectives </h3>WOPR13 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 on the WOPR web site.
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.
<span style="font-weight: bold;">Logistics </span>
These topics are explained at performance-workshop.org:
<ul>[*]Submit your proposal[*]Preparing your presentation and writing your paper[*]Qualities of a good experience report.[/list]
Detailed logistics with regards to location, travel, and hotels will follow shortly.
<span style="font-weight: bold;">Logistics Owner:</span> Cal Arnason
<h3>Dates </h3><ul>[*]Invitation to Submit Proposals Issued by: July 18, 2009[*]Deadline for submitting your proposal by: August 17, 2009[*]Selections Will Be Completed By: August 31, 2009[*]Pre-WOPR Training: Monday-Wednesday, October 12 - 14, 2009[*]Pre-WOPR Dinner: October 14, 2009[*]Workshop: October 15 - 17, 2009[/list]<h3><span style="font-weight: bold;">Costs </span></h3>WOPR is a not-for-profit, low cost workshop, however we do have expenses and we ask the WOPR participants to help us offset these expenses. Thanks to the generosity of our host, WebMD, the expense-sharing amount for WOPR13 has been set at <span style="font-weight: bold;">$250</span> per person.
Re: WOPR13 Call for Proposals (CFP)
Curious how the event turned out.
Any papers available to take a look at?