To amend the draft of TISB Standard Operating Procedures

[Ac3ranJr1]

Link to Documents Folder: https://thetaedgebhd.sharepoint.com/:f:/s/ThetaInnovation/EvsWA3-axs5Et9uat42oI-kBQoG0lApApmi00eUjcu1BoQ?e=uravgV

[nichleegc6929]

Team Inno realised that there is no "Handover form" in reference to the Proposed Flowchart (saved under Theta Inno > Documents > 1003 Operations 2024 > 09 Process and Governance Form. https://thetaedgebhd.sharepoint.com/:p:/s/ThetaInnovation/EYR3YCjmkPhMhwOZgBQ92xkBY5JsYvV4HkzjwfvoKzlG6w?e=Zdhyg6

The handover form is meant to transfer Inno's responsibilities for a product to another (i.e., the operations and support team). It typically includes info that ensures smooth transition and provides the receiving team with the necessary resources to manage the product effectively.

Key components should be:

1. Project Overview

• Brief description of the application.
• Purpose and key features.

2. Development Details

• Technologies and frameworks used.
• Source code repository information.
• Development environment setup instructions.

3. Documentation

• Links to user manuals, technical documentation, and design documents.
• API documentation (if applicable).

4. Current Status

• Version of the application.
• List of completed features and any outstanding issues or bugs.

5. Testing Information

• Summary of testing performed (unit tests, integration tests).
• Known issues and workarounds.

6. Deployment Instructions

• Steps for deploying the application to production.
• Rollback procedures in case of deployment issues.

7. Contacts

• List of key contacts within the development team for questions or support.
• Escalation procedures for critical issues.

8.Service Level Agreement (SLA)

• It’s advisable to include an SLA in the handover form, which outlines the expected levels of service after the handover, including:

• Response times for support requests.

• Availability and uptime requirements.

• Maintenance schedules and procedures.

• This ensures clarity on the operational responsibilities and sets expectations for the support team.

9. Sign-off Section

• Space for signatures from both the development team and the operations/support team to confirm the handover.

[nichleegc6929]

Hi there @Ac3ranJr1 & @nanahamzah, we'll need your assistance in drafting up this new "Handover form" before the 26th September 2024, prior to our internal briefing to both SPU and Sham Sol.