Deficiencies of scope statements in ITLET standardization

To execute good design one not only needs to know what to do and how to do it, but also why it should be done. For a standardization expert the rationale of a standardization project may be found in the proposal for a new work item or terms of reference, but rarely in the scope statement. However, it is also commonplace that the rationale of the project is not clearly stated in any of these parts. If the rationale is not surfaced in the early phases of a project, it is left to the design, sense-making and negotiation cycles of the design process to orient the project towards a goal. This paper explores how scope statements are used to position standardization projects in the IT for Learning, Education and Training (ITLET) domain, and how scope and rationale are understood in recent projects in European and international standardization. Based on two case-studies the paper suggests some actions for further research and improvement of the process.