SDLC & Agile Interview Questions

What is the difference between bug release and bug leakage?

- A bug release is when a version of a software is released with a set of known bugs. These bugs are usually of low severity/priority. It is done when a software company can afford the existence of a bug in the released software rather than the time/cost for fixing it in that version. -Bug leakage is something when the bug is discovered by the end users or customer and missed by the testing team to detect while testing the software.

Tell me about your framework

- I have a Maven project. It is based on Java Selenium. I am using cucumber for BDD and Junit for assertions. In my previous project I worked in TestNG. For reporting, I use cucumber html reporter. I take a screen shot after every failed test case. I use Page Object Model. So for each page in the application I have a page class where I store my elements and reusable methods. I have utility classes, I store generic reusable methods there, such as actions class items, waits, clickable items (because some codes are several lines, I put them in one method and I call them when I need it) -I am using Log4) for logging error messages. Our repository is located in GitHub. Development code is in different repository, testing code is in different repository. -My company uses Jira as a proprietary issue tracking product that allows bug tracking and agile project management. -For database management I use Oracle SQL -As a CICD tool I use Jenkins. -Manual API - POSTMAN or SOAP UI -For Automation - It is a MAVEN project, I use cucumber with Junit, and Java Rest Assured Libraries.

How is Agile Methodology different than Traditional Waterfall process?

- In Agile methodology, features of the software are delivered frequently, so that the testing activity is done simultaneously with the development activity. Testing time is shortened as only small features are need to be tested at once. - While, in the waterfall model, testing activities take place at the end of the entire development process. Testing time, in this case, is as long as the entire product is to be tested in one go. Waterfall methodology is a closed process where all stakeholders are not involved in the development process whereas agile methodology requires an involvement of various stakeholders including customers.

What Is the Difference between Black Box and White Box testing?

-Black box testing is a testing approach which depends completely on the product requirements and specifications. Basically, front-end testing. The knowledge of internal paths, structures, or implementation of the software is not needed -White box testing is when you know the internal structure of the application meaning you know coding and can perform unit testing as well.

What challenges have you faced in Agile environment?

-Changing of Requirements. -Not Enough Information on the Story -Estimating Time For Completing Task -Waiting on Development to be completed before testing

Tell me about yourself

-Good morning everyone! This is _. I have been in QA industry for the past years experienced in both automation and manual testing on Web-Based Windows and Client- server applications. Performed different types of testing such as Regression, Smoke, Database, Positive and Negative testing. -To summarize my roles and responsibilities - I am involved in all the phases of Software Testing Life Cycle, Starting from Impact analysis of requirement till production deployment. -Now coming to software development methodologies, I have worked in multiple critical business projects in both waterfall as well as scrum agile methodologies. -Coming to my automation working experience I have been working for last XXX years as an automation engineer using selenium automation tool with Java. -Just to add here, I have also worked at client location where I used to work with several stakeholders and coordinate with offshore team.

What are you discussing in these meetings?

-Grooming meeting - grooming the user stories, giving points to the stories, asking questions and clearing any unknowns. -Sprint planning - going over the stories one more time, discussing any remaining questions or unclear points, making sure the team is confident with the number of the user stories and points in the next sprint. -Daily standup - short meeting where every team member updates the team about his/her work and basically answers three questions: What I did yesterday, what I am going to do today and if I have any blockers. -Retrospective - a meeting where team reflects on the previous sprint. The team discusses three questions: What we should START doing, what we should CONTINUE doing, what we should STOP doing. -Demo - a meeting where team present the completed work to stakeholders and other teams in the company.

What is Negative Testing and what is Positive Testing?

-Negative testing is testing application with a negative/ incorrect/ invalid data and verifies weather application reject or accept/expected error message is displayed or not. -Positive testing is, testing the system with correct and valid data and expecting to not see any errors.

What is a peer review?

