Business Analyst 軟體需求商業分析師(必須有System Analysis經驗)
- 新北市新店區
- 5年以上
- 大學
BA的最主要價值就是利用資料，形成上面的報告，並利用商業知識，提供合理決策建議，所以，BA需要深入瞭解商業模式又有技術背景的資料分析專家和作為連接技術團隊與Business及stakeholders的橋樑。主要是介於客戶和IT團隊之間的角色，負責在IT專案中負責發掘、分析、傳達和確認客戶需求；同時瞭解有關業務上的各種問題並發現新的機會，搭建業務和IT人員之間的溝通橋樑，並推薦問題的解決方案以實現組織的目標，這其中還包括參與系統的設計和測試，以及各種協調工作。 Support, maintain, and document software functionality 【Business Documentation】 - Gather, analyze and document requirements for new projects from customers, support issues, research, and internal teams. - Create and maintain documentation used by business team to sell new features & products. - Create documentation for each release. 【Stake Holder and Project Team Walk-through】 - Give walkthroughs to business teams in order to elicit requirements - Give walkthroughs to Dev & QA teams in order for the project team to understand what needs to be done - Give Walkthrough to tech support near project launch - Give Demo to business teams & tech support to be able to support and sell in the future - Be able to work directly with all project teams including project manager to make sure project is on track and requirements are delivered in an adequate timeframe 【Critical Analysis & research】 - When given a project or idea, have detailed process for working through the solution - Give time for research in order to find new features and existing features to add to our platform - Be able to suggest proposed solutions to project teams and business teams rather than waiting for detailed requirements - Learn our platform inside out in order to be a consultant on business and technical questions 【Quality Assurance】 - Ensure releases are delivering the features that were agreed upon with stakeholders - Create training manuals in order to teach business users how to use our system - Find bugs during UAT that were not found during QAT - Be able to accurately help define priority with project managers 基本上就是 : 了解 business user 的想法和要完成的目標 提供相對應的系統流程與 user討論和確認 Integration API 要非常了解 和 與Vendor 做 需求 和 功能性 的確認 與developer說明和提供足夠的資訊和文件，包含 use case, exception case 了解每一個階段的系統架構和資料流，才能更快提出更多有用的建議 驗證需求 與Integration 有關的部分 : 1. 對於任何第三方廠商介接的相關事項，不管是新增一個API或是 某已經介接的API參數有變更，都能夠自主跟對方窗口協調跟溝通的能力，Developer不需要在這階段參與。 2. 對於任何需求，能夠有能力分析並提供適合的方案給User，若需求有跨部門的異動，可以主動跟其他部門的BA進行協調，並討論解決方案。 3. 在明確了解需求後，需要產出完整的SRS(需包含一般的功能行為，跟可預期的Exception handling)。 4. 當需求明確之後，再來跟Developer team進行go through。 5. 針對手上的待驗的Ticket應該主動管理的責任，應該主動的了解目前上版的Ticket清單，是不是要主動通知User進行複驗。 6. 若針對系統有不滿意的地方，可以提供完整且清楚的解決方案。