Requirement Gathering and Analysis: 1. Coordination with sales team and involved in client communication for initial call 2. Based on the conversation, create Proposal document (SOW), Questionnaire, assess client needs by understanding the client's requirements, challenges, and objectives. 3. Elicitation Techniques - Interview, observation, brainstorm, workshop for Requirement gathering 4. Identify issues: Recognize current and potential issues. 5. Explore and R&D for the proposed solution 6. Conduct Gap Analysis to understand the existing system and get the findings out of it. 7. Perform impact analysis Documentations: 1. Create BRD which includes the high-level requirement, stakeholder’s needs, project goal, objective in the initial phase. 2. Create FRD for the granular details of features and functionalities referred by the dev/testing team in the planning phase. It includes all the technical details, use case and system behaviour. List out the dependencies of APIs, perform feasibility study. 3. Perform the competitor analysis, listed out the new and advanced features. 4. Develop strategies: Create business strategies that meet the client's objectives. 5. Create User Story in Jira with acceptance criteria. 6. Create the Change Requests document. Identify the risks, dependencies and impacts of the newly introduced feature which must be integrated. 7. SLA, NDA, User Manual 8. Create the roadmap, divide modules in epic, listed out user stories. 9. Create the wireframe/prototype module wise with the Balsamiq/MS Visio/Figma tool. Focuses on UI/UX while creating the wireframe. 10. Create the UML diagrams (Use case diagram and Activity diagram) module wise with the [login to view URL] tool 11. create RTM for all the requirements Sprint Planning 1. Ensures that the Product Backlog Items (PBIs) are well-defined, meet the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable), and have clear acceptance criteria. 2. Collaborate with the Product Owner to refine and prioritize PBIs and assist the development team in understanding the requirements. Prioritize the product backlog items based on the business values. 3. Evaluate the velocity of team to include the tasks in the sprint 4. Adjust Trade off and view Burndown/Burnup chart. 5. Present the Wireframe/Prototype, UML diagrams 6. Provide Knowledge Transfer session to the team members for the selected sprint. 7. Refer the definition of ready checklist Daily Stand Up 1. Attend to stay updated on the team's progress 2. Address any blockers related to requirements 3. Provide the clarifications when needed Sprint Review 1. With the RTM, it helps the testing team to map all the requirements with the executed test cases. 2. Performed the process improvement 3. Involve in creating Test Cases and perform User Acceptance Testing (UAT) and API testing. 4. Create SQL queries to get the output, update and delete to manage database & data mapping. 5. Manage Trade-offs based on the re