{"id":1313,"date":"2020-02-09T06:16:36","date_gmt":"2020-02-09T06:16:36","guid":{"rendered":"http:\/\/35.178.110.234\/?page_id=1313"},"modified":"2020-02-12T07:02:00","modified_gmt":"2020-02-12T07:02:00","slug":"test-development-process","status":"publish","type":"page","link":"https:\/\/ielca.org\/test-development-process\/","title":{"rendered":"Test Development Process"},"content":{"rendered":"
[vc_row layout=”container”][vc_column]
Each qualification cycle is commissioned in order to enable the necessary resources for each item writing team with commissioning meetings held at leadt twice a year or more frequently when required.<\/p>\n \t\t\t<\/div>\n [\/vc_column][\/vc_row][vc_row layout=”container”][vc_column]\t\t\t
Content Development meetings are attended by the content development team and relate directly to non-item development but impact directly on the item writing process.<\/p>\n \t\t\t<\/div>\n [\/vc_column][\/vc_row][vc_row layout=”container”][vc_column]\t\t\t
Item writers write items with peer review taking place (up to one re-write allowed on item writer's work) on each other's work to the reviewer's checklist. Once an item has been rewritten more than once it is deemed invalid. Reviewer's returns are also sampled by the test development writers, who make amendments based on feedback from the reviewer, befoore re-submission.<\/p>\n \t\t\t<\/div>\n [\/vc_column][\/vc_row][vc_row layout=”container”][vc_column]\t\t\t