📝 customers ask to fix Requirements when will Deploy! BA do?😱

The problem of the BA and IT team. When you experience "Requirements," don't panic! Try 4 Step to cope with the pro.

✅ 1. Stop & Listen (Calm down and listen)

Don't immediately refuse (Say No) to listen to the "business reasons" why he needs to solve it now. Sometimes it can be critically urgent that we really need to solve.

✅ 2.Impact Analysis (Impact Analysis)

Inform the impact to the Stakeholder. Don't just say "can't do it," but say:

⏰ Timeline: How many days will Deploy have to be postponed?

Budget 💰: Is there an extra cost or resource required?

🛠️ Quality: Is there any point of increased risk of collapse?

✅ 3.The Trade-off (Offer Win-Win Alternative)

A good BA has to offer a solution. Let's talk about it:

"If you want to take this feature quickly, can we put the B feature on the front Sprint instead?"

Alternative negotiation reduces conflict better than just rejection.

✅ 4.Document Everything (Record of Evidence)

Most importantly! Once agreed, don't forget to always make a Change Request (CR) or Memorandum through Email / Jira to prevent future "Unrecognizable" or "Unsaid" problems.

💬 Who has ever encountered a peak case like this? How does the team handle it? Comment share experience!

# BA # BusinessAnalyst # IT # Working age # Work life review# Office # SoftSkill # Office man # Developer