Quality Plan


  1. Introduction
    • Purpose and objectives

      Quality Management in a project assures the quality of the project deliverables and the quality of the processes and procedures used to manage and develop the deliverables. The purpose of this document is to describe the necessary information required to effectively manage project quality, from project planning to delivery, comprising quality objectives in the project, roles and responsibilities, and the Quality Management approach to ensure that the quality objectives are achieved. The intended audience is the project team and any senior leaders whose support is needed to carry out the plan.

    • Reviews and approval

      This Quality Plan is to be continually reviewed, and any changes to the plan will be handled through all-partners approval process; either in all-partners meeting, or by digital communication channels.
      The plan is approved by the Project Coordinator.

    • Document conventions

      Square brackets [x] are used to indicate reference documents. The references are always made to the document's document name.
      Italic is used for references to other sections in the document.

  2. Quality Objectives
    • The Quality Objectives for Quality Management in the IMPAQT project are to assure that:
      • Project deliverables meet their stated requirements.
      • Project Management processes are appropriately followed.
    • They answer the questions:
      • What is it the project shall achieve, that is, what is the expected result?
      • Project Management processes are appropriately followed.
    • In the IMPAQT project the overall Quality Objectives are:
      1. Concise and guiding gap analysis and road map.
      2. Validated Undergraduate program structure.
      3. Course and module content development.
      4. ICT and VR content development.
      5. Academic course offering procedure.
      6. Professional lifelong learning training.
      7. Academic and program infrastructure establishment.
      8. Dissemination and exploitation
      9. Project management
  3. Milestones:
    Milestones Deliverables
    Preparation 1. Gap Analysis

    WP1: Literature survey and Gap Analysis

    1.3. Gap analysis survey.

    1.4. Role of the architect survey.

    Development 2. Developing the 5-year program structure

    WP1: Literature survey and Gap Analysis

    1.1. Architecture programs survey

    WP2: Development of Program Structure

    2.3. Integration Workshop Alex

    WP3: Development of Program Pedagogy

    3. Pedagogy reports

    Accreditation 3. Approval of 5-year program

    WP14 EG accreditation

    2.1. Course Description of all courses in the program.

    All-partners Kassel meeting

    Implementation 4. Implementation of 5-year program

    WP13 ToT

    WP15 Implementation

    Implementation 5. Implementation of Life-long Learning training

    WP11: ICT and Virtual Reality support in Architectural Education

    WP15: Implementation

    Dissemination 6. Dissemination and exploitation

    WP14: towards EU accreditation

    WP 17: Dissemination

    WP 18: Sustainability

  4. Quality Management Approach

    The quality management approach is about to ensure that all personnel in the project "does the right things, right, the first time". Thus, avoiding misunderstandings of what to produce and how, resulting in productivity losses, quality losses and schedule delays.

    This is going to be achieved by

    • Early identification and reviews of all quality-impacting documents.
    • Reviews of all quality-impacting documents.
    • Using the well-defined and anchored quality standards and procedures already in use for each work package.
    • Using Customer Satisfaction as a Quality Control tool in case quality standards and procedures are missing and/or there are no documented processes/processes procedures do not exist in any form.
  5. Quality Control

    The Quality Control in the project focuses on the deliverables of the project and monitors them in order to verify they are complete, correct, and of acceptable quality.

    1. Project deliverables
    2. A list of project deliverables [2] is maintained by the project management, covering:

      • ID (WPx.x)
      • Name
      • Type (Report, Teaching material, Learning Material, Learning event, Dissemination event, Management…etc)
      • Description
      • Responsible
      • Planned delivery date
      • Applied Quality Standards (if any) for example: course specification templates, users manuals for ICT components, user’s instructions, course offering tools, feedback report templates…etc.
      • Acceptance Criteria covering criteria for completeness and correctness
      • Approved by
      • Approval date
      • Status
      • Comments

      Quality affecting documents such as this Quality Plan, project plans, work-plans, etc. shall be prepared and controlled in accordance with this quality plan and approved processes. These documents shall receive the required reviews and approvals; be uniquely identified, and their distribution must be formally established. Other essential policies, plans, procedures, decision, data and transactions produced by each work package are documented to an appropriate level of detail. Document reviews by subject matter experts; management and Quality Assurance are performed as appropriate and as specified in the referred Quality Standard.

    3. Deliverable Quality Standards
      • Document Management
      • The document standard to be used covers the mandatory templates to be used within the project and the procedures for document reviews.

      • Design-Based Research, DBR
      • DBR will be used to develop a methodology to evaluate any software platform for automatic recognition of academic achievements and its impact on students, which may be used for future improvement.

    4. Quality Control Activitie
      • In the project deliverables list, quality control activities are specified for each deliverable. The main quality control activity to determine whether the results conform to requirements is Inspection, which is to be carried out in different forms;

      • Examining
      • Document Review

        Methodically go through the document to be examined, to verify the quality of the document, validate the content, identify faults and shortcomings, and to disseminate knowledge of its content.

      • Solution Validation

        Aims to ensure a solution is of sufficient level of originality. Solution validations shall be part of the quality procedures in all WPs, but may also be called for by Project Management or be part of the project reviews.

      • Testing (during and after implementation)

        Testing (functional and non-functional) against defined acceptance criteria.

  6. Milestones:

    The focus of the Quality Assurance is on the processes used in the project. The Quality Assurance aims to ensure that the processes in the project and the WPs are used effectively to develop quality project deliverables.

    • Project Processes
      1. Gap analysis and validation.
      2. Course structure development (5-year plan) development and validation.
      3. Lifelong learning content development and validation.
      4. ICT and VR content development and correlation with academic content.
      5. Academic infrastructure development and validation.
      6. Course offering, implementation and validation.
      7. Dissemination process.
      8. Quality system implementation process
      9. Project management process.
    • Quality Assurance Activities

      Project Audits will be conducted in order to measure the application of the approved Project Plan and discover deviations that can be negative for the project.

      Planned:At the prescribed WP delivery time for all WPs

      Participants:Project Coordinator, Project Technical Coordinator and WP Leader

      Result:Recommended actions.

      Documentation:Project Audit Report

    • Project Review

      Project Reviews will be conducted in order to discover any deviations from and/or risks related to time, schedule, scope, and budget which can threaten the project and/or the outcome of the project.

      Planned:Every 6 months during all-partners meetings

      Participants:Project Coordinator, Project Technical Coordinator and WP Leaders

      Result:Recommended actions.

      Documentation:Project Review Report

    • Quality Audit

      Quality Audits will be conducted in order to measure the application of the approved Quality Plan and discover deviations that can be negative for the project and/or the outcome of the project.

      Planned:At the end of every Milestone

      Participants:Project Technical Coordinator, External Expert and WP Leaders

      Result:Recommended actions.

      Documentation:Project Audit Report

    • Review

      A Review may be called for by anyone in the project in order to verify that a process or activity is sufficient for its purpose and is applied and followed.

      Participants:Work Package Leaders

      Result:Recommended actions.

      Documentation:Review Report

  7. Roles and responsibilities
    • Project Coordinator

      The project coordinator is responsible for all administrative activities and deliverables related to the project implementation and is responsible to assure compliance with the time frame and expenditures compliance with granting rules.

    • Project Technical Coordinator

      The role of Quality Technical Coordinator reports to the Project Manager and aims to ensure that the deliverables of the project are fit for purpose, is consistent and meets both external and internal requirements. The Quality Technical Coordinator conducts quality assurance activities like audits and reviews to ensure that processes and procedures in the project are sufficient for their purpose and are applied and followed. The role includes responsibility for:

      • Devise and establish the project's quality procedures, standards and specifications.
      • Review project requirements and makes sure they are met.
      • Compile, assess and set standards for quality.
      • Establish and maintain control and documentation procedures.
      • Monitor performance by gathering relevant data and produce quality reports.
      • Make suggestions for changes and improvements and how to implement them.
      • Manage reported deviations from the Quality Plan, either by ensuring that the Quality Plan is followed, or through a Change Request adapting the Quality Plan to better reflect the reality of the project.
    • Work Package Leaders

      The Work Package Leader participates in the work to together with the WP partners to compile and customize Quality Objectives and Standards for the Work Package, ensure compliance with those standards, and to report deviations and needs for changes to the Project Technical Coordinator.

    • WP Partner

      Although the Project Technical Coordinator is responsible for Quality Management in the project, all project members are responsible to follow the Quality Plan and report directly to Work Package Leader when one considers that the quality plan deviates from reality, or that it is not followed.

  8. Reporting
    • WP partners to WP Leaders
    • WP Leaders to Project Technical Coordinator
    • External Expert to Project Technical Coordinator and Project Coordinator
    • Project Technical Coordinator & Project Coordinator to EACEA