An organization has just hired you as a new Scrum Master to help them transition their teams from their current traditional process to Scrum. The teams are currently structured to specialize in a single function. This is also known as component teams where a team would only address a single layer (i.e. design, frontend, backend, database, testing, etc.). You’ve introduced the concept of cross-functional teams where all the skills needed to produce business functionality, from end to end, are inside of a single team.
What should you keep in mind when transitioning from siloed teams to cross-functional teams? (Choose two.)
- A: It is easier to compare the performance between cross-functional teams in order to identify to which teams to assign tasks and which teams need additional coaching.
- B: Newly formed teams will need time to stabilize before reaching their peak performance. During the initial stages of forming, performance will suffer and productivity may be low, although even then delivery of business value is still likely to increase.
- C: Without feature teams, you cannot do Scrum. Postpone Scrum adoption until the teams are reorganized in feature teams.
- D: People from the different layers and components will need time to become accustomed to working and delivering unified functionality together as one Scrum Team thus productivity may suffer.