What is UAT (User Acceptance Test)?

What is UAT : In this article let us understand what is UAT and what is the role of Business Analyst during UAT phase. As we discussed in previous articles, Business Analyst is responsible for end to end to project execution.

What is UAT (User Acceptance Test)?
What is UAT

UAT (User Acceptance Test)

Business Analyst suppose not to actively participate in testing part but, Business Analyst do support and perform testing.

What are User Acceptance Tests or what is uat?

User Acceptance Test is very important. Usually client will do the UAT. Once development completed and all approvals are in place, then we will release changes to client for Testing. Before releasing to client, we will do the end to end testing (Testing Team/QA Team).

Before planning for production movement, we will release to client for testing, client will do the end to end testing, and usually End users will do the UAT. As they have good knowledge on functionality, they will do the UAT.

Sample BA Document Templates


Send download link to:

I confirm that I have read and agree to the Privacy Policy.

Subscribe to get exclusive content and recommendations every month. You can unsubscribe anytime.

What is the Role of Business Analyst in UAT(User Acceptance Test)?

Business Analyst supports to End users during UAT, if any issues are observations raised by the client, then they will inform to the Business Analyst, Business Analyst is the person to understand the issues are observations raised by the client. Then Business Analyst will coordinate with the respective teams to fix the issues.

If any understanding gaps then Business Analyst will explain to the End users, what is the existing functionality and what changes we deployed, so that they can test without deviations, or else we deploy something and client test something else and raise as a Bugs or defects. It may lead to project delay and client escalation due to misunderstanding.

Business Analyst responsibility is to support to client during the UAT and get signoff from the client, once we received signoff (Approval) from the client then we will deploy the changes into production environment.

Why UAT (User Acceptance Test) is required and important?

As we discussed earlier, client will do the UAT testing and Business Analyst supports to complete the UAT successfully.

User Acceptance Testing (UAT) are tests that are usually conducted by the end user to verify that the product is working as expected. It is used to confirm if the product meets both the requirements and expectations of the stakeholders.

These tests are usually performed to capture product before it is deployed to the production environment.

The user acceptance tests are usually done in an environment that is almost identical to the final production environment.

They are one of the final tests that are conducted after all other tests such as the functional, integration and system tests are done.

As client (End Users) is performing the UAT, they can identify the application or functional issues/bugs.  As soon as we receive issue tracker or bug tracker from the client, we will start work on fixing the bugs. This helps us to deploy the product in production environment with ‘0’ errors or less errors. 

And we can make client happy as there is no issues or less issues in production environment.

If a defective product is prematurely deployed, it can severely damage an organization and the cost of fixing the incurred damages can sometimes outweigh the value to be gained from the deploying that product.

So it is important that the user acceptance tests are conducted before the product is deployed.

How are the User Acceptance Tests conducted?

The UAT is usually performed by the users who are going to use the final product, as they have knowledge and idea on product requirements and understand the business process so they are the best qualified resource to identify the application or functional issues with the finished product.

What steps to be taken care before deploying to UAT?

  1. Once the product is ready for the user acceptance tests, the test scenarios and test cases should be created. Sometimes Business Analyst may create the Test cases, it depends on the organization.
  2. The test scenarios should be created based on the requirements. If the project is Agile, then the created user stories can be used to create the acceptance testing scenarios.
  3. Once Test cases and test scenarios are in place, then we can release to client for testing.
  4. Before releasing to client we should ensure all the approvals are in place and testing and QA completed from our end.
  5. Then client starts the user acceptance tests and reports if any issues with the product.
  6. The identified issues should be reviewed and any defects should be fixed from our end. If any understanding issue or process gaps then we need to schedule meeting with the stake holders and explain to them.
  7. Once issues or bugs fixed from our end then again user acceptance tests should be rescheduled.
  8. The users should retest the product.
  9. The process continues until the product passes the tests at an acceptable level and we receive the signoff from the client. Without client signoff we can’t move any changes to production environment.
  10. Sometimes we will move the working product to production environment if the raised issues or bugs are not show stopper. It depends on the client.

