Business Analyst Roles & Responsibilities In Each Phase of SDLC:

-

Business Analyst Roles & Responsibilities In Each Phase of SDLC: 

For Full Business Analyst Training for Beginners: Check out my FREE training videos on #YouTube


SDLC:

SDLC stands for Software/ System Development Life Cycle, which is the process of developing software in a structured and systematic way. There are several phases in the SDLC, and they are as follows:

  1. Planning/ Requirement Gathering: This is the first phase of the SDLC, where the project is planned and defined. It involves identifying the scope, objectives, requirements, and risks of the project.
  2. Analysis: In this phase, the business requirements are analyzed, and a detailed description of the software is developed. Use cases, user stories, and other documentation are created.
  3. Design: In this phase, the software design is created based on the analysis phase. The software architecture, data structures, user interface, and other components are designed in this phase.
  4. Development: This phase involves the actual coding of the software. Developers write the code based on the design and requirements specified in the earlier phases.
  5. Testing: In this phase, the software is tested to identify any bugs or errors. Different types of testing are conducted, such as unit testing, integration testing, and system testing.
  6. Deployment/Install: In this phase, the software is released to the production environment. This involves installing and configuring the software on the server or client machines.
  7. Maintenance/ Support: This is the final phase of the SDLC, where the software is maintained and updated. Bug fixes, patches, and upgrades are made as needed to keep the software functioning properly.
Overall, the SDLC phases are designed to ensure that the software development process is systematic and structured, with each phase building upon the previous one.

Business Analyst Roles & Responsibilities In Each Phase:

Requirement Gathering:

  • Gathers project/ product requirements from internal/ external business. 

Analysis:

  • Evaluates information gathered from multiple sources, reconcile conflicts, decompose high-level information into details, abstract up from low-level information to a general understanding, and distinguish user requests from the underlying true needs. 
  • Study of the problem environment and the subsequent definition and prioritization of the requirements for solving the problem.
  • Develops use cases and functional specifications.
  • Identifies and analyzes gaps or conflicts in requirements.

Design:

  • Works with designers and developers to ensure the solution aligns with the business requirements
  • Develops data models, process models, and other documentation to support the design.
  • Collaborates with the testing team to develop test cases and scenarios.

Development/ Coding: 

  • A BA has limited role in this phase of SDLC. He/ She answers or get an answer from business in case developers have any questions.
  • Monitors the progress, what was planned and what is completed.
  • Collaborates with developers to ensure the solution is developed according to the design specifications.

Testing:

  • BA works with QA to ensure, development meets the requirement and the acceptance criteria.
  • BA can also do manual/ automation end-end testing.
  • During UAT, a BA plays a crucial role. He/ She is the ultimate responsible for successful user testing and sign-off. 

Deployment/ Install: 

  • Reviews new changes with the change management team, taking approval, creating installation/ deployment request.
  • Collaborates with the support team to ensure any issues or defects are addressed promptly.
  • Works with business with post production final testing.
  • BA DOES NOT do deployment. This responsibility lies with someone technical, usually developers or a dedicated operation resource. 

Support:

  • Maintenance and enhancement of the solution during agree timeline.
  • Training documentation, Biz/ user training.
  • Address any issues or defects that arise.

Comments

Post a Comment

Popular posts from this blog

Minutes of Meeting (MOM):

-
Image
Are you tired of taking ineffective meeting minutes? 🤔💬 Check out my latest YouTube video, 'Minutes of Meeting', where I share my top tips for creating clear and concise meeting minutes. Don't miss out on this valuable resource - head over to my channel now and start improving your note-taking skills today!   Click here:    Minutes of Meeting (MOM):  Minutes of Meeting (MOM) is also known as Minutes.  It is a written record of what happened during a meeting.  It is used to document the key points of a meeting, including decisions made, actions to be taken, and any important information discussed.  The minutes usually include the names of those in attendance, the date and time of the meeting, and the agenda items discussed.  Minutes of a meeting are typically taken by a designated person, such as a Business Analyst, and are distributed to all attendees and relevant stakeholders after the meeting. It serve as an official record of the meeting and ...
Read more

Business Requirement Document (BRD)

-
Image
Unlock the secrets to creating a winning Business Requirements Document (BRD) with my latest  YouTube video! 🚀💼. This free resource provides a detailed walkthrough on the components of a BRD and tips on how to create a document that aligns with project goals.  Don't miss out on this valuable knowledge - Watch Now:   What is a Business Requirement Document (BRD) and why is it important? A Business Requirement Document (BRD) is a formal document that describes the business requirements and objectives for a project or initiative. It typically includes a detailed description of the problem that needs to be solved, the goals and objectives of the project, the scope of the project, and the functional and non-functional requirements that must be met to achieve the desired outcomes. The BRD is important in software development projects because it serves as a critical communication tool between the business stakeholders and the development team.  The purpose of the BRD is...
Read more