遇過 user 阿頭畀 requirements,但佢唔係用果個,於是造出嚟被 end user 屌死
咁係咪直接問 end user 就得呢?好多 user requirements 其實真係user 自己的 requirements,只因應佢自己 work flow 先存在,唔係 business requirements 嚟,照住造就會搞到個 app 古古怪怪,一堆唔知為乜嘅功能,end user turnover 又高,之冇人答到你為乜要
所以 BA 唔係 bridge between user and dev 就夠,仲要識 分真 requirements
另一方面,dev 有啲野可能唔係為 functional requirements 而造,可能為 performance,為 scalability,為compatibility,甚至為執前人啲蘇州屎,依啲又唔可以樣樣同 user 講,所以 BA 要識分邊啲講得唔講得
依個世界冇話冇邊個 post 會死,唔係話一定要靠 BA,但每個人時間有限,你 tech 好 deep 自然唔夠時間去 wide(服侍user 啲真假 requirements),咁咪要靠啲wide 人即 BA 去做囉