Scrum Fundamentals
Stable teams, are happier and perform better
Cross-functional teams / Swarm on Tickets
Predictability:
Team Norms
DOR / DOD
Flow-efficiency vs. resource-efficiency
Team Name / Team Identity
Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside of the team.
the Scrum Team, who is accountable for delivering useful, valuable increments, has the opportunity to do what it takes to deliver that value.
"Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done."
Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.
The best architectures, requirements, and designs
emerge from self-organizing teams.
Identity: Team Name
Team Norms
Definition of Ready
Definition of Done
Servant Leadership
Escalating Risks
Accountability
Team comes together. Usually a time of great positivity.
Getting used to each other, establishing roles. This is a point where the team is most likely to have conflict.
Team members begin to work together effectively. Trust develops. More cohesion as people find ways to work together, despite their differences.
Team members are confident and motivated. Understand each other's strengths and weaknesses. The team is doing its best work. Not every team makes it to this stage.
Project ends, teams disband
Stable teams are usually higher performing than new teams or changing teams.
Teams are closest to the information
Teams make the decisions, not team leaders
Team members come up with their own team name
Nothing to do with the project or initiative
Not created by management or a lead
Team members come up with their own team name
Nothing to do with the project or initiative
Not created by management or a lead