Mandatory Experience for the Role

• 2+ years of practical experience in software requirements analysis;

• Ability to analyze and document functional and non-functional requirements;

• Knowledge of requirements specification techniques, such as interviews and workshops;

• Familiarity with modeling and diagramming tools, such as use case diagrams and flowcharts;

• Ability to identify and manage changes in requirements;

• Understanding of business analysis principles and requirements management.

Mandatory Technical Knowledge

• Software Management: experience working on projects with agile software development principles and practices (Agile Manifesto, Scrum, and Kanban). Knowledge in agile product conception, design thinking approach, and design sprint process;

• Software Requirements: experience in elicitation, documentation, validation, negotiation, and requirements management, creation of requirements artifacts (Scrum), diagram creation (UML), and knowledge of business process modeling (BPM/BPMN);

• Software Construction and Configuration: Identify and map business needs in a practical and visual way. Represent business needs in the form of maps, business requirements, and user stories; Master the concepts of business analysis and process, user-centered design, and agile methods. Have facilitation skills and conduct workshops and classes using techniques such as: Design Thinking; Business Model Canvas; UX Design. Knowledge of business analysis practices, MVP (Minimum Viable Product), and agile requirements; Understand existing business processes, products, and services and their rules in order to provide IT solutions whenever necessary; Understand the needs of business managers and clients/users to propose solutions; Knowledge of the methods: SCRUM and Lean Startup; Knowledge of IT tools and solutions to solve business problems, ease in identifying IT services that can be reused in various businesses or stages of a business process: Figma, Balsamiq Mockup, or Bizagi. Assist the Product Owner in preparing the backlog of user stories for the start of sprint execution. Assist the Product Owner in accepting the stories built during the sprint. Maintain traceability of requirements and record impact analyses of sprint stories. Elicitation, analysis, specification, documentation, and validation techniques for stakeholder needs

Desirable/Differentiating Knowledge

• Certified Business Analysis Professional (CBAP);

• IREB Certified Professional for Requirements Engineering

• PMI Professional in Business Analysis (PMI-PBA)

Behavioral Skills/Soft Skills

• Enthusiasm for learning;

• Negotiation and communication;

• Interpersonal relationships;

• Analysis, abstraction, and extrapolation;

• Planning and activity management;

• Initiative and creativity.

Duties and Responsibilities to be Performed

• Gather, analyze, and document the project Scope containing the Domain Model design and other information that enables clear understanding and definition of the product backlog to be developed;

• Conduct information gathering through meetings with end clients and other stakeholders and analyze them to understand needs, enabling the generation of documents used in the creation of systems and applications;

• Document requirements for system and application development in a way that is easy to interpret for both programmers and clients;

• Prototype system screens to help understand what needs to be developed;

• Draw, as needed, Flow, State, Activity diagrams, among others that can complement requirements documentation and facilitate understanding of demands;

• Map and draw business processes as a complement to requirements documentation to increase clarity of the whole and facilitate understanding of what needs to be developed and delivered;

• Conduct requirements handovers to the development team and be able to resolve the team's doubts throughout the entire requirements lifecycle;

• Monitor items developed by the team to ensure that value deliveries are made in each cycle for our clients;

• Control change and improvement requests, keeping requirements always up to date;

• Provide support when necessary, identifying client needs, proposing process and function changes, negotiating solution alternatives, proposing the adoption of new methods and techniques, aiming to adapt solutions to their needs.

Employment Contract Information

Remuneration: To be agreed

Working Hours: 40 hours per week - Monday to Friday - from 08:00 to 12:00 and from 14:00 to 18:00.

Career Plan;

Access to courses on learning platforms

Work Model: On-site