Konubinix' opinionated web of thoughts

Scrum Team

Fleeting

Less than 10 persons.

It is said that the team is cross-functional1, but nothing says that each member of the team should be cross functional perselves. To the best of my understanding, it does not contradict having specialized members, like a frontend guy, a backend guy etc.

The team is self-managing2. That includes the product owner in the self-managing decisions. They make use of some tools to improve their predictability, like the velocity, but it remains their call.

The team embodies the values of scrum and commits and focuses on creating increments useful for the stakeholders sprint after sprint3.

The scrum team is committed to deliver the unique sprint goal. It focuses on the sprint goal and the product goal. Shows some transparency via the scrum artifacts and makes use of the scrum events to inspection its progress towards the goals at regular interval and has the courage to adaptation when things diverge.

The team is not committed to the stakeholders, yet its transparency and openness allow the stakeholders to have an impact on its commitments, mostly during the sprint review. After all, the sprints are made to increase their value.

The team define the definition of done of the increments that will produce value during the sprint. They share the same definition of done with other teams when they collaborate.

All the work done by the team initially comes from the product backlog.

only one scrum master

  • External reference:

    The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization

    — https://scrumguides.org/scrum-guide.html

The Scrum Master is accountable for the Scrum Team’s effectiveness. They do this by enabling the Scrum Team to improve its practices, within the Scrum framework

— https://scrumguides.org/scrum-guide.html

Scrum Masters are true leaders who serve the Scrum Team and the larger organization

— https://scrumguides.org/scrum-guide.html

only one product owner

Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team

— https://scrumguides.org/scrum-guide.html

Product Owner is also accountable for effective Product Backlog management, which includes:

— https://scrumguides.org/scrum-guide.html

The Product Owner may do the above work or may delegate the responsibility to others. Regardless, the Product Owner remains accountable.

— https://scrumguides.org/scrum-guide.html

These decisions are visible in the content and ordering of the Product Backlog, and through the inspectable Increment at the Sprint Review

— https://scrumguides.org/scrum-guide.html

Those wanting to change the Product Backlog can do so by trying to convince the Product Owner.

— https://scrumguides.org/scrum-guide.html

The product owner has nothing to do with the sprint backlog. The developers do.4

product owner does not define the sprint goal the whole scrum team does

During the sprint planning.

whole Scrum Team then collaborates to define a Sprint Goal that communicates why the Sprint is valuable to stakeholders

— https://scrumguides.org/scrum-guide.html

product Owner is one person, not a committee

The Product Owner is one person, not a committee

— https://scrumguides.org/scrum-guide.html

developers

Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.

— https://scrumguides.org/scrum-guide.html

Developers are always accountable for:

  • Creating a plan for the Sprint, the Sprint Backlog;
  • Instilling quality by adhering to a Definition of Done;
  • Adapting their plan each day toward the Sprint Goal; and,
  • Holding each other accountable as professionals.

— https://scrumguides.org/scrum-guide.html

It is to be noted that developers create the sprint backlog, not the product owner.

Notes linking here

  1. Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint

    — https://scrumguides.org/scrum-guide.html

    people who collectively have all the skills and expertise to do the work and share or acquire such skills as needed.

    — https://scrumguides.org/scrum-guide.html

     ↩︎

  2. also self-managing, meaning they internally decide who does what, when, and how.

    — https://scrumguides.org/scrum-guide.html

     ↩︎

  3. The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint.

    — https://scrumguides.org/scrum-guide.html

     ↩︎

  4. The Sprint Backlog is a plan by and for the Developers

    — https://scrumguides.org/scrum-guide.html

     ↩︎