-Peer review is when you would go over your co-worker testers test case to make sure everything is good, no issues with test case grammatically or logically it makes sense. -An example at (your Company we have a code meeting review every Wednesday. When someone developed a function all team members review/test/try to break/ provide suggestions to the newly developed function before placing it in the shared folder.

Can you tell us the difference between STLC (Software Testing Life Cycle) and SDLC (Software Development Life Cycle)?

-SDLC stands for Software Development Life Cycle. Which consists of the following phases Requirement gathering, Design, Coding, Testing, Production -STLC stands for Software Testing Life Cycle. Which consists of the following phases Requirement analysis, Test Planning, Test case Development, Setup testing environment, Test Execution, Test closure

Describe Scrum

-Scrum Team - Normally scrum team consists of 5-9 team members. This is called development team-which includes Developers, Testers and BA -Scrum master - He or she is responsible to move the team to the right direction and handle all needs of the team. Scrum master is the coordinator assures team productive and following agile principals. Also if there are any issues and blockers scrum master is the point of contact to handle such matters -Product owner - He or she has the responsibility of delivering a whole concept of what to build and then convey the idea to the team. Also they are the one who created wish list to the project which is called product backlog. Product owner usually prioritizes the product backlog item and comes up with sprint Backlog as well.

Scrum Ceremonies

-Sprint Planning Meeting- Here the Product Owner selects the Product Backlog Items (User Stories) from the Product Backlog. Most important User Stories at the top of the list and least important User Stories at the bottom. Scrum Development Team decides and provides the effort estimation. For example, 4 hours up to 20 hours etc. -Sprint Demo - This is usually led by SME or test lead where we will have demo for client (Stake Holders) and showcase what was developed and answer any questions they have a quick walk through of what was built and also receive feedback. -Sprint Retrospective - Here scrum team meet and documents the lessons learned in the earlier sprint such as "What went well*, "What could be improved". It helps the Scrum Team to avoid the mistakes in the next Sprints. -Daily Scrum - Everyday we will have a 15 minute scrum meeting to answer following question: What did he/she do yesterday ? What he/she will do today ? What are the impediments (blockers) faced ?

What is the difference between static and dynamic testing?

-Static Testing (Done In Verification Stage). Static Testing is a White Box testing technique where the developers verify or test their code with the help of checklist to find errors in it, this type of testing is done without running the developed application or program. Code Reviews, Inspections, Walkthroughs are mostly done at this stage of testing. -Dynamic Testing (Done In Validation Stage). Dynamic Testing is done by executing the actual application with valid inputs to check the expected output. Examples of Dynamic Testing methodologies are Integration Testing, System Testing, Regression and Acceptance Testing.

What are differences between a Test Plan and Test Strategy?

-Test Plan provides more details on how the testing should take place in the entire project lifecycle -Test Strategy is a high-level plan usually initiated by QA manager. It captures all the primary testing activities. It is basically for the stakeholders who have high influence but low interest in the project. includes a plan for how to test the application and exactly what will be tested (user interface, modules, processes, etc.). It establishes limits for testing and indicates whether manual or automated testing will be used.

Can you tell us the different type of testing you are aware of?

-Unit testing -Integration testing -Regression testing -Ad-Hoc -Smoke testing -Performance testing -Load testing -stress testing -White box and Black box testing -System testing

What is a testing hierarchy?

-Unit testing: Developers test their code to make sure the functionality they are working on created is working. -Component Testing: Component is a standalone functionality that can work by itself. -Integration Testing: All modules are combined. When integrated do they still work together. -System Testing: Hardware, Software, Database, servers everything. -Acceptance Testing: (User Acceptance Testing) It's testing by UAT team mostly business/client-side team or hired UAT team that validates what QA team tested before moving to production.

What's a user story?

-User stories are short and simple description of capabilities. They are written from the perspective of a user or customer of the system. Other word for user story is Requirement. -EXAMPLE: As a (valid user]. I want [to access the system] so that [I can review my information]. -As an [administrator]. I want to (restrict access to the system to valid users] so that [I can ensure we protect user information].

What is test coverage?

-What we are testing and How much we are testing. -Test coverage means how many test cases we have and what functional areas of those test cases are being covered. Do our test cases cover the entire application or not?

When do we use Agile Scrum Methodology?

-When the client is not so clear on requirements. -When the client expects quick releases -When the client doesn't give all the requirements at a time

What other agile meetings you have?

-sprint grooming -sprint planning -daily stand up -retrospective -demo

Can you explain the difference between bug severity and bug priority.

A bug severity is how damaging a bug can be, how much impact it will have on the system while bug priority is how fast a bug needs to be fixed, it's the time frame of its urgency

What is a hotfix?

A hotfix is an emergency issue that needs to be fixed right away and does not need to go through a whole sprint cycle. It's an exception where it can be developed tested and deployed in few hours or a day since it's an extreme priority and client wants the critical issue fixed ASAP and deployed.

What is a test case and what does it include?

A test case is a document which has a set of actions that needs to be executed to verify a feature or functionality of your software application. It includes -Test Scenario/Objective -Pre-Condition -Test Case ID -Test Data -Test Description -Expected Result -Actual Result -Pass or Fail -Comments

When is a test considered to be successful?

A test that discovered more errors. The whole purpose of testing process is to discover as many bugs and errors as possible. Test that covers more functionality and discovers more errors in your software product, therefore, considered more successful.

What is agile?

Agile is a term used to describe a general approach to software development. All agile methods, including Scrum, emphasize teamwork, frequent deliveries of working software, close costumer collaboration, and the ability to respond quickly to change.

What is 508 Compliance testing?

All government websites are supposed to be 508 compliant meaning disable personel should be able to use it. Features are specific font is used on these types of websites, Text to speech capability and magnify capability etc. Just know what it is but you don't have to tell the interviewer that you have done so.

What is an Epic ?

An epic is a large user story that cannot be delivered as defined within a single Sprint .It is large enough that it can be split into smaller user stories

What is the most difficult problem you've found during testing?

An unclear requirement is the most challenging part it requires continues meeting and going back forth for clear explanation and even justifying a bug sometimes since requirements are vague. It also makes writing test cases difficult at time and modifying them when they are already created.

When does the automation testing start?

Automation starts when I receive my user story. I start working on my scripts and when I receive the actual locators from the developer I integrate them to my automation suite, make the necessary corrections and finish up with the automation. This saves a lot of time.

What is Beta Testing?

Beta testing is conducted to gather feedback from the real-time usage of the product. It happens after the installation at the client-end or another good example is in real-world gaming industry they release a game to a certain audience before a mass release to get feedback.

What is Ad-Hoc Testing? Exploratory testing?

Both are the same thing, it is informal testing where you are testing without a test case and randomly testing a module conducting negative testing and positive testing but not in any order etc.

What is Boundary Testing?

Boundary testing is to make sure software accepts valid data inside the valid Boundary and rejects invalid data outside the valid Boundary. A simple example input field limitation is from 0 to 100 so lower boundary 0 higher boundary 100. We make sure we can't go lower than 0 and higher than 100. We only test the edges and not the middle

How do you define the bug life cycle?

Bug life cycle basically comprises of numerous statuses of an error during its life cycle. A few examples are open, deferred, solved, reopened, fixed, retest, Reject, solved and closed.

What is the most technical work in test automation that you have done in the last three vears?

Building new frameworks from the scratch.

What did you do which made you different from others in your current project?

Developed the automation regression suite further which covered more functionalities/scenarios of the application. It made regression testing easier and faster, also caught bugs in earlier stages.

What is DoD? How is this achieved?

DoD stands for Definition of done. It is achieved when: -The story is development is complete -QA complete -Regression around the story is complete -The feature is eligible to be shipped / deployed in production.

What are the layers in the application?

Environments. We have Dev, Test, UAT and Prod environments in our application. The work starts in Dev environment and makes it way to Production where customers see the application. Environments get more and more stable towards the production: Dev being the least stable and production being the most stable environment.

What do you do when you find a bug?

First you will go back and retest it to make sure it is a bug, then you take a screenshot and create/log a bug in Jira with as many details as possible such as short description, environment found in, exact steps to reproduce, severity, priority etc. so the developer can try to recreate it.

How long is your sprint?

For this vou can either say 2 weeks long or 4 weeks long sprint.

What challenges did you overcome in your project? How did you do it?

Frequently changing requirements. Tried to overcome the challenges by prioritizing tasks, getting organized and completing tasks one by one.

What would you do if a developer rejects your bug and refuse to fix it?

Go back and retest it several times that it is a bug. Then check it against the requirements'. If the developer still refuses to fix it then set up a meeting between BA and developers. If in rare situation developer still does not want to fix, then QA manager or Project manager get them involved last resort.

When is a good time to stop testing?

Here are some factors that tell us when to stop: -Deadlines (Release or Testing timelines) -Test case completion with expected pass percentage -Testing cost overruns. -Attained the desired coverage of code/functionality/requirements. -Defect discovery rate falls below the threshold.

How do you create defect in your project (JIRA)?

I click on "Create" button, choose type "Bug", put a title, and write a description of the defect.

Your experience in IT

I have been in IT sector now for more than 7 years. I started as a Manual tester and after seeing the needs of the IT sector, I gradually changed to automation.

What are some tools you have used in your project?

I have used various tools throughout my career. For bug tracking, I have used JIRA mostly but have some exposure to ALM. For automation, I have been using Selenium for several years. SOL developer for back- end, Cucumber Reporting for screen capture for reporting purpose. Besides that, I use Outlook for email and Skype Business/LYNC and Slack chat for communication. Also, for document sharing across the company I have used SharePoint and Version ONE as well. -IF they ask, have you used RALLY, JAZZ, Microsoft TFS or some other tools, just mention you are very familiar with it but other team members used it in other projects and they are very similar and it won't be a problem for me to work with it.

Out of your total experience, please provide how much of it is in Automation QTP (UFT) vs Selenium Java?

I only have experience with Java Selenium and I have been doing automation now 6 years.

What other information you provide when creating defect?

I put as many details as possible, such as steps to recreate the bug, login, ID details, environment that it was found, screenshots or recording, severity of the defect, when we should fix that bug (current sprint or one of the upcoming ones). Finally I assign it to the relevant developer.

How do you see yourself in the next three ears (more leadership or technical role)?

I would like to get better at what I am doing, learn more tools, find most efficient ways of testing the application, and contributing to having a bug free application. Also I would like to improve myself, get required training and try myself in leadership roles.

Let's say you have a bug that comes in the day before the sprint is ending, do you let it go into production or move it to the next sprint?

IF the bug is of a very low priority and severity we will log it and fix it at a later time since it doesn't impact the system much and release it into production, but if it's a show stopper we will never release it into production since it can cause other issues.

When do you know if you have enough test cases for your project or a specific module?

If all requirements have at least one test case, then we know we have covered everything also in this case an RTM is very useful since it maps out Requirements to Test Cases

If there isn't enough time for testing what would you do?

If we are short on time, I would prioritize my test cases and tackle ones that cover most functionality. I will also check with my team members to see if they can help. Since I have been on agile projects we work together in matters as such.

You are in the middle of a sprint and suddenly the product owner comes with a new requirement, what will you do?

In ideal case, the requirement becomes a story and moves to the backlog. Then based on the priority, team can take it up in the next sprint. But if the priority of the requirement is really high, then the team will have to accommodate it in the sprint but it has to very well communicated to the stakeholder that incorporating a story in the middle of the sprint may result in spilling over few stories to the next sprint.

How many months did you spent on doing API Automation in the last year and the last six months?

In last year about 1-2 months in total.

How often you execute your test scripts?.

In my company we run our regression suite twice a day to make sure the application is working as expected.

Where do you write your test cases?

In my company, all test cases are written in excel. In past when I was exposed to ALM you could create Test Cases in ALM under Test Plan Module but last few years in this project I have been using JIRA. We only have Atlassian Confluence where our team only uploads and holds our Systems Documents, BRD, and other documents.

Other than testing what else have you done to contribute to the team?

In my experience I have created documentation like, user guides, PowerPoint slides, conducted demos and attended meetings and traveled for projects representing my team.

How would you test an application if the requirements are not available?

In this scenario you experience plays a role I would do significant amount of AD-hoc testing to start off then I will gather as much information from end- user and also see competitors application if available to get an idea. I will schedule meetings with end client or SME who can really guide me.

What would you do if you end up with unclear requirements?

In this scenario, your knowledge of application plays a big role I would start to do some random testing to understand what is being asked or what is at least attempted basically discovering to get an idea, so I can start writing scripts. Then I will check our meeting notes, emails, and discussions on this requirement. On top of that, I look for a wire frame which might give me an Idea but overall my common sense and experience plays a part here and also I would think from a customer's perspective here. I can also ask if BA is available to clarify them as well.

What is system testing?

It is testing the entire system where Front-end, Back-end, Database, Server, Hardware, Software everything is tested.

Who approves test cases?

It varies, from company to company. In some companies, test lead would approve them. In other places, just a peer review is good enough and you don't need formal approval, while in some cases a business analyst can approve as well it all depends.

What is component testing?

It's when you are testing each component of the application separately. In application, it could be one component. One component has stand-alone functionalities, for example, Amazon Prime, Amazon Fresh etc.

What is unit testing, and have you ever done unit testing?

No, I haven't done unit testing. Unit testing is done by the developers before they deploy their code from the Development environment to QA environment.

Can you do 100% manual testing and find all bugs?

No, it is impossible because there are a number of possibilities and scenarios. If we cover all functionalities and test them then we can reduce the risk of bugs and have a satisfied client.

What is Integration testing?

Once every individual component is tested we must make sure that when we integrated these components together they must work as expected. Example amazon.com has fresh and prime, but the entire website works together even it has different components.

What is non-functional testing?

Performance testing, Security testing

What is the difference between UAT and QA? What is Acceptance testing?

QA is one lower environment to UAT. QA can be a separate team that does testing and after PASS QA environment code is moved to UAT environment where again Testing is conducted to make sure no bugs have been missed. Also, UAT is mostly conducted by the business side or client side. Acceptance testing is UAT testing another name for it.

What is Requirement Traceability Matrix?

RTM is mapping requirement to test cases and test cases to the defect. If there is a defect found, we can trace back to tell which specific requirement failed. RTM also tells us if we are missing test cases in case requirement is there and no test case is available.

What is the difference between regression testing and retesting?

Regression testing is performed if new functionality is added or bug fix occurs, and we want to make sure other parts of the application is still functioning correctly. While retesting means if a defect gets fixed, I must retest the functionality to see it is really fixed or not.

What's Requirements Traceability Matrix?

Requirement Traceability Matrix (RTM) is a document that maps and traces user requirements with test cases. It captures all requirements proposed by the client and requirement traceability in a single document, delivered at the conclusion of the Software development life cycle. This document makes sure that my test cases cover all the requirements so I don't miss anything.

Tell us some key challenges you face in Testing industry?

Requirements changing. -Application not stable. -Rush testing to meet deadline -Unclear requirements -Domain knowledge and business user perspective understanding. -Lack of Regression testing or not enough. -Lack of skilled testers. -Lack of resources, tools and training

How much time do you spend on doing hands-on scripting weekly in your current project/assignment?

Scripting takes about 60% of my time.

How do you determine the level of severity of a defect?

Severity can be broken by the functionality here are some examples -Low priority bugs are small errors that don't stop shipping or cause real trouble for any user. -Medium priority bugs cause some internal users trouble but have known workarounds. -High priority bugs are problems that our customers will see, can corrupt data, or crash a system. -High Priority & High Severity: An error which occurs on the basic functionality of the application and will not allow the user to use the system. -High Priority & Low Severity: The spelling mistakes that happens on the cover page or heading or title of an application -High Severity & Low Priority: An error which occurs on the functionality of the application (for which there is no workaround) and will not allow the user to use the system but it's on part of the application rarely used -Low Priority and Low Severity: Any cosmetic or spelling issues which is within a paragraph or in the report (Not on cover page, heading, title).

Have you done any performance testing?

Simply say NO you have not done so and that performance testing was conducted by a separate Team.

What is Functional testing?

Simply testing any functionality is functional testing. Manual testers do functional testing.

What is the difference between system testing and integration testing?

System testing is when the entire system is checked such as hardware, software, servers, databases etc., whereas for integration testing, the integration between the individual modules is tested.

In which phase should testing begin: requirements, planning, design, or coding?

Testing should start at the requirements phase.

Testing process in your current project?

Testing starts when I receive my user stories after sprint planning meeting. First I analyze the user story and create subtasks. If a story requires only my input I start working on it, if it needs the development work then I wait for the developers to complete their work. Till I receive the story from the developer I create my test cases, start working on my automation script. And as soon as I receive the story from the developer I do manual testing first, and then finish up with the automation. If I see any issues I create a defect and assign it to the developer. When I complete my work I move the story from "in progress" to "done".

What is ETL testing?

The ETL or Extract, Transform, and Load process supports the movement of data from its source to storage (often a data warehouse) for future use in analyses and reports. And ETL testing ensures that nothing has been lost or corrupted along the way. (It's okay to say that you are not familiar with this type of testing)

How do you deal with a bug which is not consistently reproducible?

The best approach is to take a screenshot of it if you are using Snagit you can even capture video of it and note it down. Discuss the bug with the team so everyone can keep an eye on it.

Product backlog

The entire application that we want to develop and sort in user stories.

Sprint Backlog

The items that we are going to develop in a specific sprint.

How do you track your progress in a sprint?

The progress is tracked by a "Burn-Down chart". A burn down chart is a graphical representation of work left to do versus time

What kind of projects is suitable for the Agile Scrum methodology?

The traditional methodology is suited for projects with predefined, clearly stated requirements while agile development methodology is suitable for projects with dynamic requirements where frequent changes in the product come up on regular basis.

How many people are on your team or describe me your team?

There are 2 Automation Testers, 1 manual tester 4 Developers, 1 scrum master, 1 QA manager or product owner, 1 BA. *Tell them how many there are also mention we arg cross-functional team etc.

Why do Software Applications have bugs?

There are various reasons why a system might have bugs, such as bad design, coding errors, miscommunication, continues change in requirements, rushing to meet deadline and also the complexity of the application

What is Parking lot?

This usually comes up in meetings especially daily stand up but its basically a problem not relevant to others in meeting and don't want to discuss it to waste time there for a separate meeting can be arranged for it at a later time.

Explain what is Velocity in Agile?

Velocity is the sum of story points that a scrum team completes (meets the definition of done) over a sprint. It figures out how much work a team can complete in a sprint and how much time will it need to finish a project.

Can you tell me the Difference between Verification and Validation?

Verification is when vou are analyzing requirements and test cases to ensure we cover all scenarios and we are creating the right product and here there is no code involved. Simply reviewing documents to ensure everything is covered and NO coding is involved. -Validation is when we are executing our test cases and actually writing code to verify the system

How many bugs do you find a day?

We don't test every day since we have meetings and time must be allotted to creating test cases. When we do actual testing anywhere from 2 to 3 bugs a day at the very beginning and as we continue testing the bug rate falls to 0 to 1

When working in Agile team what was the team structure and what was your role there?

We have 1 PO, 1 BA, 1 Scrum Master, 1 Tech lead, 5 developers, 2 testers.

Who is responsible for writing test cases and test plans?

We testers write test cases for various scenarios, while test lead or even QA Manager is responsible for making a test plan.

Which tools do you use to create test cases?

When I first joined the team they were using HP ALM, but we gradually changed to Jira Xray (mention the one you learnt during the bootcamp, it's even okay do say your company was using excel sheet)

When do you choose automation testing over manual testing?

When you have complex functionality that is time-consuming. Automate test cases that are redundant for manual testers. High priority test cases. Smoke test cases and regression test cases.

How many months did you spent on doing Selenium Automation in the last year and the last six months?

Within the last year I've spent approximately 60% of my time on automation and the rest of the time in meetings, reviewing requirements, writing test cases, doing manual testing and so on

Experience in Selenium

Yes I do have good hands on experience in Selenium. I have been using Selenium Webdriver with Java programming language for automation.

Currently, you are working at __________ company which is not related to this job how can you relate or help our company?

Yes, I don't have the domain knowledge of this position, but I have testing experience. I know testing principals how to test, how to break a system and be detailed orientated to find issues in an application. Plus, I have done various type of testing that is common all across and are in practice.

Can you explain agile and how are agile practices implemented in your company?

Yes, in our company we have daily stand up every morning... also, we have sprint planning meeting where we discuss and allocate user stories. Towards the end of sprint we have a sprint demo and then we have retrospective where we talk about what went right and wrong etc.

Is it possible that you come across different story point for development and testing efforts? In that case how do you resolve this conflict?

Yes, this is a very common scenario. There may be a chance that the story point given by the development team is, say 3 but the tester gives it 5. In that case both the developer and tester have to justify their story point, have discussion in the meeting and collaborate to conclude a common story point.

What do you do if there isn't enough time for thorough testing?

You have to prioritize here, there are many scenarios: -Which functionality is most visible to the user? -Which functionality has the largest safety impact? -Which aspects of the application are most important to the customer? -Which aspects of the application can be tested early in the development cycle? -Which parts of the code are most complex and thus most subject to errors? -Which parts of the application were developed in rush or panic mode? -Which parts of the requirements and design are unclear or poorly thought out? -What do the developers think are the highest-risk aspects of the application? -What kinds of problems would cause the most customer service complaints? -What kinds of tests could easily cover multiple functionalities? -Which tests will have the best high-risk- coverage to time-required ratio?

About Agile process?

working in agile gives us flexibility. The team works in small increments called sprints. And the team is able to deliver the work in small chunks/deliverables. This helps the customer see the development work step by step and make changes or add new functionalities whenever needed.