What are the things to be taken care as a Business Analyst to complete the UAT successfully?

  1. Before client performing the UAT, schedule a meeting or session with the client and explain about developed product, like how it works and what are the requirements covered and how the solution has been provided to the requirements, so that client or end user can test the product in proper way.
  2. Identify the right testers: stakeholder analysis is an important part of the UAT’s because if the wrong people are invited to test the product, the product might not be properly tested and this could lead to costly mistakes. Usually client will assign the end users who needs to test the application, get in touch with the end users and explain and make them to understand the product before starting testing and before they raise as defect or bug.
  3. Business Analyst should have clear idea on test cases and test scenarios and what is the functionality of the product, so that it is easy to explain the product features and clarify the end user doubts.
  4. Clarify the test results: the UAT results might include the identification of some product defects and change requests. The report might require some clarifications, so the business analyst would need to follow up with the end users to fully understand the UAT results.

I hope this help you to understand what is uat and what are user acceptance tests. And why Business Analyst  should have knowledge on what is UAT?

What is User Acceptance Testing (UAT)?

Sample BA Document Templates


Send download link to:

I confirm that I have read and agree to the Privacy Policy.

Subscribe to get exclusive content and recommendations every month. You can unsubscribe anytime.


What is UAT testing?

User acceptance testing (UAT) is the last phase of the software testing process. During UAT, actual software users test the software to make sure it can handle required tasks in real-world scenarios, according to specifications.

What UAT means?

user acceptance testing

Short for user acceptance testing, typically the final phase in a software development process in which the software is given to the intended audience to be tested for functionality. … UAT also is called beta testing, end-user testing or application testing.

How is UAT performed?

User Acceptance Testing (UAT) is a type of testing performed by the end user or the client to verify/accept the software system before moving the software application to the production environment. UAT is done in the final phase of testing after functional, integration and system testing is done.

Who should perform UAT testing?

User Acceptance Testing (UAT), also known as beta or end-user testing, is defined as testing the software by the user or client to determine whether it can be accepted or not. This is the final testing performed once the functional, system and regression testing are completed.

What is the purpose of UAT?

User acceptance testing (UAT) is the last phase of the software testing process. … The goal of User Acceptance Testing is to assess if the system can support day-to-day business and user scenarios and ensure the system is sufficient and correct for business usage.

What happens during UAT?

User acceptance testing (UAT) is the last phase of the software testing process. During UAT, actual software users test the software to make sure it can handle required tasks in real-world scenarios, according to specifications.

Who prepares UAT test cases?

When it comes to UAT, often the UAT is composed of Business Analysts and selected end-users who will perform the actual UA testing. But QA, who have an overall responsibility to ensure the application/product works as required, should be part of the process for test definition.

What is UAT sign off?

UAT Signoff: When all defects are resolved, the UAT team formally accepts (or recommends acceptance to the project manager) the software application as developed. The approval shows that the application meets user requirements and is deployable.

What is UAT full form?

Short for user acceptance testing, typically the final phase in a software development process in which the software is given to the intended audience to be tested for functionality. … UAT also is called beta testing, end-user testing or application testing.

What is the difference between QA and UAT testing?

Difference Between QA and UAT Testing. … The major difference between both of these is the fact that quality assurance ensures that the software is error-free, whereas user acceptance testing ensures that the software is giving the users just the experience and usability that they were looking for.

How is UAT done in agile?

Lets have each of them one by one: Agile UAT begins with user stories which includes both story and acceptance criteria. … In last, UAT involves a dedicated sprint to perform overall user acceptance test and fixing discovered defects. It should be done by Product Owner along with the subject matter experts.

What are the primary objectives of UAT?

User Acceptance Testing (UAT)
The aim of User Acceptance Testing (UAT testing), is to receive feedback on the software from real customers. Thus, as a rule, UAT is conducted by people selected from the target audience. These conditions are the closest real-world usage of the product.

What is Stand up Meeting (Daily Scrum)?

How to Conduct Stand Up Meetings?

Let us discuss about Stand Up Meeting or daily stand up meetings.

What is stand up Meeting

Stand up meetings are an important event that is used in the Scrum methodology. Their primary purpose is to keep the Scrum team updated on the team’s progress.

The stands up meetings are usually held daily and they are allotted short time frames i.e. 15 minutes or less.

What is a Stand Up Meeting?

A stand-up meeting is a short meeting that is held on daily basis.  Usually this meeting will happen when day starts.  This is very short meeting and usually it takes 15 minutes. Due to its short time frame, these meeting are usually held with the team standing up, hence the name – Stand Up Meeting.

