The previous chapter focused on the two new roles on a Scrum project—Scrum-
Master and product owner. But changes to a Scrum project’s team members go
beyond the introduction of two new roles. For example, the self-organizing nature
of a Scrum team eliminates the role of the technical team leader, individuals are
asked to look beyond their specialty and help the team in any way possible, emphasis
is shifted from writing about requirements to talking about them, and teams
are required to produce something tangible by the end of each sprint. Because
these changes alter the roles and relationships within the team and organization
they often contribute to some of the challenges organizations face when adopting
Scrum.
Chapter Contents
- Analysts
- Project Managers
- Why the Title Change?
- Architects
- The Non-Coding Architect
- Functional Managers
- The Leadership Role of the Functional Manager
- Personnel Responsibilities
- Programmers
- Database Administrators
- Testers
- User Experience Designers
- Three Common Themes
- Additional Reading