147 pages pdf - ICT Digital Literacy

More documents

Recommendations

Info

Testing Here, External Testing There, Quality Assurance Everywhere Chapter 9: Testing Here, External Testing There, Quality Assurance Everywhere Testing … it is all about expecting the unexpected. Learn to be your own worst enemy – in this case it will only help! All that strategic planning, the perfectly negotiated contract, the wonderfully executed design, and your top-down and bottom-up buy-in will be quickly forgotten if problems begin to surface. #421: Test! Test! Test! After posting a module or course to the Web, and BEFORE announcing its availability to students, make sure that all sections of the module or course are accessible to the students and that all the links, etc. work like they were designed to. Wiiliam McPeck Maine State Government #422: Bring In The Instructional Designer Again At The "End" With quite a bit of the development happening in an outsourced way, the SME and the development teams are usually sitting miles (sometimes thousands of them) apart. The communication chain - starting from the actual thought originating with the SME and terminating at the programmer or graphic designer - could get really long. And with it increases the chances of information distortion. A good idea to catch (and resolve) such issues would be to have the Instructional Designer review the final product from the development team's end. Close the loop by ending as you began. Amit Garg #423: Make A Commitment To Accessibility For ALL Employees Include users with disabilities in the design, development, and testing of e-Learning. It’s the best way to determine true accessibility. You’ll save money (it costs a lot more to make e- Learning accessible after launch), produce a better quality course, have more productive and satisfied employees, reduce legal liability and enhance the corporate image. Dick Mahoney The Paciello Group #424: Wanted: Wide Range Of Testers Perform good, solid testing of the course prior to launching it. Have someone who is outside of the project review the course to check for spelling, grammar, functionality, etc. Also have a Subject Matter Expert test the course for accuracy. And have one of the learners who the course is designed for test it out for the transference of knowledge. Did the course meet the established learning objectives? Having many different people test out the course is crucial because they will all look for different things and you will get a wider breadth of feedback. Nancy Thompson Bank One #425: Make sure you … … test all user PC/Software possibilities, the bandwidth requirements, and build your content to the minimum configurations. Scott Sutker Wachovia Corporation 701 e-Learning Tips by The MASIE Center www.masie.com 84
Testing Here, External Testing There, Quality Assurance Everywhere #426: Creating Quality: How Can You Produce Cleaner Results Faster? 1. Plan for more than one round of testing. The first round of testing is traditionally called the Alpha test with the second round usually being called a Beta test. Once you do plan for more than one round of testing, still attempt to find all of the defects in the first test. 2. Use the 80/20 Rule. Have just a few people test the first round, and have several test in later rounds. Following the old 80/20 rule, 2-3 people can find the majority of the problems. However, it sometimes takes several people to uncover the remaining problems. 3. Don’t take any issue for granted. In other words, keep a detailed log of every problem that is found as well as clear notes about how and when it was resolved. This list can be an important reminder later of why you made certain decisions along the way, especially if there is ever a difference of opinion among team members about why an issue was resolved a certain way. 4. Verify every fix. Personally my least favorite part of the process, this step is extremely important. As a project manager, WBT producer, or one-man-team, you need to make sure that every defect is taken care of before delivering it to your client. Remember though, if you are the one that made the fix, be sure someone else verifies the fix for you. 5. Where possible, perform testing micro-cycles. Instead of having all of the testers test at the same time, then consolidate notes, have them test one at a time and perform quick fixes between testers. Be ready to get their feedback quickly, even real-time if possible and make the fixes as the issues come in or shortly thereafter. This allows the next tester to spend his/her time finding other problems for you rather than submitting the same problems the previous tester submitted. I call these “micro-cycles” because of the quick turnaround time. Using testing micro-cycles, you’ll get more testing bang for your testing buck. Garin Hess Papid Intake #427: Get Tough On Testing Have a good testing plan for courseware and never cut corners from testing time. We plan for 5 days of testing time for every course we develop and at least 10 days for 3rd party courses. We have a checklist of testing requirements that each course must pass. In the event the course does not pass a requirement, we have a process in place where we return the course to the developer and project leader for corrections. This keeps everyone in the loop regarding the status of the project. Debbie Strong Country Insurance and Financial Services #428: Execution = Perfection e-Learning has to be obviously easy to use so that anybody can figure it out with a minimum scan of the screen navigation. And every feature must work impeccably. Testing, Testing, Testing! Sally Heinz St. Paul Travelers #429: Get Real Always test your e-Learning in the environment most similar to the environment that the learner is using. Joseph Dunlap Northwestern Mutual Life Insurance #430: This Is Not Simple Stuff - Learn From Professional Testers Develop a test plan at the very beginning. If possible, get your organization's Testing & Integration department to conduct the testing. A good test procedure will be based upon written project requirements. We are talking about software development and/or systems integration and T&D professionals need to learn the proper tools to execute these projects efficiently. You cannot wing testing and failure to do proper testing will result in technical "gotchas" and e-Learning that doesn't satisfy customer requirements. Tom Swider 701 e-Learning Tips by The MASIE Center www.masie.com 85
Page 2 and 3:
Letter from Elliott Dear Colleague,
Page 4 and 5:
Getting Started: The ABC’s of “
Page 6 and 7:
Page 8 and 9:
Page 10 and 11:
Strategic Planning vs. Leading Will
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
So Many Choices, So Little Time - C
Page 30 and 31:
Content, Content (Not To Mention Co
Page 32 and 33:
Content, Content (Not To Mention Co
Page 34 and 35: Content, Content (Not To Mention Co
Page 62 and 63: The Learning Tools & Technology Tsu
Page 70 and 71: Global & Cultural Perspectives -- H
Page 72 and 73: Global & Cultural Perspectives -- H
Page 74 and 75: Still Learning After All These Year
Page 80 and 81: In Recognition & Rewards We Trust C
Page 82 and 83: In Recognition & Rewards We Trust #
Page 86 and 87: Testing Here, External Testing Ther
Page 88 and 89: Testing Here, External Testing Ther
Page 90 and 91: High Signal/Low Noise - Promoting L
Page 98 and 99: The Name Of The Game: Integrating &
Page 100 and 101: The Name Of The Game: Integrating &
Page 102 and 103: Pedagogy & Webagogy -- Ready, Set
Page 124 and 125: Hey, Who Moved My Administration &
Page 134 and 135:
Hey, Who Moved My Administration &
Page 136 and 137:
Measure for Measure: Doing The “R
Page 138 and 139:
Measure for Measure: Doing The “R
Page 140 and 141:
Thanks To Our Sponsors! Thanks To O
show all

147 pages pdf - ICT Digital Literacy

Create successful ePaper yourself

Delete template?

Save as template?