Elicitation Techniques

BA approaches to cearly outline project goals and objectives in consultation with stakeholders. Identify success criteria and key performance indicators (KPIs). Conduct kick-off meetings with all stakeholders to align on project vision and scope. Establish communication channels and reporting structures. For, Stakeholder Analysis Use RACI (Responsible, Accountable, Consulted, Informed) matrix to clarify roles and responsibilities. Create an Influence/Interest Matrix to understand stakeholder influence and interest levels. Develop a stakeholder engagement plan outlining how and when to communicate with each stakeholder. Elicitation Techniques includes Interviews: Conduct interviews with key stakeholders to gather detailed requirements. Workshops:Organize requirement workshops with stakeholders to collaboratively gather and refine requirements. Surveys/Questionnaires: Distribute surveys to a broader group of farmers to gather additional insights. Document Analysis: Review existing documents related to farming needs and previous initiatives. Prototyping:Develop low-fidelity prototypes to gather feedback on UI/UX and functionality.Create a Business Requirements Document (BRD) detailing all high-level requirements. Develop Functional Requirements Document (FRD) and System Requirements Specification (SRS). Design Documents:Work with developers to create detailed design documents. Traceability Matrix:Maintain a requirements traceability matrix to ensure all requirements are addressed throughout the project lifecycle. Approval and Sign-Off Process Document Review: Circulate BRD, FRD, and SRS among stakeholders for review. Feedback Incorporation:Gather and incorporate feedback from stakeholders. Formal Sign-Off: Obtain formal sign-off from stakeholders on the finalized documents. Use e-signature tools or formal meetings to document approvals. Communication Plan Channels: Establish regular meetings (weekly/bi-weekly) for project updates. Use emails, project management tools (e.g., Jira, Trello), and instant messaging (e.g., Slack) for daily communications. Reports: Provide regular status reports and progress updates to stakeholders. Develop a communication matrix specifying what information will be communicated, to whom, and how often. Change Management Change Request Process: define a clear process for submitting and reviewing change requests. Use a Change Request Form to document all changes. Impact Analysis: Conduct impact analysis for each change request to assess implications on scope, time, cost, and quality. Approval: obtain approval from the change control board (CCB) before implementing changes. Documentation: Update all relevant project documents and the traceability matrix to reflect approved changes. Project Progress Monitoring Status Meetings:Conduct regular status meetings with the project team and stakeholders. Progress Reports:Generate and distribute progress reports highlighting completed tasks, ongoing activities, and any issues or risks. Performance Metrics:Track project performance using KPIs and milestones. User Acceptance Testing (UAT) and Project Closure UAT Preparation:Develop UAT plan and test scenarios based on requirements. Ensure stakeholders are prepared and available for UAT. Conduct UAT: Facilitate UAT sessions, document any issues or defects. Client Approval:Gather client feedback, ensure all issues are resolved. Obtain formal sign-off using the Client Project Acceptance Form. ELICITATION TECHNIQUES are: Brainstorming – It can be done in groups or individually. The ideas collected then can be reviewed / analysed and relevant included in the software. Most effective with group of 8-12 people. Document Analysis – Documentation about current system which can provide input for new system. Such document can include interface details, user manuals, and software vendor manuals. Reverse Engineering – In situations where very little or close to zero documentation is available reverse engineering is used. It is a technique that can extract implemented requirements from software code. Black Box - The system or product is studied without examining its internal structure White Box - The inner workings of system or product are studied Focus Groups – Is a means of elicit ideas and attitudes about specific products service or opportunity in an interactive group environment. It typically has 6 – 12 members. Homogeneous groups are those which has individuals with similar characteristics. Heterogenous groups are those which has diverse backgrounds, perspectives. Observations – Observing or shadowing users or even doing part of their job can provide information of existing process, inputs and outputs. Passive invisible in this approach BA observes the subject matter expert but does not ask questions. Active visible is the approach where BA observes the subject matter expert and can interact with them. Workshop – A structured way to capture requirements. A workshop may be used to scope, discover, define, prioritize and reach closure requirements. JAD – it is a technique an extended workshop. It involves collaboration of stakeholders and system analysts to identify needs or requirements in concentrated and focused effort. Interview – Process of asking structured questions to understand requirements or needs. Prototyping – Creating a model which resembles same as expected outcome Questionnaire – Questionnaire can be useful for obtaining limited system requirements details from users, stakeholders who have a minor input or are geographically remote.