The correct answer is B - Discuss the issue with the team in the daily stand-up meetings. Agile emphasizes transparency, collaboration, and self-organization. The daily stand-up is an appropriate forum to raise and discuss workload distribution so the team can adjust and support each other.
From the PMI Agile Practice Guide:
"Daily stand-ups are a tool for fostering open communication, uncovering impediments, and adjusting the plan for the day. It enables the team to help each other balance workloads and remove bottlenecks." (PMI Agile Practice Guide, Section 5.2 - Daily Stand-Ups) Mike Griffiths explains:
"Team members should use stand-ups to discuss challenges. If someone is overloaded, the team can identify ways to redistribute work to maintain balance and avoid burnout." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 4 - Team Performance) Incorrect options:
* A escalates the issue unnecessarily and bypasses team self-management.
* C is too narrow and private for a team-based issue.
* D adds administrative burden without solving the underlying problem.

In a newly formed team, especially in a regulated environment like pharmaceuticals, guiding the team to collaborate effectively and share knowledge is essential. As the team lacks subject matter expertise, fostering an environment of continuous learning and collaboration will help them quickly build knowledge and improve their performance.
It is crucial to organize a meeting to clarify roles and responsibilities. This ensures everyone understands their individual contributions and how they relate to the team's goals. Clear role definitions are particularly important in a cross-functional team to avoid confusion and ensure smooth collaboration.

Before the workshop, the team members should read and identify relevant user stories from the product backlog that directly contribute to the goal of developing the feature for receiving and resolving customer complaints. This ensures that the stories being worked on are well-understood and aligned with the release goal.
The team should also consider the possible risks associated with each selected user story, such as technical challenges or dependencies. Additionally, they should evaluate the value each story adds to the final user (customer), ensuring that the team focuses on delivering maximum value in the release.

The goal of each iteration in Agile is to deliver working software frequently, typically at the end of each iteration. This allows the team to gather feedback early and make improvements quickly. The emphasis is on delivering usable software that provides value to the customer, rather than just completing tasks or preparing timelines. This approach aligns with the Agile principle of delivering working software frequently to ensure continuous progress and customer satisfaction.

In Agile, transparency and communication within the team are key. The team member should log the concern into the risk register to formally track the issue and share it with the team at the next standup. This allows the entire team to discuss and assess the situation collaboratively, ensuring that the concern is addressed and managed collectively. This approach aligns with the self-organizing nature of Agile teams, where team members are responsible for working together to find solutions.