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.
what you never wanted to know about coemployment
a day in the life of Benjamin Skillen (Bengt Skillen) as he works simultaneously for Intel and PTI Global
Tuesday, July 25, 2006
Friday, July 14, 2006
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.
