I have created a training and orientation session for new QA testers. The training is based principally on MSPowerPoint. However, there is a handbook that attendees to the session will receive and can use it first during the session to follow along with the PowerPoint presentation. Later, they can use the information in the handbook as a resource. This training and orientation session seems simple enough to develop, but it has already gone through several iterations. It isn't enough to gather info and then develop the training session. I have to collaborate with administration to make sure what they consider pertinent and important facts are included. Often, there have been discrepancies among members of the administration. Finding compromises can be the biggest piece of work for the training. However, I feel the training is interesting and educational at the same time as it provides accurate and succinct definitions for what the QA tester needs to complete the job successfully, what tools will be needed, and what skills are necessary as well as what skills will be developed or expanded. In short, the training session makes sure that the QA tester knows what is essential for completing the job description successfully.

As I have a background in teaching adults and actually work as an ESL instructor at a local community college here in the Portland area, I am often asked by my superiors here at Intel to give training and mentoring to new hires. I helped a new hire today in fact. She had been learning the ropes when I had to show her how to verify whether bugs in the software were fixed or not. We use a specialized software program called PVCS Tracker to do so. Tracker allows debuggers to first enter in information about bugs that they find. This information catalogues all kinds of data, such as OS version, language, software component, severity of bug ect. Providing this information helps the software engineers locate and eliminate the bug. The software program then allows the debuggers to check if the bug is removed. My job today was to show the new hire, Fiona, how to check to see if bugs were removed. After giving her a little bit of theory and information about Tracker and how it can be used to verify that bugs have been eliminated, I demonstrated the process to her. Then I had her check for bug removal, too, by giving her verbal guidance and prompts to ensure she was able to complete the task from beginning to end. Too often, people demonstrate and then expect the process to be transparent. However, I have learned as a teacher that students need the hands-on experience also to solidify learning and understanding. In doing, people are able to experience the heuristic directly and can prompty comment and ask relevant questions as they come up, giving someone such as a mentor or instructor direct evidence that learning has or hasn't quite yet taken place. It serves as an informal means of assessment as well.

I've discovered already a lot about the difference between creating training within both the private and public sectors. Most of the training I have created thus far has been for the public sector. The private sector does not want a lot of what it perceives as "frills and extras" even if there is a logical explanation for including "frills and extras" in the training. They consider "frills and extras" as features that take more time, which means that their trainees will be away from work longer and, if trainees can bill for the training, more money spent on training. So, trim the fat, and keep that return on investment in mind when developing training in the private sector. Only the most essential information is considered worthy in private sector training and that information needs to be presented in the most straightforward and time-saving manner. It is a completely different style of training.

I am into using a systems approach to curriculum and training design. I've reviewed all the materials from PTI Global (Job Description et al.) and Intel about the tools and materials needed to be a successful QA tester in a localization department. I've also reviewd the job description and supporting information that are available for me for writing the questionnaire for the needs analysis. I will write a questionnaire that I will use to interview people of all ranks and files personally. I find writing down what people have to say is easiest for gathering info for a needs analysis. People are more likely to respond and in depth when all they have to do is verbally respond to questions. Sending out questionnaires is always a crapshoot. Many people don't have time to fill them out, or the desire, so the info gleaned from them is only adequate at best. After I write the first draft of the questionnaire, I will show it to my supervisors to see if any editing will need to be done. Then I will begin contacting people to see if they have time to sit down and respond to my questions.

So I work at Intel - actually I work for Intel and PTI Global. PTI Global is my employer while Intel is my client and provides the physical space and all the equipment I use to do my job. I have two jobs here. First, I debug Norwegian software. I examine the software, documentation, and associated components for problems. When I find a problem, I note what kind of problem it is (graphical, linguistic, functional) and the steps involved to reaching and recreating the problem. I take a screen shot of the problem and then file it. This file is sent to a software engineer who fixes it. He or she in turn sends it back to me and I have to verify if it really has been fixed or not. Depending on the size and nature of the project, debugging can be an easy or painfully difficult process. I mainly debug software for installation and proper use of network cards, but I also debug larger applications, such as Viiv. In a pinch, I can debug and am the back-up debugger for Swedish, Danish, Finnish, and French. The second job I do here is work as an instructional/curriculum designer. My teaching background has come in handy. When I started here, I was thrown to the wolves. I had to learn how to debug basically on my own. I am now putting together a series of trainings and classes that break the job down into logical parts or modules. For example, I have been working on an initial new hire training which covers not only the administrative and logistical information that a new hire would need, but also the rudiments of the job.