Team Charter

Document Change Control

Release No	Release Date	Issued By	Version Comment	ClickUp Version Time
1.0	23/1/2025	Ahmed Shehata	Initial Version	Mar 02 11:50 am
2.0	30/9/2025	Ahmed Khafagy	Updating Tailoring Discision Section	Nov 24 3:26 pm

List Of Approvers

Name	Title	Approved Release No
Tarek Ramadan	Software Engineering Director	2.0

1. Team Overview

Team Name: Weqaa Eservices
Date: 17/8/2025
Product Owner: ________Islam Ramadan__________________
Scrum Master: ________Ahmed Essam___________________
Team Lead: ___________Mustafa Othman________________

2. Team Roles & Responsibilities

Team Member’s Name	Role	Responsibilities
Mustafa Othman	Dev TL	Assigns tasks to the team based on skills and capacity. Tracks daily progress and ensures the team stays on track. Helps solve technical or coordination issues. Works closely with the PO to clarify requirements for the team.
Dania	Developer	Implements assigned tasks according to sprint goals. Participates in daily stand-ups and shares progress or blockers. Writes clean, testable, and maintainable code. Collaborates with the QC to fix bugs and improve product quality.
Mahmoud Shawky	Developer	Implements assigned tasks according to sprint goals. Participates in daily stand-ups and shares progress or blockers. Writes clean, testable, and maintainable code. Collaborates with the QC to fix bugs and improve product quality.
Yomna Hassan	QC	Tests completed work to ensure it meets requirements. Writes and executes manual or automated test cases. Reports bugs and follows up until they’re fixed. Helps improve user experience and product quality.
Abdelrahman Mohamed	QC	Tests completed work to ensure it meets requirements. Writes and executes manual or automated test cases. Reports bugs and follows up until they’re fixed. Helps improve user experience and product quality.
Ahmed Sayed	PO	Owns and prioritizes the product backlog. Clearly explains requirements to the team and answers questions. Ensures each sprint delivers real value to the customer. Reviews completed features and verifies they meet expectations.
Islam Ramadan	PO	Owns and prioritizes the product backlog. Clearly explains requirements to the team and answers questions. Ensures each sprint delivers real value to the customer. Reviews completed features and verifies they meet expectations.
Ahmed Essam	SM	Facilitates all Scrum ceremonies (Daily Standup, Sprint Planning, Review, Retrospective). Removes any blockers that slow down the team. Supports the team in following Agile principles and Scrum practices. Coaches the team to become self-organized and high-performing. Acts as a bridge between the team and external stakeholders (without disturbing the team focus). Protects the team from unnecessary interruptions.
Ahmed Kadry	Developer	Implements assigned tasks according to sprint goals. Participates in daily stand-ups and shares progress or blockers. Writes clean, testable, and maintainable code. Collaborates with the QC to fix bugs and improve product quality.
Abdelrahman Shawqy	Developer	Implements assigned tasks according to sprint goals. Participates in daily stand-ups and shares progress or blockers. Writes clean, testable, and maintainable code. Collaborates with the QC to fix bugs and improve product quality.

3. Operating Model

Sprint Length: __2_ weeks
Ceremonies:

Meeting Type	Meeting Day	Frequency	Duration
Release Planning	Sunday		8h
Sprint Planning	Monday	Bi-Weekly	4h
Sprint Review	Sunday	Bi-Weekly	30m
Retrospective	Sunday	Bi-Weekly	1h
Daily Standup	Every working day	Daily	15m

Definition of Done:
- The project is following the Organization DOD

Please refer to EjadTech PAL > EjadTech_QMS_Implementation > EjadTech Organization Definition of Done

4. Working Agreements

Start/end meetings on time
Escalate blockers within 24 hrs.
Regular retrospective action items tracked

5. Escalation Matrix & Levels

Level	Description	Escalates To	Response Time
L0	Internal Team Issue	Scrum Master	Same Day
L1	Product / Scope Conflict	Product Owner	1 Working Day
L2	Process / Dependency Blocker	Software Engineering Director	1–2 Days
L3	Organizational / Strategic Risk	EPG	≤ 3 Days

6. Communication Tools

All outputs should be written on email or Click Up for reference.

7. Delegations

In case of the absence of scrum master

Required Follow-up	Assigned Team Member
Holding the Standup	Mustafa Othman
List actions of retrospectives	Mustafa Othman
Retrospectives action execution	Mustafa Othman
Manage meeting times	Mustafa Othman

Trainings

The Team doesn't need any training plans currently

8. Tailoring Decisions