Requirements Analyst - Connectivity

RESPONSIBILITIES AND DUTIES Identify involved stakeholders by either getting the stakeholders list from the initial stakeholders or conducting a study to analyse all functions involved/affected by the project. Sometimes, a combination of both these techniques may also be used Gather requirements from key stakeholders by using requirement elicitation techniques like brainstorming, requirement workshops, focus groups, and others Validate requirements by cross-referencing them with other stakeholders and try to get their buy-in. It’s important to achieve a consensus against the requirements before actually start building the solution Analyse and interpret requirements for their viability against the business objective. The last thing any client will want is ‘a fully functional product/service that is not able to solve the problem the project was built for’ Recommend workarounds, value additions and remove solution bottlenecks for the stakeholders. Since a Business Requirements Analyst needs to have knowledge of both business and technology, he should be able to propose solutions other might not think of Document requirements by creating use cases, functional and requirement specifications documents. Also, Categorise requirements as functional (contains the features required by the end-users), non-functional (requirements for the performance and usability of the project) operational (operations that are carried out in the background) and technical and accordingly segregate them in different types of documents. Not all requirements may be important and feasible considering the scope and schedule of a project and thus these requirements need to be managed and prioritised by the Business Requirements Analyst by working closely with the business owners Prototype and model requirements – An important step towards letting the end users ‘feel’ what they might get at the end of the project completion. Also, prototyping aids in solution verification, error identification and getting early feedback regarding the user interface of the project Gain requirements sign-off from the key stakeholders by making sure all of them are on the same level of understanding against the requirements and then get written approval from them on the requirements to be developed Identify change requests and translate them into a documentation Follow the CR process supporting the development team until the deployment Overall, be the Requirement Gatekeeper and validate any new requirement for their effect and impact on the existing requirement set of the project. Aid in development and testing of the product – Business Requirements Analysts are frequently seen doing the unit testing of the features of their projects and are also assisting the testing team in test case preparation Be a part of the Change Control Board – A responsibility wherein an event of any change to the requirement/s, the Requirements Analysts is required to first assess the need of the change, deduce the impact of the change to the complete project, propose any workarounds if possible and then along with other board members (usually the Business representative, PM, technical lead) collectively decide whether to go ahead with the change or not. Prepare end-user documentation/manuals – A task which the Business Requirements Analyst may have to do in case a formal Technical Writer is not available Give client presentations, show and tell sessions, Overview sessions – Again, an optional task which needs to be covered by a Business Requirements Analyst in case the Project Manager or Project Coordinator is not available REQUIREMENTS Degree in Business Administration / Engineering At least 5 years+ of experience on testing/engineering in the automotive industry Must-have experience in mid/large structured companies (at least 4-5 yrs) Excellent knowledge of English (C1 level - equal or higher than) Computer skills/software: Microsoft Word / Excel / PowerPoint (GOOD), Google Suite (GOOD), Vector - Can analyzer, CDA, Atlassian Jira, Confluence, Siemens Polarion and various tools for ECU testing, Microsoft Project (BASIC knowledge) Project management skills: the resource will operate within a complex environment; will act as focal point and driver of the project Team-working ability: the resource will be in contact with different stakeholders both internal and external Personal interest for the Digital / Connected world will be considered a plus ...