4.7. Summary Table: BA’s Role Across SDLC Phases

Define scope, identify stakeholders Business Case, Stakeholder Matrix

In the planning phase, the Business Analyst (BA) focuses on defining the project's scope and identifying key stakeholders. This is crucial as it sets the foundation for the project by outlining what will be accomplished and who will be involved. The BA assists in creating a Business Case, which justifies the need for the project based on its potential benefits and costs. The Stakeholder Matrix is developed to document the stakeholders' interests, influence, and involvement, ensuring that all voices are heard in the planning process.

Imagine planning a community event. The BA is like the event organizer who needs to figure out what the event will achieve (scope) and who should be invited (stakeholders). They write down a proposal (Business Case) to convince the community council that the event will benefit residents and need particular support. They also list all the people who have a say in the event planning (Stakeholder Matrix).

Gather, model, and validate requirements BRD, FRS, Use Cases

During the analysis phase, the BA is responsible for gathering, modeling, and validating the requirements for the project. This involves eliciting both functional (what the system should do) and non-functional (how the system should perform) requirements from stakeholders. The BA creates documents like the Business Requirements Document (BRD) and the Functional Requirements Specification (FRS) to capture these requirements clearly. Use Cases are also developed to illustrate how users will interact with the system, ensuring requirements are understood and agreed upon.

Think of this phase as drafting a blueprint for a house. The BA, like an architect, meets with the homeowners to understand their needs and preferences (gathering requirements). They then create drawings and specifications (BRD and FRS) that outline the necessary features, such as the number of rooms (functional) and energy efficiency (non-functional). Use Cases are scenarios showing how a family would use the space, helping ensure everyone is on the same page before construction starts.

Collaborate on solution design, review Wireframes, Interface Requirements

In the design phase, the BA collaborates closely with UI/UX designers and technical architects. Their role is to ensure that the designs created are feasible and align with the business goals established earlier. The BA clarifies any requirements and provides input on wireframes and prototypes, confirming that they meet user needs and expectations. Key deliverables in this phase include wireframes and interface requirements, which outline how the user will interact with the system.

Imagine a dress designer. The BA is like the designer's assistant who ensures that the final dress not only looks good but also fits the client's requirements in terms of style and comfort. They review sketches (wireframes) and suggest adjustments to make sure the dress is practical for wearing on different occasions (interface requirements). Their collaboration helps guarantee the final product is exactly what the client envisioned.

Support UAT, trace requirements, validate Test Scenarios, RTM Updates

In the testing phase, the BA plays a vital role by supporting User Acceptance Testing (UAT) and ensuring that the solution meets the documented requirements. They assist in preparing test scenarios and cases that validate the system's functionality. The BA updates the Requirements Traceability Matrix (RTM) to ensure all requirements have been tested and validated. This oversight helps identify any discrepancies between the requirements and the actual product.

Consider this phase as a cook preparing for a big dinner event. The BA is like the head chef who double-checks the menu (test scenarios) against the actual dishes being served. They taste the food to ensure everything meets the quality standards laid out (UAT) and make lists to ensure that every dish has been prepared correctly (RTM). Their attention to detail ensures the dinner will be a success.

Assist go-live, create user guides, train Training Docs, Go-live Plan, Release Notes

During the deployment phase, the BA assists with planning the go-live activities and communicates changes to stakeholders. They may create user guides and conduct training sessions to ensure users understand how to use the new system effectively. The BA prepares a Go-live Plan and Release Notes that outline what will happen during the rollout, ensuring a smooth transition from development to live operation.

Think of the deployment phase like opening a new theme park. The BA is the park manager who organizes a grand opening event, making sure all staff are trained (user guides and training sessions) and that all rides are operational (Go-live Plan). They communicate with the public about new attractions (Release Notes) to generate excitement and ensure visitors know how to enjoy their experience smoothly.

Analyze feedback, suggest improvements, manage changes Change Requests, Impact Analysis Reports

In the maintenance phase, the BA monitors the system's performance and gathers feedback from users about its efficacy. They handle enhancement requests and analyze any issues that arise post-implementation. The BA creates Change Requests (CRs) and Impact Analysis Reports to propose optimizations or adjustments to improve the system's performance continually.

Imagine owning a smartphone. The BA's role in this phase is like a tech support specialist who listens to customers' experiences, identifying issues or desired features (feedback analysis). They then work with the software team to prepare updates that improve the phone's functionality (Change Requests) and assess how new features might affect existing software (Impact Analysis). Their goal is to ensure the smartphone remains useful and relevant to users over time.

--