【IT168 技术文章】

    6 Requirements Elicitation Composites

    6需求捕获的阶段组成

    Onsite Best Practices

    现场非常好的实践

    Plan for two kick -off meetings: first one with top management and second involving all the stakeholders from both sides

    Create project team’s profile book to be shared in first onsite kick-off meeting

    Conduct internal review of MOM before circulating to attendees

    Use recorders for meeting discussion recording. This gives more time to the team for actively participating in the discussion as well as creates a professionalism impression

    Pre-decide the seating plan so as to seat customer and ABC team members at alternate places. Reach the meeting room 5-10 minutes in advance and occupy seats accordingly. This ensures proper mixing, avoids cartels and helps in listening to low-volume users.

    Brainstorm all known cross-cultural issues and prepare appropriate guidelines

    Involve business experts from customer’s team and create business process workflows during domain appreciation phase

    Conduct a onsite wrap-up meeting to thank everyone for assistance and time, handover requirements book, sharing future plan, roles and responsibilities, Offsite model, etc.

    Conduct user activity study for detailed understanding & definition of the performance requirements. Spending a day with the users in their work environment and observing the pattern of their activities will give lot of inputs about workload modeling, user response time, system bottlenecks, system load Vs. time pattern & system response time requirements.

    计划两次现场启动会议：第一次与高层管理人员，第二次与双方所有风险承担人

    在第一次现场启动会议上介绍项目组的概要情况

    会议纪要在交给与会者传阅前，要通过内部品审

    使用录音机记录讨论会议的情况。这样团队就有更多的时间积极参与讨论，同时也显得更专业

    预先确定座位，使项目组核心成员和客户间隔而座。提前到达会议室5到 10分钟，依次入座。这种排座方式建立了融合的氛围，避免象谈判对手似的对立，也有助于倾听嗓音低沉者的发言

    集体讨论所有已知的文化差异问题，并提议适当的指导原则

    从客户团队中邀请商务专家在问题域增值部分创建新的商务流程

    召开一个现场会议感谢大家花费时间提供帮助，移交需求文档，分享将来的计划，介绍产品中角色设定和职能划分等

    观察用户的活动，详细理解并识别性能需要，花一天时间与用户待在一起，观察他们的工作模式，得到工作量的模型，用户响应时间，系统瓶颈，系统负载与时间模式，以及系统响应时间的需要