A BRD is a formal report that outlines the business rationale and

expectations for a project, program, or business solution. An FRD

is a formal statement of an application's functional requirements,
and acts as a contract between developers and the project.
• What is the template of BRD and FRD?

BRD-

BRD should have a logical flow and easy to understand. The most
acceptable contents of a BRD are as below:

• Objective of the project

• Current business state, environment and system assessment
• Business changes to be done
• Process detail and stakeholders details
• Accepted assumptions and constraints in the project
• Impact (or Risk) Analysis
• Functional Requirements
• Non-functional
• Schedule and Budget (optional when BRD is shared with technical team)
• Terms and Conditions (Legal information)
Finally the document should contain the business partner sign-off with the details
of the review, comments and signature of the business partners.

FRD-

• Introduction
• Purpose
• Scope
• Background
• References
• Assumptions and Constraints
• Document Review
• Methodology
• Functional Requirement
• Context
• User Requirements
• Data Flow diagrams
• Logical Data Model/Data Dictionary
• Functional Requirements
• Other Requirements
• Interface Requirements
• Data Conversion Requirements
• Hardware/Software Requirements
• Operational Requirements
 • Appendix A – Glossary

Finally the document should contain the stakeholders sign-off with the details of
the review, comments and signature of the stakeholders.

• What is the high level difference between BRD and FRD?

BRD is created from the business flow ad business requirement point of view and FRD is
prepared from developing that requirement.

What is Acceptance Criteria?

ACCEPTANCE CRITERIA: Acceptance criteria are the specific rules or conditions that a product must
meet for the work to be accepted as complete.

OR

The Definition of Done (DoD) is a clear and concise list of criteria that a product increment must
meet for it to be considered complete and ready for release.

What is Scrum?

Scrum is an agile project management framework that helps teams structure and
manage their work through a set of values, principles, and practices. Much like a ...

Que . What is difference between Agile and Waterfall Methods.?

Ans :

Agile Waterfall
In Agile all the software development process is It is a linear sequencing model for developing and
done in smaller parts, that called Sprint. testing software.
Changes can be made at any time of development. Once the development started, requirement cannot
be changed.
It is a flexible method to build a software. It is a structure method for software development.
Que . What is Product Backlog & Sprint Backlog?

Ans : Product Backlog – A user requirement list for whole project according Priority, It is created by
Product Owner.

Sprint Backlog – Sprint Backlog is splitted part of Product Backlog. We break the Parts into
manageable Parts.

Que . What is Sprint ?

 Ans : In Agile we do all the Process in smaller parts or small time duration, these time duration are
called SPRINT.

Que . Who is Product Owner ?

Ans : Product Owner keep all the accountability of all the requirements of Client that which
Requirement should be Processed First and which will go last.

Que. What is Epic, User Story and Tasks ?

Ans : User Story -. A user story is a brief description of a feature from the perspective of an end
user, typically following the format: "As a [user], I want [feature] so that [benefit]."

Epic –AN epcic is big idea of project which can broken down to smaller task or user story

Task – In Jira, a task is a work item that needs to be completed, while a sub-task is a smaller, more
manageable piece of a larger task..

Que. Which Software used for Project Management ?

Ans : we use JIRA for Project Management.

Que. What are the Templates of User Story.?

Ans : User Story Template is as Follows ;

“As a” “ I want to” “So that”

Exa : For example, user stories might look like:

• As User, I want to invite my friends, so we can enjoy this service together.

• As User, I want to organize my work, so I can feel more in control.
As a manager, I want to be able to understand my colleagues’ progress, so I can
better report our success and failures.

Que. What is Velocity.?

Ans : It predict how much work Agile Team can complete in a Sprint and how much time will it
require to complete a Project .

Q. Which methodology you are working in agile?

Ans: I have worked on waterfall and agile both, currently I am working in Scrum

Q. what are ceremonies in scrum?

Ans: There are 4 ceremonies in scrum-

1. Daily Standup – We gather tother over the call at 6:30 pm to get updates on each user
story.

2. Sprint planning – In this meeting we are planning the complete sprint, which user stories
to be picked and who is working on which story.

3. Sprint review – In the meeting, we are looking that everything going as per sprint planning
or not and what needs to be changed during the sprint

4. Sprint retrospective – what went good or bad and how to improve next sprint and plan
success party if everything went well.

Q. what is the duration of sprint?

Ans: Here, we follow 2 weeks of sprint duration.

Q. what is velocity?

Ans: How many story points completed in a sprint and average of story points completed in different
sprint is called team velocity.

Q. how do you capture requirement in Agile?

Ans: - We capture requirements in agile through User stories.

Q. what do you do in UAT?

Ans: I use to do a couple of tasks in UAT like writing UAT test cases, reviewing the test cases, tracking
the UAT on a daily basis so that I can monitor the progress of the UAT and taking the sign off from
the client after successful completion of UAT.

Non-functional requirements (NFRs) are specifications that define the

