I am a dynamic Software Business Analyst that possess a Product Owner, Quality Assurance, Agile and Scrum skills.
For Business Analyst role, I possess the quality of requirement gathering and elicitation following a unique steps from having the domain knowledge, stating the user persona, stating the features of the application or software under development lifecycle, eliciting the user story, writes the test scenario, writes the acceptance criteria, writes the test cases and documentation of test cases for testing purposes.
As a result of these documents, I work closely with the scrum team and more with the Product Owner for the purpose of Return On Investment (ROI) goals. I possess strategic Roadmap Planning of the product/software under the Software Development Lifecycle (SDLC), with a collaborative skill with the Scrum Master and Development Team using the Requirement Prioritization Metrics such as Minimum Viable Product (MVP), I.N.V.E.S.T. methodology, etc, to ascertain the Product Backlog Items (PBI) using Jira software as a tool, and in returns communicating with the PO or the Stakeholders with the authorization of the PO for adequate feedback to guide against defects and to help in achieving the definition of Done in each Sprint and achieving the goal of releasing a potentially shippable product increment on the projected date of release.
Also in most cases as I may be authorized, I make sure the development process undergoes daily refactoring, testing, coding, on a continuous basis for defect detention and for appropriate correction to be made.
Some of the metrics I work with are:
-Work In Progress Limit
-Capacity
-Backlog Health
-Root Cause Analysis
-Definition of Done
-Failing Fast
-Technical Debt
-Code Freeze
-POC and SPIKE
-Most Have, Should Have, Could Have, Won't Have (MOSCOW), etc.
The Technical skills that have worked for me are:
-Requirement Traceability Matrix (RTM)
- Data Directory
- Capability Maturity Model Integration (CMMI)
- JSON
- SQL
- XML
- HTML, etc.
I possess the skill to ascertain AS- IS and TO-BE using GAP analysis to create a process flow of how application works today, relating it to how I want it to function in the future using [login to view URL] or Balsamiq mop-up. And making sure the Scrum Team collaboratively work towards the achievement of common goal.