6 Requirements Elicitation Composites
6需求捕获的阶段组成
Onsite Execution
现场执行（下）
Challenges Guidelines
挑战 指导
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、 并非所有人都清楚商业目标
2、 用户组不同步
3、 已取得的需求与期望要求之间的差距导致冲突
4、捕获需求的目标用户组不正确
5、 用户组的关键领导人无法解决争议 1、 在现场启动会议上对所有的风险承担人解释商业目标
2、 与最高管理层确认商业目标后，将商业目标写成文档并传递给所有的风险承担人
3、 召开冲突解决会议并充当中间人角色，解释冲突两方面的观点
4、 在需求文档中，重点标示已有问题和假设
5、 扮演风险承担人的角色，让他们确认你理解他们在目前系统中的责任
6、 详细说明增加了的业务规则并保证能正确使用
7、 确定IT工作和商业团队的结合点
Stakeholder Identification
风险承担人识别
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