O slideshow foi denunciado.
Seu SlideShare está sendo baixado. ×
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Carregando em…3
×

Confira estes a seguir

1 de 14 Anúncio

Mais Conteúdo rRelacionado

Diapositivos para si (20)

Quem viu também gostou (20)

Anúncio

Semelhante a Roles of business analyst (20)

Mais recentes (20)

Anúncio

Roles of business analyst

  1. 1. Roles of Business Analyst Author :- Sumit Sinha Software Business Analyst CSM®, EPGBM from IIM-C
  2. 2. Who is Business Analyst ?  Is a collaboration between the client and software development team
  3. 3. BA - characteristic  Functional  Technical  BA Skills  Tools & Techniques  Methodologies and models  Resume & Interview skills
  4. 4. Key BA Skills  Communication  Negotiation ( MMM )  Problem Solving  Leadership  Business Knowledge  Technical Knowledge
  5. 5. Roles and Responsibilities  Requirement gathering and analysis  Designing Prototype  Co-ordinating with development team to check how the business logic is implemented  Check with the testing team to check if the quality parameters are adhered
  6. 6. Roles and Responsibilities (Cont)  UAT (User Acceptance Testing)  UMP ( User Manual Preparation)  User Trainings
  7. 7. BA role is shared across  BA  TBA  Pre Sales Consultant  SME’s  Techno Fucntional Consultant  System Analyst
  8. 8. Reasons for Project Failure  Not Clear Requirements  Change in requirement by Customer  Lack of executive support/knowledge  Lack of user involvement/experiences  Unrealistic expectations  Improper Planning
  9. 9. Six key Skills  Elicitation  Enterprise Analysis  Requirement planning and management  Requirement communication  Requirement Documentation  Solution assessment and validation
  10. 10. Key Terms  Scope : Completing the project in time and budget  Requirement : A condition or a capability to which a system should adhere to.  Artifacts (Deliverables, Process Product) : the end result of an activity is called an artifact.  Prototype : The look and feel of the entire system in a wire frame.  Templates: It is a blue print or skeleton  Stakeholders : the person who is using or getting affected by the application or product is called as a stakeholder
  11. 11. Strategic Planning and Goal Setting  Focuses on Client/Customers requirements and offsore development team and plan to smooth delivery of the project on time. And prioritize programs and projects.  Provides context in which Enterprise Architecture is conducted.  Strategic planning related to environment and market trends  Assessing current technology structure to ensure alignment with business vision.  Identifying ongoing business issues.
  12. 12. Explore the business need  Business analyst is trying to find a solution for business needs and explore the business in right fashion.  Input : Business Goals and Objectives. A common test for assessing objectives is to ensure that they are SMART  Output : Business Need. A business need describes a problem that the organization is or is likely to face, or an opportunity that it has not taken, and the desired outcome.
  13. 13. Thank You! Name :- Sumit Sinha Contact :- sumitrsinha@gmail.com www.linkedin.com/pub/sumit-sinha-csm®-iim-calcutta/19/aa5/78a/

×