Development Support and user acceptance

Question 1

When do delivered features go through the go/no go process?

Answer 1

Once the UAT phase is completed

Question 2

What do Go / No Go decisions do?

Answer 2

Go means feature is approved and can be deployed to production
No Go means feature is not approved

Question 3

What is the outcome of a Go/No Go decision?

Answer 3

approving or rejecting a project deliverable before it is released

Question 4

What step in the release process are. go/no go decisions?

Answer 4

Final step before releasing feature

Question 5

What does the release checklist entail in Go / No Go decisions?

Answer 5

Does the Feature Achieve its objective
Does the feature impose risk
Does the feature impact live data
Does the feature comply with regulations

Question 6

For a Go Decision, what must be completed for project sign off?

Answer 6

project team verifies if the product accomplishes the elicited requirements, meets the acceptance criteria, and passes UAT

Question 7

Once what is given can the project team schedule the release of the product?

Answer 7

Official Sign off by project owner

Question 8

What does a No Go statement entail?

Answer 8

Feature is not ready for release TODAY, but could be on a later date

Question 9

Why would a No Go statement happen?

Answer 9

Feature would impact live data, not follow regulations

Question 10

How do business analysts help project owners in Go / No Statements?

Answer 10

Business Analysts are there to make sure the project owner understands all feature requirements, and that all teams are aligned.

Question 11

What is User Acceptance Testing?

Answer 11

UAT is the process is testing if the software meets the needs of the business

Question 12

When does UAT start?

Answer 12

there is a right time for UAT! It is:

After development of requirements, and before deployment

Question 13

What is the Business Analyst Role in the UAT process?

Answer 13

1. Identify the UAT Testers (who would be good at testing this feature?)
2. Obtain Sign-Off then conduct Roundup Meeting. Acts as liasion between business and developers
3. Creating Test Cases based on requirements
4. Executing test cases. does the feature complete the requirements?

Question 14

Who tests in UAT?

Answer 14

end users, project experts, project owner

Question 15

Who are the four groups of people involved in UAT?

Answer 15

Testers - End users of the product, or experts in the project

Project manager - Final Decision maker. is the link between testers and business owner

Business Owner - Project sponsor, makes sure test plan supports project goals. If shit doesn’t work, they approve changes

Software Development Team - If bugs are found, these guys fix them

Question 16

What are the steps in UAT?

Answer 16

Planning - what are the requirements, drawing up plans for UAT

Design Test Cases - Guide testers what to test in UAT, design use cases for testing

Select Testers - testers who UNDERSTAND THE BUSINESS should be selected

Executing tests and documentation - complete the tests, document bugs found

Bug Fixes - development team works to fix bugs

User Acceptance - Test team runs through tests again, signs off that it works

Question 17

What are the testing types including UAT?

Answer 17

6 -
Performance Testing (see how the system performs)

Unit Testing - Every unit of code in a single component

Functional Testing - system is functioning as expected, comparing code to system as a whole

User Acceptance Testing - End users who are capable of defining the process test to make sure feature works

Regression testing - verifies modifications are impacting existing functionality

System Testing / E2E testing - packages or api testing

Question 18

What are the best practices that should be followed while performing UAT?

Answer 18

1. make distinct plan for each KIND of test user. For each user type, write down business scenarios they will go through
2. Give the testers instructions for each business scenario to test. A good plan will include all test cases for each scenario (duh)
3. Check that each of the requirements will be tested by all intended user types. Add test plans as necessary for new user roles that get added.

Question 19

What should you avoid when planning UAT?

Answer 19

Reusing tests - those tests have already been passed!

Not planning UAT test plans - need to make sure users know how to test the new stuff!

Question 20

Difference between QA and UAT testers

Answer 20

QA testers are looking for system failures to locate flaws

UAT testers are looking to make sure features are acceptable and working

Question 21

How do Business Analysts facilitate UAT?

Answer 21

Are in all stages of UAT!
determine its scope, build the schedule, clarify all uncertainties

build tests, testing success paths and potential risks

gets the testers

works with developers to get all bugs fixed

Question 22

what is UAT?

Answer 22

User acceptance testing is end-user testing performed in a sandbox or test environment to verify that a project or enhancement works as intended, and what was originally requested is actually being delivered.

The BA prepares and guides UAT

Question 23

distributed vs centralized version control systems

Answer 23

distributed - copies on all workers computers of ALL versions of the project.
If server goes down, can backup from workers computer versions.

centralized - copies on central server, workers ‘check out’ PARTS to work on then check them back in when complete. Advantage - everyone knows what you are working on, disadvantage is if the server goes down or corrupted, lose all work