Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Size

Medium

Budget Epic Name

CDP-178 Moodle 4.0

Jira Outcome

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Feature Lead

Nikola Bozhkov

  • Outcome Description:  

    • FOR WHO: Staff, students all stakeholders of DLE systems/platforms and integrations

    • WHAT: Providing support, maintenance, development and testing of the DLE platforms, in partnership with hosting partners, 3rd party product vendors across both product software, infrastructure and DEV/OPS implementations.

    • WHY (Business Value): Ensuring business continuity, security of service, scalability and performance for core systems

  • Dependencies

    • Catalyst IT, Internal product resources, specialist skill sets as required

  • Risks:

    • Lack of internal resource

  • Outcome Deliverables EPICs:

TI3

  • Load testing preparation (spike) - https://ucldata.atlassian.net/browse/CTP-2656

    • What: Vendor discussions and spike

    • Why: It is critical that we have robust solutions to measure and ensure that UCL systems are provisioned correctly and can respond to increases in load. We also require a solution that can be replicated and used to benchmark our solution and to measure against specific scenarios (eg assessment load).

    • Dependency: ? / Risk: ?

  • Load testing preparation (spike) - https://ucldata.atlassian.net/browse/CTP-2656

    • What: Vendor discussions and spike

    • Why: It is critical that we have robust solutions to measure and ensure that UCL systems are provisioned correctly and can respond to increases in load. We also require a solution that can be replicated and used to benchmark our solution and to measure against specific scenarios (eg assessment load).

    • Dependency: ? / Risk: ?

  • Load testing preparation (spike) - https://ucldata.atlassian.net/browse/CTP-2656

    • What: Vendor discussions and spike

    • Why: It is critical that we have robust solutions to measure and ensure that UCL systems are provisioned correctly and can respond to increases in load. We also require a solution that can be replicated and used to benchmark our solution and to measure against specific scenarios (eg assessment load).

    • Dependency: ? / Risk: ?

  • Load testing preparation (spike) - https://ucldata.atlassian.net/browse/CTP-2656

    • What: Vendor discussions and spike

    • Why: It is critical that we have robust solutions to measure and ensure that UCL systems are provisioned correctly and can respond to increases in load. We also require a solution that can be replicated and used to benchmark our solution and to measure against specific scenarios (eg assessment load).

    • Dependency: ? / Risk: ?

  • Load testing preparation (spike) - https://ucldata.atlassian.net/browse/CTP-2656

    • What: Vendor discussions and spike

    • Why: It is critical that we have robust solutions to measure and ensure that UCL systems are provisioned correctly and can respond to increases in load. We also require a solution that can be replicated and used to benchmark our solution and to measure against specific scenarios (eg assessment load).

    • Dependency: ? / Risk: ?

  • Preview Improvements for Moodle 4 - CTP-2021

    • What: ??

    • Why: In TI2, the Preview environment was implemented in AWS and pipeline migrated to Github Actions. We now need to keep improving this environment to support it's availability to demo Moodle 4.

    • Dependency: ? / Risk: ?

  • DLE Operations - CTP-392

    • What: FR, CIs, Moodle releases, Monthly Manual patching, Service Health Reviews - Schedule & docs, etc.

    • Why: Day-to-day operational support and monitoring are essential to maintain a complex system such as Moodle and ensure value for stakeholders.

    • Dependency: Catalyst/Vendor resource / Risk: The product requires an additional member of staff within this team area to support our services.

  • No labels