Mark is the business analyst for his organization. He is working with the solution development team and he believes that the team does not want to implement a certain portion of the requirements. The

The team is dismissing the past project comparison, not using it to justify changed prioritization - there is no evidence they are referencing prior work to rank requirements.

The team is claiming the requirements are uniquely difficult and dismissing the comparison to a past similar project, which are tactics to exaggerate complexity and manipulate the prioritization of those requirements downward. This is a recognized stakeholder behavior in business analysis where perceived implementation burden is inflated to deprioritize unwanted scope. The BA's ability to reference a comparable past project weakens the team's argument, revealing the complexity claims are likely overstated.

The team has not formally proposed removing the requirements from scope - their actions target perceived difficulty to reduce priority, not to eliminate scope.

The team is not asking the BA to escalate concerns to the customer - they are expressing resistance to the BA directly as a way to avoid doing the work.