quality attributes, system performance, and constraints of a system.
These can be divided into Operational Level Agreements (OLAs) and
Service Level Agreements (SLAs).

1. **Operational Level Agreement (OLA)**:

- **Definition**: OLAs define the interdependent relationships among the

internal support teams within an organization to support SLA compliance.
 - **Example for a Ride-Sharing App (like Ola)**: "The system must ensure that
the database response time for queries does not exceed 200 milliseconds during
peak usage times."

2. **Service Level Agreement (SLA)**:

- **Definition**: SLAs are formal agreements between a service provider and

an external customer, detailing the expected level of service.

- **Example for a Ride-Sharing App (like Ola)**: "The app must maintain an
uptime of 99.9% per month, ensuring that users can book rides at any time with
minimal downtime."

In summary:

- **OLA** focuses on internal performance and cooperation within teams to meet

service delivery goals.

- **SLA** focuses on the service quality and performance agreed upon between
the service provider and the external customer.

Interview Questions-

A BRD is a formal report that outlines the business rationale and

expectations for a project, program, or business solution. An FRD
is a formal statement of an application's functional requirements,
and acts as a contract between developers and the project.

• Are you also responsible for the appraisal of the team?

Yes, I am responsible for the appraisal of the team because I am reviewing, monitoring,

guiding and allocating the task to the team throughout the year.

• What is the template of BRD and FRD?

BRD-

BRD should have a logical flow and easy to understand. The most
acceptable contents of a BRD are as below:
 • Objective of the project
• Current business state, environment and system assessment
• Business changes to be done
• Process detail and stakeholders details
• Accepted assumptions and constraints in the project
• Impact (or Risk) Analysis
• Functional Requirements
• Non-functional Requirements
• Schedule and Budget (optional when BRD is shared with technical team)
• Terms and Conditions (Legal information)
Finally the document should contain the business partner sign-off with the details
of the review, comments and signature of the business partners.

FRD-

• Introduction
• Purpose
• Scope
• Background
• References
• Assumptions and Constraints
• Document Review
• Methodology
• Functional Requirement
• Context
• User Requirements
• Data Flow diagrams
• Logical Data Model/Data Dictionary
• Functional Requirements
• Other Requirements
• Interface Requirements
• Data Conversion Requirements
• Hardware/Software Requirements
• Operational Requirements
• Appendix A – Glossary

Finally the document should contain the stakeholders sign-off with the details of
the review, comments and signature of the stakeholders.

• What is the high level difference between BRD and FRD?

BRD is created from the business flow ad business requirement point of view and FRD is
prepared from developing that requirement.
 • How would you ensure that whatever requirement client has given is implemented or not?
For this; we prepare a Requirement Traceability Matrix (RTM) document. In RTM, we map each
requirement with the test cases and ensures that every test case must pass.
.

1. **SIT (System Integration Testing):** Testing how different parts of a

system work together, like checking if the car's engine and transmission work
smoothly together.

2. **UAT (User Acceptance Testing):** Testing is done by end-users to

ensure the software meets their needs.

3. **Regression Testing:** In RT we Recheck existing features to ensure they

still work after changes,

What is Unit Testing ?

WHAT IS TEST CASE?

Test case attributes are the various characteristics and information associated with each test case,
providing context and details needed for effective test execution and management. Common test
case attributes include:

1. **Test Case ID/Name:**

- A unique identifier or name to distinguish the test case.

2. **Description:**
- A brief description outlining the purpose, scope, and goals of the test case.

3. **Test Steps:**
- A sequence of detailed steps or actions that the tester needs to perform during the test.
4. **Test Data:**
- The specific input data required for the test case to be executed.

5. **Expected Result:**
- The anticipated outcome or behavior when the test case is executed successfully.

6. **Actual Result:**
- The result observed during the actual execution of the test case.

7. **Test Environment:**
- Information about the testing environment, including hardware, software, and network
configurations.

8. **Preconditions:**
- Any necessary conditions that must be in place before the test case can be executed.

9. **Postconditions:**
- The state or conditions that should exist after the test has been executed.

10. **Priority:**
- The importance or urgency assigned to the test case, indicating its relative significance in the
testing process.

11. **Test Case Type:**

- Categorization of the test case based on its purpose, such as functional, integration, or regression
testing.

12. **Test Case Status:**

- The current state or progress of the test case, indicating whether it's pending, in progress, or
completed.

13. **Assigned To:**

- The individual or team responsible for executing the test case.

14. **Execution Date:**

- The date and time when the test case was executed.

What are the documentation you use to prepare as a BA:

• BRD
• FRD
• RTM
• User Profile Matrix
• Gap Sheet for gap analysis
• Data mapping sheet
• ETL document

Which software do you use in your job?

Project Management Tool – JIRA

Database – I have worked on oracle and sequel both, for Oracle I have used SQL Developer, Rapid
SQL, TOAD. For sequel, I have used Microsoft management studio.

For making Diagrams – MS Visio

For Project documentation – we use Confluence, share drive share point