Team Charter

Document Change Control

Release No	Release Date	Issued By	Version Comment	ClickUp Version Time
1.0
2.0
3.0

List Of Approvers

Name	Title	Approved Release No
Tarek Ramadan	Software Engineering Director

Team Charter

1. Team Overview

Team Name: ______________EA Team___________________
Date: _________________________________________________
Product Owner: __________Mohsen Waheed______________
Scrum Master: ____________Ahmed Essam_______________
Team Lead: ____________Mahmoud El Badri_______________

2. Team Roles & Responsibilities

Team Member’s Name	Role	Responsibilities
Mahmoud El badri	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.
Mohsen Waheed	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 Risk	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.
Ahmed yousif	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.
Moataz Mustafa	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 Esaam	Scrum Master	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.

3. Operating Model

Sprint Length: ___ weeks
Ceremonies:

Meeting Type	Meeting Day	Frequency	Duration
Release Planning	Sunday	2 month	8h
Sprint Planning	Monday	2 weak	2-4h
Sprint Review	Sunday	2 weak	1 Hr.
Retrospective	Sunday	2 weak	1 Hr.
Daily Standup	Daily	Daily	15 Min.

Definition of Done:
- - We are following the Organization DoD :

https://app.clickup.com/4669532/docs/4eg2w-106255/4eg2w-33435

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	Mahmoud El Badri
List actions of retrospectives	Mahmoud El Badri
Retrospectives action execution	Mahmoud El Badri
Manage meeting times	Mahmoud El Badri

Trainings

The Team doesn't need any training plans currently

8. Tailoring Decisions

No.

Standard Process

Tailoring Decisions

1

The Team should create a project Charter for the Project

Since this is a product, the team could not create a project charter