info@ejadtech.sa
966555861076
+

Team Charter


1. Team Overview

  • Team Name: _____________________Compliance management________________________
  • Date: _________________________18/5/2025________________________
  • Product Owner: ________________Ahmed lotfy_________________________
  • Scrum Master: _____________Ahmed Essam____________________________
  • Team Lead: _________________Mahmoud Elbadry________________________

 

2. Team Roles & Responsibilities

Team Member’s NameRoleResponsibilities
 Ahmed lotfy

 

  •  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 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.

 

 Mahmoud Elbadry 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.

 

Ahmed YousefDeveloper
  • 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.

 

MoatazQC
  • 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.

 

3. Operating Model

  • Sprint Length: ___ weeks
  • Ceremonies:
Meeting TypeMeeting DayFrequencyDuration
Release Planning Sunday  1 month  8h
Sprint PlanningSunday   2 weeks 2-4h
Sprint ReviewSunday   2 weeks 1h
RetrospectiveSunday  2 weeks 1h 
Daily StandupDaily Daily 15m 

 

4. Working Agreements

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

 

5. Escalation Matrix & Levels

LevelDescriptionEscalates ToResponse Time
L0Internal Team IssueScrum MasterSame Day
L1Product / Scope ConflictProduct Owner1 Working Day
L2Process / Dependency BlockerSoftware Engineering Director1–2 Days
L3Organizational / Strategic RiskEPG≤ 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-upAssigned Team Member
Holding the Standup  Mahmoud Elbadry
List actions of retrospectives Mahmoud Elbadry 
Retrospectives action execution Mahmoud Elbadry 
Manage meeting times Mahmoud Elbadry