The Scrum framework : Values

The Scrum framework consists of Scrum Teams and their associated accountabilities, artifacts, events and rules as defined in the Scrum Guide.

The 5 Scrum values are :

• Courage
• Focus
• Commitment
• Respect
• Openness

Courage

• There are times when doing the correct thing to serve the best values and benefits for our clients are not the easiest :
  • In such moments, Scrum Master, Product Owner, and the Developers should remember their duty and obligation.
    • That’s to build the best possible products and services in their particular business and information technology domain.
    • To be better than mediocre, a Scrum Team should sooner or later face difficult decisions that won’t make everyone happy in their particular ecosystem of Stakeholders.
    • To deal with this, all members of the Scrum Team should remember what they learned with the Scrum framework.
  • They should remember to be courageous, and they should master to decide and act courageously.

Focus

• With the Scrum framework, when you hear the value focus, you should be thinking about two things :
  • Identification of correct work :
    • What tasks are necessary to deliver the goals of my Sprint?
    • What are essential to developing the best software products and services for my clients so that they will be pleased with my work?
  • Prioritization :
    • What tasks should I be working on next?
    • Each moment in time, there is one critical question that the entire Scrum Team, including Scrum Master and Product Owner, must be answering.
    • This question is:
      • “What are the most important things we should be doing at the moment to fulfill reasons of why an employer hired us in the first place?”
    • Scrum framework has several built-in events (rituals) to ensure the reasonable prioritization of Product Backlog Items and tasks.
      • According to the Scrum process, the prioritization of Product Backlog Items and their associated tasks should have a continuous priority.
      • So we make sure that the Scrum Team works on the right things in the correct order.
      • Some of the built-in scrum ceremonies (Scrum Events) to prioritize our work and adjust our focus are:
        • Product Backlog Refinement:
          • Product Backlog Refinement solely focuses on prioritization for Product Backlog to prepare it before the upcoming Sprint Planning.
        • Sprint Planning :
          • These meetings help us see the dependencies and correct order of work to deliver our Product backlog Items.
        • Daily Scrum :
          • Daily Scrum (Daily Stand-Up) supports us to set the tone of an upcoming workday.
          • We must direct our focus on where it’s most required.
        • Sprint Review :
          • Sprint Review indirectly shows us where the emphasis of the Scrum Team must be channeling to have more successful reviews in the future.
        • Sprint Retrospective :
          • Sprint Retrospective support the scrum team to prioritize what aspects of their engineering process must be first improved.
    • Having read all these, it must be evident how essential prioritization and focus for the Scrum framework are.

Commitment

• Without the commitment of Scrum Master, Product Owner, and the Developers, there is no possibility to deliver outstanding results with software.
  • In the world of the scrum software development process, most people translate the commitment value as the agreement and confinement of goals of given sprint deliverables.
  • Although this entirely makes sense, that understanding is not flawless.
  • Whenever you hear the word “commitment” within the context of Scrum Values; what you should remember is the word: “obsession”.
  • To be successful in software engineering and, in life and business, you should become obsessed with your goals.
  • So in the context of the scrum process, you should become obsessed with creating marvelous software for your clients to solve their problems.
• Why are commitment and the associated obsession with Scrum goals so important?
  • Because without the obsession with the team’s mission to build and deliver astonishing software, each time the Scrum Team encounters a non-trivial impediment, your work will slow down and stall.
  • Then the Scrum Master and the Scrum Team will start creating explanations to justify and legitimize for Product Owner why they’re unable to deliver Sprint goals.
  • Excuses should have no more room in your team if your goal is to become a better than an average Scrum Team.
• Only with an enormously high level of dedication, it’s relatively more comfortable and fulfilling to solve the problems of our clients and help and build value for them with software.

Respect

• Regardless of their age, gender, race, belief, experience, competence, opinions, and work performance, every member of a Scrum Team must respect and count on each other.
  • This respect is not only confined within the boundary of the Scrum Team.
  • Moreover, every internal or external IT and business Stakeholder who interacts with the Scrum Team is utterly respected and welcomed by a Scrum Team.
  • Experienced team members must pay attention in order not to invalidate the willingness of the contribution from less experienced team members.
  • It’s particularly crucial to properly receive and answer opposite opinions that the majority of the group do not agree with.

Openness

• The scrum value “openness” is often one of the primary differentiators between an average and high-performer Scrum Team.
  • It would help if you resembled the openness capability of a Scrum Team to the vast ability of a collection of openminded individuals.
  • They’re creative, innovative, intellectual, honest, direct, and humble.
• In the scrum software engineering and delivery process, there is no inappropriate opinion, decision, and action.
  • The only condition is that they must be transparent, and they should aim to contribute to the joint mission of the Scrum Team.
  • It doesn’t mean that every decision and action must necessarily accelerate the outputs of the Scrum Team, and they should result in substantial success Product Backlog Items.
• Thanks to openness and courage values, the scrum software development group is not afraid of making mistakes.
  • They see their errors and less than optimal outcomes as vital chances to meaningfully improve their overall productivity and quality of work.

More informations for the Scrum PSD certification here.

Updated : 20/08/2021