Lead with team scope
Put your current Scrum Master title, product or delivery setting, and number of teams near the top of the experience section. Show whether you supported software, platform, or another product group so readers can place your work quickly. Avoid describing yourself as a project manager unless that was also your formal responsibility; Scrum Master work is centered on team effectiveness and Scrum practice.
Connect practices to outcomes
Use bullets that pair the action with a team or delivery measure: carryover work, blocked time, release changes, or completion of planned work. Explain the period and scope when you can, and keep the number modest and defensible. Avoid claiming that a Scrum event alone caused a business result; describe the collaboration or change that contributed to it.
List credentials precisely
Write Certified ScrumMaster (CSM) with Scrum Alliance as the issuer, or Professional Scrum Master I (PSM I) with Scrum.org. Include credentials you currently hold and check renewal status where the issuer requires it. Do not treat course attendance as certification, and avoid listing credential IDs or dates unless an employer requests them or they clarify current status.
Name your delivery tools
Include tools such as Jira or Confluence only when you used them, and say what you did with them: maintained a backlog, tracked sprint work, or recorded team decisions. If the job ad names another tool, use its wording when accurate. Leave out generic office software and long tool inventories that do not show how you supported a team.