Problem-Solving Scenario: The "FitTrack" Project Crisis

Background: You have been hired as an Agile Consultant to evaluate a software engineering department currently developing a new application called "FitTrack." The organization claims to use the Scrum framework, but the project is suffering from severe delays, poor morale, and lack of tangible output. After observing the team for a few weeks, you log the following field notes:

1. Team Composition: The main Scrum Team consists of 24 cross-functional members working on the same sprint backlog.

2. Feature Prioritization: The role of the Product Owner is handled by a "Steering Committee" of three executives. When the Developers need clarification on prioritizing a core user journey feature versus a secondary feature, they must submit a formal request and wait for the committee's bi-weekly meeting to get a decision.

3. Sprint Deliverables: Because the team felt overwhelmed by coding tasks, they decided to spend the last two Sprints entirely on writing comprehensive system architecture documentation instead of delivering the planned functional workout-logging feature. They argued this would save time later.

4. Stakeholder Interference: The Marketing Director frequently visits the Developers directly during the Sprint, asking them to "quickly add" small social sharing features to align with an upcoming marketing campaign. To keep the stakeholders happy, the Developers regularly accept these ad-hoc requests, resulting in the team repeatedly failing to meet their main Sprint Goal.

Questions: As the Agile Consultant, write a report addressing the following:

1. Identify the Issues: Based on Agile Principles and the Scrum Framework, identify the four specific anti-patterns (violations) occurring in this scenario.

2. Explain the Impact: Explain why each identified issue is detrimental to the project's success, referencing specific Agile principles or Scrum rules.

3. Propose Solutions: Provide a concrete, actionable solution to resolve each issue. Specify which Scrum Role (Product Owner, Scrum Master, or Developers) must take accountability for fixing it.