The purpose of the meeting is to update the status of the assigned user stories or tasks,  like finished, in progress, or about to be started. All the teams join in these meetings. They will raise their concerns if they have any, then Scrum Master will note down and coordinate with concerned teams if there is any dependency on other teams and try to provide the solution.

So this meeting is to understand the status of User Stories.

How to conduct  Stand Up Meetings?

The stand up meeting is to be brief and focused on the team’s progress. The Scrum Master is responsible for conducting the meeting so they should ensure that they keep the meeting straight to the point. No discussions will be allowed during this meeting. Only team members will update the status on the assigned user stories.

The Scrum Master should start planning the stand up meeting by choosing a convenient location and meeting time for all the team members.  Usually these meetings held on the same place and same time.

If we have team in different locations and team is working on different time zones, ensure that you pick a time when they would all be in to work.

Once the meeting is scheduled, the Scrum Master should ensure that the team stays focused by answering the below questions:

  1. What did you do yesterday?
  2. What will you do today?
  3. Is there any impediment, that is slowing or stopping you?

All the team members should ensure that they attend the meeting on time. So that time will not be wasted and it shows that they are respecting team member’s time.

Scrum Master should ensure all the team members must participate in meeting and sufficient time allocated to each team member to update the status.

When the team members are discussing their progress, they might get carried away and want to discuss details but the Scrum Master should try to keep them on track by asking them to take it “Offline”.

Taking it “Offline” means that the team member should schedule another meeting with the appropriate team members to discuss their encountered issues in more detail. Scrum Master is responsible to schedule the meeting.

While this might discourage some of the team members, the Scrum Master should remind them that the Stand Up meeting is a short one and other team members also have to provide their updates.

It is also called as Daily Scrum meeting or Daily stand up Meeting

This is also called as Daily Meeting, Daily Status Meeting, Daily Status update Meeting, Daily Scrum Meeting or Status call..


What is the purpose of daily standup meeting?

Daily Scrums improve communications, eliminate other meetings, identify impediments to development for removal, highlight and promote quick decision-making, and improve the Development Team’s level of knowledge. This is a key inspect and adapt meeting.

What does stand up meeting mean?

standup meeting (or simply “standup“) is a meeting in which attendees typically participate while standing. The discomfort of standing for long periods is intended to keep the meetings short.

How do you do a stand up meeting?

7 Rules for Effective Stand-Up Meetings
Only meet when necessary. One common employee complaint is that many meetings could easily be replaced by an email. …
Keep it short and sweet. At it’s core, a stand-up meeting is brief. …
Establish a goal. …
Maintain structure. …
Make remote employees feel like they’re there. …
Give everyone a chance to talk. …
Don’t skip follow-up.

What happens in a stand up meeting?

standup meeting is a short meeting between a team that is held on foot. The goal is to go over important tasks that have been finished, are in progress, or are about to be started. It is also known as daily standup or daily Kanban to teams practicing the Kanban method, due to the recurring cadence of the meeting.

What happens in daily standup meeting?

Daily Scrums improve communications, eliminate other meetings, identify impediments to development for removal, highlight and promote quick decision-making, and improve the Development Team’s level of knowledge. This is a key inspect and adapt meeting.

What are the three questions asked in daily standup call?

What did you do yesterday?
What will you do today?
Are there any impediments in your way?

What are the benefits of daily standup meeting in agile?

Listed below are few benefits of having daily scrum meeting:
Let’s the team to be in sync on how things are going.
Allows for corrections in the sprint.
Building trust between team members.
Encouraging personal planning.
High visibility of progress.
Self-organization in team.

How do I start a daily standup meeting?

Here are some effective tips for a successful daily standup meeting:
15 minutes or less. …
Be on time! …
Keep the team engaged. …
Put discovered problems on hold. …
Keep it fun! Start every standup meeting with a joke, meme, gif, comic, quote, etc. …
Say ‘thank you’. …
Hold your daily standup meeting around the task board.

Why is it important to meet every day for daily stand up?

The main aim of a standup meeting is to distribute relevant and important information and/or to make quick decisions. They are also used to make major strategic decisions and above all, they offer a chance to “go around the room” and get everyone to present their results from the day before.


Enjoy this blog? Please spread the word :)