6 Requirements Elicitation Composites
6需求捕獲的階段組成
Onsite Execution
現(xiàn)場(chǎng)執(zhí)行（下）
Challenges Guidelines
挑戰(zhàn) 指導(dǎo)
Requirements Conflict
需求沖突
1、 Business objective not clear to all
2、 User groups not in sync
3、 Gaps in requirements taken as assumptions leading to conflicts
4、 Incorrect groups targeted for requirements
5、 User group key person not identified for resolutions 1、 Include all stake holders in the onsite kick-off meeting and explain the business objective of the exercise to the group
2、 Document business objectives and circulate to all stakeholders after validating it with top management
3、 Conduct conflict resolution meetings and play the role of arbitrator explaining pros& cons
4、 Highlight all open issues and assumptions in the requirements document
5、 Perform stakeholder analysis and confirm with them your understanding of their responsibilities with current system
6、 Define escalation criterion and use appropriately
7、 Identify one point contacts from IT & business teams
1、 并非所有人都清楚商業(yè)目標(biāo)
2、 用戶組不同步
3、 已取得的需求與期望要求之間的差距導(dǎo)致沖突
4、捕獲需求的目標(biāo)用戶組不正確
5、 用戶組的關(guān)鍵領(lǐng)導(dǎo)人無法解決爭(zhēng)議 1、 在現(xiàn)場(chǎng)啟動(dòng)會(huì)議上對(duì)所有的風(fēng)險(xiǎn)承擔(dān)人解釋商業(yè)目標(biāo)
2、 與最高管理層確認(rèn)商業(yè)目標(biāo)后，將商業(yè)目標(biāo)寫成文檔并傳遞給所有的風(fēng)險(xiǎn)承擔(dān)人
3、 召開沖突解決會(huì)議并充當(dāng)中間人角色，解釋沖突兩方面的觀點(diǎn)
4、 在需求文檔中，重點(diǎn)標(biāo)示已有問題和假設(shè)
5、 扮演風(fēng)險(xiǎn)承擔(dān)人的角色，讓他們確認(rèn)你理解他們?cè)谀壳跋到y(tǒng)中的責(zé)任
6、 詳細(xì)說明增加了的業(yè)務(wù)規(guī)則并保證能正確使用
7、 確定IT工作和商業(yè)團(tuán)隊(duì)的結(jié)合點(diǎn)
Stakeholder Identification
風(fēng)險(xiǎn)承擔(dān)人識(shí)別
1、 Inadequate framework for stakeholder analysis
2、 Lack of awareness of client structure 1、 Use standard templates and framework for stakeholder identification
2、 Team shall go through the proposal thoroughly and identify anchors
3、 Request BM/AM to conduct a team orientation session before onsite start
4、 Kick-off meeting with client to incl