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 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.
All the work done by the team initially comes from the product backlog.
only one scrum master
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
Scrum Masters are true leaders who serve the Scrum Team and the larger organization
only one product owner
Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team
Product Owner is also accountable for effective Product Backlog management, which includes:
- Developing and explicitly communicating the Product Goal;
- Creating and clearly communicating Product Backlog items;
- Ordering Product Backlog items; and,
- Ensuring that the Product Backlog is transparent, visible and understood.
The Product Owner may do the above work or may delegate the responsibility to others. Regardless, the Product Owner remains accountable.
Those wanting to change the Product Backlog can do so by trying to convince the Product Owner.
product owner does not define the sprint goal the whole scrum team does
During the sprint planning.
product Owner is one person, not a committee
The Product Owner is one person, not a committee
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.
Notes linking here
- being committed towards the sprint goal does not necessarily mean always working towards it
- being committed vs spending all one’s time
- can the CTO and/or the CEO be stakeholders of scrum?
- commitment (scrum)
- courage (scrum)
- daily scrum
- definition of done
- doing scrum or pretending to do scrum?
- débat sémantique
- focus (scrum)
- gtd and scrum
- misconception about the daily meeting: the three questions fallacy
- métaphore salade vs pâtes
- product backlog
- product goal (scrum)
- product owner as a task tree
- product owner rethoric
- scrum artifacts
- scrum events
- scrum mum
- scrum team is cross-functional
- scrum team is self-managing
- sprint backlog
- sprint goal
- sprint plan to deliver increments to fulfil product backlog items
- sprint planning
- sprint review
- stakeholders (scrum)
- step by step journey to #NoEstimates
- syndrome du technical product owner
- test-driven development
- unit of work in scrum is the team, not the team member
- usage ordinaire du mot scrum
- what if the scrum team fulfills the sprint goal before the end of the sprint?
- what should I put into those scopes and access tokens claims? (blog)
Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint
people who collectively have all the skills and expertise to do the work and share or acquire such skills as needed.
also self-managing, meaning they internally decide who does what, when, and how.
The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint.