Skip to content
ScrumMastered logo
  • Corporate clients
    • Private Agile & Scrum Training
    • Agile Consulting
    • Case Studies
  • Courses
    • Upcoming live public classes
    • Jira for Scrum Masters
    • Scrum Master (PSM I™) Exam Prep Certification Course
    • Fundamentals of Agile Course
  • Resources
    • Wiki
    • Start here
    • Freebies
    • The Agile Audit Podcast
    • Premium Downloads & Courses
  • Blog
  • About
  • Corporate clients
    • Private Agile & Scrum Training
    • Agile Consulting
    • Case Studies
  • Courses
    • Upcoming live public classes
    • Jira for Scrum Masters
    • Scrum Master (PSM I™) Exam Prep Certification Course
    • Fundamentals of Agile Course
  • Resources
    • Wiki
    • Start here
    • Freebies
    • The Agile Audit Podcast
    • Premium Downloads & Courses
  • Blog
  • About
Shop

Scrum Framework Explained

  • Scrum Overview
  • Sprint Events
    • Sprint Retrospective
    • Sprint Review
    • Daily Scrum
    • Sprint Planning
  • Scrum Accountabilities / Roles
    • Scrum Master
    • Developers
    • Product Owner
  • Scrum Artifacts & Commitments
    • Sprint Goal
    • Sprint Backlog
    • Product Goal
    • Product Backlog
    • Definition of Done
    • Increment
  • Scrum Values
    • Value: Courage
    • Value: Respect
    • Value: Openness
    • Value: Focus
    • Value: Commitment
  • Pillars of Empiricism
    • Pillar: Adaptation
    • Pillar: Inspection
    • Pillar: Transparency

Useful Models

  • Use Kano Model to prioritize features
  • Psychological safety
  • Team Overestimating Their Knowledge – The Dunning-Kruger Effect
  • Cognitive Bias in Business
  • Shu-Ha-Ri Maturity Model
  • Tuckman’s Stages of Group Development
View Categories
  • Home
  • wiki
  • Scrum Framework Explained
  • Scrum Values
  • Value: Respect

Value: Respect

< 1 min read

đź’ˇ Respect is often simplified to just regular polite respectful interactions we expect from everyone at work. But it goes further than that. Respect is also about considering how our actions and decisions may impact others: our team, our stakeholders, our customers, and the organization as a whole.

âś… Encouraged behaviors #

  • Listening to the Product Owner’s decisions about what’s more important.
  • Putting trust in team’s ability to manage their own work and deliver high-quality products.
  • Respecting team’s decisions even if disagreeing.
  • Considering every opinion, regardless of who it comes from, a manager or a junior team member.
  • Preparing for meetings to keep them within the timeboxes (respecting everyone’s time).
  • Following the rules of Scrum (respecting the framework).
  • Fixing issues in our product that may impact our users.

❌ Discouraged behavior #

  • Namecalling and personal attacks.
  • Changing priorities behind Product Owner’s back.
  • Pretending to agree with the team only to work in your own corner.
  • Mocking opinions and ideas of others or openly showing disinterest in them.
  • Micro-managing the team.
  • Wasting people’s time in meetings with long rants, questions that should have been answered outside of the meeting, unpreparedness, etc.
Was this helpful?
Share This Article :
  • X
  • LinkedIn
Updated on April 4, 2024
Value: CourageValue: Openness

Powered by BetterDocs

Table of Contents
  • âś… Encouraged behaviors
  • ❌ Discouraged behavior

Join 5000+ Agile practitioners around the world on their journey to building awesome teams.

ScrumMastered logo
Quick Links
  • Shop
  • Agile Consulting
  • Private Training
  • Scrum.org Classes
  • Blog
  • About & Contact
  • Terms & Conditions
  • Privacy Policy
Follow for More

All Rights Reserved by ScrumMastered © 2025