Scrum teams are cross functional. Every person on the team has skills and experience that they contribute, turning the requirements into the best possible increment possible for them. One never knows when an insight, a memory, a skill rarely used will come into play. That is the beauty of Scrum teams, the growing synergy of the unanticipated.
Many have trouble setting aside the labels that have confined their participation. Labels such as “business analyst” in no way limit someone from knowing the endless loops are bad. People previously known as “quality assurance” often can see that architecture will be untestable, hence not viable.
I was in a bar last week (don’t ask why) and saw someone similarly constrained.
An office building was going up across the street. It was nearly complete, and had beautiful brickwork throughout.
During its construction,, the construction workers stopped by the bar after work. They would share stories, discuss the odds for the Red Sox, and try to relieve some of their aches. One of the most vocal was a bricklayer, a duck from Nova Scotia. Apparently, his flock had left him behind six years previously. He had to find gainful employment, so he turned to an opening in brick laying and masonry field, starting as an apprentice and working his way up.
Today, though, the duck was pouring them down. He was despondent that the project was over, he was out of work, and winter was approaching. He turned to bartender, moaning of what was to come of him.
The bartender, knowing that there was a circus in town, told the duck to go to the circus and offer his services.
The duck rejoined, “Why would a circus want to hire a brick laying duck?”