Agile Scrum Master Interview Questions and Answers

Looking to shift your career in Agile Scrum Master? Need some interview question and answers to get your dream job in the first attempt. Then we the Wisdomjobs will provide you with the complete details about the Agile Scrum master Jobs and interview Question and Answers on our site page.  To clear any interview, one must have a complete knowledge of all topics and one must know for which role they are going to attend the interview. If you are good at the Agile Scrum Master topics then there are many leading companies that offer job.

1.What is a test stub?

Ans:

A small code which mimics a specific component in the system and can replace it. Its output is the same as the component it replaces.

2.What is Sashimi?

Ans:

Sashimi is a Japanese word which means pierced body. Basically, it is a Japanese dish which consists of fresh meat or fish, sliced into thin pieces. Each piece is similar in taste when compared with the other pieces.

Sashimi in scrum methodology means every phase of the software development cycle in a sprint which includes requirement analysis, planning & design, development, testing, documentation is complete or not and the product is ready to be displayed, etc.

3.What is a Sprint Retrospective meeting?

Ans:

This is mostly the last part of the sprint or may be done after the sprint review meeting. Scrum master and the whole team participate in it, they discuss ‘ what was good during the sprint’,’ what was bad’,’ what needs to be improved’. It generally lasts for 2-3 hrs.

4.Why aren’t user stories simply estimated in man hours?

Ans:

Estimation of user stories on the basis of man-hours can be done but preferably not. You won’t be able to concentrate on the quality product to be delivered to the customer. Moreover, you will concentrate on cost and budget of the management while using man hours.

Instead of that, one can use story points, as it provides a complete idea about both the complexity of work and required efforts.

5.Is it ever suggested to use waterfall over Scrum?

Ans:

If yes, explain when.

Yes, sometimes it is suggested to use the waterfall model over Scrum. It is done when the customer requirements are simple, well-defined, fully understood, predictable, and are not subjected to change until the completion of the project. It may the case that you would haven’t ever used waterfall over Scrum but you need to prepare for such Agile Scrum interview questions.

6.What is a Daily Stand-up Meeting?

Ans:

Daily Stand-up Meeting is a daily routine meeting. It brings everyone up to date on the information and helps the team to stay organized.

Each team member reports to the peers the following:

1. 1.What did he/she do yesterday
2. 2.What are the impediments faced
3. 3.What he/she will do today

In general, it’s not a recorded meeting. Reporting will be between peers not to Scrum Master or Product Owner. It is normally timeboxed to a maximum of 15 minutes.

It is aka 15 Minute Stand-up Meeting.

7.What is the lifespan of the scrum cycle?

Ans:

The project size and team size are the two main factors which determine the time length of the scrum cycle. The size of a team can be 3 to 9 members. Usually, it can be estimated that the time span of a scrum sprint of about 3 to 4 weeks on average.

8.What are the disadvantages of the agile model?

Ans:

Some of the disadvantages of using an agile model are as follows:

a) Not easy to predict: When you encounter a large project, it is not easy to get an idea of how much effort will it need

b) If the guidelines given by the customers is not properly grasped, then the final outcome of the project is not customer satisfying

c) Sometimes focusing on design and documentation is not proper

d) High-level decisions are under the hand of Veterans, if not combined with non-experienced one, freshers have little scope to grasp proper knowledge.

9.What does the X and Y-axis of the burndown chart?

Ans:

In burn down, chart X-axis shows working days and Y-axis shows remaining efforts.

Project XYZ

Here, in the image blue line depicts the ideal time suggested for completing the project. For example in a project ideally, 28 tasks (efforts) are pending on the starting day of the project. And the project is scheduled to be completed in 20 days. So on the 20th day, zero tasks (efforts) should remain, which means the project should get completed.

On the other hand, the red line depicts the actual task (efforts) given with respect to the days. Here on day 5, 7 tasks need to be completed as per planning, however, in actual only 4 tasks were completed.

Thus, it provides proper tracking down of the progress of the project and thereby helps in improving the efficiency and on-time taken to deliver the project.

10.What are the main roles in the scrum?

Ans:

1) Scrum team:–

Scrum team is made by an individual person who works collectively to achieve a particular task. The team works in a bond to deliver committed and requested product

2)Scrum master:–

scrum master is responsible for the proper execution or working of the scrum team. Being a servant – leader and a coach, he ensures the proper productivity of a team towards scrum a sprint goal.

3)Product owner:–

product owner has the responsibility to deliver a complete picture of what to build and to convey that idea to the team

11.What are the places where Scrum and Kanban are used?

Ans:

When there is a need for shifting towards appropriate and prominent process then you use Scrum. When you need to improve the process that is running provided that there are not many changes then Kanban is used.

12.What are the most important agile Matrices?

Ans:

The following are the important agile Matrices.

Velocity – To have a clear about your progress, capacity and many more keeping track of the velocity is important. It can be measured by adding all the estimates of the stories that are approved.

Work category allocation – the work category allocation will provide a clear idea about where you are investing your time and also about the priority of the work.

Defect removal awareness – active members can produce quality products.

The cumulative flow diagram – the uniform flow of work can be checked thought this diagram of cumulative flow. Here the x-axis represents time and the y-axis stands for the number of effort.

• The sprint burndown matric – it helps in keeping track of the completion of the work with the sprint.
• Business value delivered – this is an entity that is concerned with the work efficiency of the team. It is used to measure and 100 points are associated with every project.
• Time coverage – it is defined as the amount of time that is given to code while it is being tested. This is measured with the help of the ratio of the number of lines of code that is called by the test suite by the number of relative lines of codes.
• Defect resolution time – this is a term which is concerned with the process in which team members detect bugs and also fixes them. There are a number of processes involved in fixing a bug.
  clearing the picture of the bug
  Schedule a fix
  Fixation of a defect is done.
  Report of resolution is handed.

13.What does a scrum burndown chart comprise?

Ans:

A scrum burndown chart should consist of

• X-axis that displays working days
• Y-axis that displays remaining effort
• Ideal effort as a guideline
• Real progress of the effort

14.What are the artifacts of Scrum process?

Ans:

Sprint backlog – The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment.

Product backlog – The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.

Velocity chart- A velocity chart shows the sum of estimates of the work delivered across all iterations. Typically, velocity will stabilize through the life of a project unless the project team make-up varies widely or the length of the iteration changes.

Burn-down chart – It is a chart that shows how quickly you and your team are burning through your customer’s user stories. It shows the total effort against the amount of work we deliver on each iteration.

Click here, to learn about online Agile Scrum training.

15.What do you know about Scrum ban?

Ans:

Scrum-ban is a Scrum and Kanban-based model for software development. This model is specifically used for the projects that need continuous maintenance, have various programming errors or have some sudden changes. This model promotes the completion of a project in minimum time for a programming error or user story.

16.What does the term scrum of scrums mean?

Ans:

There are 7 teams appointed on a particular project and let us consider that each team has got 7 members each. A particular team will conduct their own scrum meetings. In order to have coordination among the teams, another separate meeting is held and this is known as a scrum of scrums. The person who will present the team in the scrum of scrums is an ambassador. In the meeting g the points that are discussed are:-

After the last meeting how far the team has progressed.

17.What do you mean by planning poker or scrum poker technique?

Ans:

The technique which is a card-based estimation based on a general agreement is known as scrum poker or planning poker. Some features of it are:-

• The first step is to story of the agile user is read by the customer or owner. Then the estimator understands the features.
• There are different planning cards with a different number for each estimator. The different numbers are the story points.
• Based on the estimation which is done by discussing features, the estimator will select a card.
• When a common value is selected then it is considered to be an estimate otherwise there is a discussion on maximum and minimum estimation.
• Until a general agreement is reached this process is repeated.

18.What do you mean by the disadvantages of the agile model?

Ans:

There are certain disadvantages of the agile system which are discussed below.

• It is not easy to predict. If a big project is assigned you will have a problem to estimate the effort you need to put into that.
• Focusing on design and documentation is not always proper.
• The final product will not satisfy the customers if the guidelines given by the client are not properly understood.
• The high-level decision making is in the hands of the higher authorities which makes the fresher to have little knowledge.

19.What is the role of the Scrum Master?

Ans:

Here’s how you can answer Scrum Master interview questions like this –

The scrum master is the leader as well as coach of the Scrum team. The scrum master is responsible to serve and protect his team from any kind of distractions that could affect their performance. The main role of the scrum master is to motivate his team to achieve the sprint goal. He is focused to build a self-organized and motivated team where each member is familiar with the implementation of Agile and Scrum principles and applications. The scrum master keeps a proper check on the scrum team if they are executing committed tasks properly. He is also responsible to increase the efficiency and productivity of the team so that they can achieve the sprint goal effectively.

20.What do you understand by the term “Scrum of Scrums”?

Ans:

This is one of the commonly asked scrum master interview questions. Consider a case to understand the meaning of the term scrum of the scrums. Let us assume an active project on which seven teams are currently working. The number of members of each team is also seven. Each team is responsible to lead its own scrum meeting. But, in order to coordinate and communicate with different teams, it is required to organize a separate scrum meeting. The scrum meeting organized to hold coordination between scrum teams is known as the scrum of scrums. There is one team leader from every team, known as an ambassador, who is responsible to represent his team in the scrum of scrums.

21.What do you know about impediments in Scrum?

Ans:

Impediments are the obstacles or issues faced by the scrum team which slows down their speed of work. If something is trying to block the scrum team from their getting work “Done” then it is an impediment. Impediments can come in any form. Some of the impediments are given as

• Resource missing or sick team member
• Technical, operational, organizational problems
• Lack of management supportive system
• Business problems
• External issues such as weather, war, etc
• Lack of skill or knowledge

While answering impediments related agile scrum interview questions remember that you may be asked the way to remove any of the mentioned impediment.

22.Name some methodologies and development where you have used Agile model?

Ans:

While answering this type of agile scrum interview questions, keep in mind to mention those methodologies that are familiar with.

Some of the methodologies and development where Agile model can be used are:

• Crystal methodologies
• Lean software development
• Dynamic development
• Feature-driven development

23.How do you know if you are using agile development?

Ans:

Whenever you are using certain things like Test-driven development, time-boxed task board, class responsibilities collaborators, daily stand up meeting, pair programming, continuous integration, reviews and much more… you will get to know that you are using agile development.

24.What do you mean by sprint retrospective meeting?

Ans:

Sprint retrospective meeting is the last part of the sprint. It is probably done after the review meeting of a sprint. The whole teams along with scrum master participate in this discussion and it lasts for 2 to 3 hours.

25.What is the difference between the agile & traditional way of working?

Ans:

This question is to judge whether one is aware of the environment of the agile way of working. Here the answer is expected to cover few or all of below:

The traditional way is sequential where design-> Development-> Testing etc. happen one after another whereas in agile all of this is done in every iteration/sprint

Changes are welcomed in agile as Scope is flexible whereas in traditional manner scope is fixed in the beginning due to which changes have to follow change request path

Progress is measured with % completion traditionally whereas working software is the measure of progress in agile

Project Manager as a central controlling authority is traditionally driving the project whereas Self-motivated and self-organizing teams drive the projects in agile. 

26.What are the responsibilities of a Scrum Master?

Ans:

Key responsibilities of a Scrum Master involves:

• Tracking and monitoring
• Understanding requirements properly
• Work to reach the project goal
• Process checking master and quality master
• Protect the team from detachments
• Improving the performance of the team
• Lead the meetings and resolve issues
• Resolution of conflicts and impediments
• Communication and reporting

27.How does agile testing (development) methodology differ from another testing (development) methodologies?

Ans:

The testers (developers) ensure that the whole process of testing (development) is broken into small steps as possible, and just a small unit of code is tested (developed) in each of these steps. The team of testers (developers) consistently communicates the results of their work and changes the short term strategy and even the development plan on the go, based on the results of agile testing. The agile methodology encourages a flexible and rapid response to change, which should lead to better end results.

28.How much time should a person expect to spend on Scrum Master activities?

Ans:

A ScrumMaster should make this role their top priority to focus on the benefits of the overall team. Their load will vary from sprint to sprint depending on what impediments and issues the team are dealing with. Newly formed teams typically take more ScrumMaster time; 50%-100%, while experienced ScrumMasters with established well functioning teams might spend 50% or less time on the ScrumMaster role.

29.What is the difference between Epic, User stories & Tasks?

Ans:

An epic is a group of related user stories.

User Stories define the actual business requirement. Generally created by the business owner.

Task: To accomplish the business requirements, development team create tasks.

30.What is the difference between the Sprint Planning Meeting and Sprint Retrospective Meeting?

Ans:

The difference between the Sprint Planning Meeting and Sprint Retrospective Meeting is as follows:

Sprint Planning Meeting – A meeting in which all the Scrum roles (product owner, scrum team, and scrum master) have a discussion about the team’s priority features and product backlog items is known as a sprint planning meeting. This meeting is held every week and lasts for almost 1 hour.

Sprint Retrospective Meeting – A meeting in which all the Scrum roles (product owner, scrum team, and scrum master) have a discussion about the good part of the sprint, the bad part of the sprint, and the sprint improvements is known as sprint retrospective meeting. This meeting that is held at the sprint review meeting or at the end of the sprint; it lasts for 2-3 hours.

This is one of the frequently asked Agile Scrum interview questions. You may be asked to define the above terms separately or the difference between these two.

31.What is the difference between agile & scrum?

Ans:

This question will test whether you are aware of a broader picture of agile and its different frameworks or flavors. Below image will help you explain this answer where you can say agile is an umbrella of values and principles and under it, one of the lightweight frameworks is called Scrum.

• Difference between Agile and Scrum
• Certification-related Agile Scrum Interview Questions

Certifications have become very important these days. Although it’s not compulsory to have a certification for any job position but it demonstrates your skills to the employers. So, interviewers include these certification-related agile scrum interview questions in an agile scrum interview.

32.Do you have a Scrum Master certification?

Ans:

This question may seem awkward to you but it is one of the most popular Agile Scrum interview questions. If an interviewer asks this question, it doesn’t mean that certification is must for the job position. Just be confident while answering whether you have a scrum master certification or not. If you are a certified scrum master, just share the details of your certification like certification exam, score obtained, and the year of passing the certification exam. In case you don’t have a certification, mention and highlight your

(company) experience in the particular field. Also, let the interviewer know if you are planning to invest in the certification in the near future.

33.How to measure velocity if our iteration lengths change?

Ans:

You can’t measure it easily. Velocity’s value comes from its inherent consistency. A fixed iteration length helps drive the reliable rhythm of a project. Without this rhythm, you are constantly revising, re-estimating, and reconciling, and the ability to predict out in the future is minimized due to inconsistent results.

If, on the other hand, almost everyone is going to be out a week for the holidays or a couple of days for company-wide meetings then, by all means, adapt iteration dates or velocity accordingly. Like most agile practices, these are guidelines, not strict rules.

34.What square measures the principles of agile testing?

Ans:

Some major principles of agile testing are:

• Customer satisfaction
• Face to face communication
• Sustainable development
• Quick answer changes
•  Continuous feedback
• Successive improvement
•  Self-organized
• Focus on essence
• Error-free clean node
• Collective work

35.What square measure the 2 key factors once operating as a QA in an associate Agile team?

Ans:

QA will add lots useful to associate an agile team due to the various mindsets. Testers will and will admit the various doable situations to check a story.

But the foremost vital plus that they will bring is:

To forestall defect: QA ought to advocate best practices on the thanks to forestalling defects from getting into the system within the 1st place.

To offer quick feedback: it’s vital for developers to grasp if the new practicality works evidently and if regression tests pass, and that they would like that feedback quite quickly. QA ought to offer the results of the tests to developers as shortly as doable.

36.What are impediments?

Ans:

Any hindrance that prevents the sleek flow of labor or because of that the team isn’t able to perform its task in an exceedingly higher manner is what we tend to decision ‘impediments’.

37.What is the scrum of scrums?

Ans:

Suppose there are 7 teams working on a project and each team has 7 members. Each team leads its own particular scrum meeting. Now to coordinate among the teams a separate meeting has to be organized, that meeting is called Scrum of Scrums.

Scrum of Scrums

An ambassador ( a designated person who represents team) represents its team in the scrum of scrums.

Few points discussed in the meeting are:

(a)The progress of the team, after the last meeting.

(b)The task to be done before the next meeting.

(c)Hindrance which the team had faced while completing the last task.

38.Describe the places where ‘Scrum’ and ‘Kanban’ are used?

Ans:

‘Scrum’ is used when you need to shift towards more appropriate or more prominent process while if you want improvement in running the process without much changes in the whole scenario, you should use ‘Kanban’

39.Should scrum master remove impediments on behalf of the scrum team?

Ans:

The scrum master can do that, but he should not. The scrum master should neither over-rule nor pamper his/her team. Initially, there may be chances of failure, unplanned excursions or dead-end where the team can trap, here scrum master should support them and show the proper way of getting out of it. A scrum team should be independent to take its own decision.\

40.What are the principles of Agile Software Development?

Ans:

1. 1.Highest priority is to satisfy the customer through early and continuous delivery of business valuable software
2. 2.Welcome changing requirements, even late in development
3. 3.Deliver working software frequently
4. 4.Business people and developers must work together with transparency on a daily basis throughout the project
5. 5.Build projects around motivated individuals
6. 6.The best form of communication is to do face-to-face conversation
7. 7.Working software is the primary measure of progress
8. 8.Able to maintain a constant pace
9. 9.Continuous attention to technical excellence
10. 10.Simplicity – the art of maximizing the amount of work not done – is essential
11. 11.Self-organizing teams
12. 12.At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly

41.What are the main roles in Scrum?

Ans:

Scrum consists of three main roles:

Product Owner:

Product Owner usually represents the Client and acts as a point of contact from the Client side. The one who prioritizes the list of Product Backlogs which Scrum Team should finish and release.

Scrum Master:

Scrum Master acts as a facilitator to the Scrum Development Team. Clarifies the queries and organizes the team from distractions and teach the team how to use scrum and also concentrates on Return on Investment (ROI). Responsible for managing the sprint.

Scrum Development Team: Developer’s, QA’s. Who develops the product. Scrum development team decides the effort estimation to complete a Product Backlog Item.

Scrum Team:

A cross-functional, self-organizing group of dedicated people (Group of Product Owner, Business Analyst, Developer’s and QA’s). The recommended size of a scrum team is 7 plus or minus 2 (i.e, between 5 to 9 members in a team).

42.What is a Sprint?

Ans:

In Scrum, the project is divided into Sprints. Each Sprint has a specified timeline (2 weeks to 1 month). This timeline will be agreed by a Scrum Team during the Sprint Planning Meeting. Here, User Stories are split into different modules. The end result of every Sprint should be a potentially shippable product.

43.What is Defect Burndown Chart?

Ans:

A graph which shows how many defects identified and fixed.

44.What is a Sprint Planning Meeting?

Ans:

The first step of Scrum is the Sprint Planning Meeting where the entire Scrum Team attends. 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 effort estimation.

45.What is a Sprint Review Meeting?

Ans:

In the Sprint Review Meeting, Scrum Development Team presents a demonstration of a potentially shippable product. Product Owner declares which items are completed and not completed. Product Owner adds the additional items to the product backlog based on the stakeholder’s feedback.

46.Is it possible to apply agile methodology another testing apart from software testing and development testing?

Ans:

The methodology of a file testing can be applied in case of biophysics, biochemistry, biomedical and those places that have insufficient data and the project needs to complete with a small team.

47.What does story point mean in the scrum?

Ans:

The unit that is used to estimate the total effort which is needed to finish or do a particular work or implementing a backlog is referred to as a story point in the scrum.

48.What do you mean by the X and Y-axis of the burndown chart?

Ans:

In the burndown chart, the X-axis represents the working days and the Y-axis stands for showing the remaining efforts.

49.Can agile methodology also be applied in other than software testing and development projects?

Ans:

There are several places where agile methodology can be applied in the field of biochemistry, biophysics, bio-medical or at the place where there is insufficient data, where the project needs to be completed in a small team, where to work in unknown and there are several areas.

50.What is Zero sprint in Agile?

Ans:

It can be defined as pre-step to the first sprint. Things like setting up the development environment, preparing backlog etc needs to be done before starting of the first sprint and can be treated as Sprint zero.

51.What do you know about Kanban?

Ans:

A tool which is used in helping the team to overlook the work which includes its progress is known as Kanban. Along with progress, the status of the current development story is also described by Kanban and it is done by Kanban board.

52.What is your view on scrum master removing impediments for the scrum team?

Ans:

The scrum master can remove impediments on behalf of the scrum team but he should not do that. The scrum master should not pamper nor overrule the scrum team. Also, the scrum team should be able to make their own decisions…

53.What is pair programming?

Ans:

Pair programming is an Agile technique in which two programmers team up to solve a problem. 

However, pair programmers coordinate better than Tracy and Jenna. 

They even share a computer, keyboard, and mouse. 

The one with the keyboard is known as the ‘director’ or ‘driver’ and leads the learning for the other programmer, who is known as the ‘observer’ or ‘navigator’. They also switch roles to maximize learning and engagement. 

However, just like the Tracy-Jenna combo, pair programming is not without its pitfalls.

Pair programming is known to slow down learning rather than speed it up. It also dials up the cost of operating as it increases the number of man-hours taken per task.

54.Is Scrum different from Agile? How?

Ans:

Scrum derives a lot of its working principles from the Agile methodology. 

But it’s not the same as Agile. 

Here are the key differences between the two:

• The Scrum framework is only applicable to Scrum teams, whereas any small team can become an Agile development team  
• An Agile team has a more centralized leadership structure, with a major share of the responsibilities resting on the shoulders of the product or project owner
• The Scrum framework takes Agile’s bias for speed and experimentation a few steps further and makes space for independent, self-sufficient teams. Teams make several decisions by themselves — the Scrum master role is only to guide them on the Scrum principles. 

55.Describe the process in the Agile Scrum methodology?

Ans:

Scum is a cyclical process. 

Each Scrum sprint is repeated until the product is refined and released in its final form to the customer. 

For example,

let’s say that Liz asks you to build an app to help her manage the team better. 

Your Scrum cycle will start by first understanding and documenting her requirements thoroughly. 

In the production stage, you’ll start developing the product in short sprints of two to four weeks each. 

After each Scrum sprint, the current version of the software will be tested with its target audience. In this case, it’s Liz and her writers. 

Using the team’s feedback, you’ll start the next Scrum sprint. And just like that, you’ll be closer to a more focused, feedback-driven product with each Scrum cycle!

56.Who are the different people involved in a Scrum process? 

Ans:

A Scrum project is like a live sketch comedy show: you need everyone to make it happen!

Product owner :

The product owner is responsible for understanding customers’ needs and communicating them to the team. They lead the whole Agile development process and lay the groundwork in the form of ‘user stories’. 

Scrum master role :

The Scrum master guides the team about the nuances of the Scrum process. The Scrum master role also supports the project owner and facilitates Scrum meetings if needed. 

Development team :

Includes multi-skilled, self-organizing developers who build the product from scratch. Typically, they’re software developers. But the development team can also include researchers, analysts, designers, or anyone who’s directly contributing to the product.

57.What kind of Agile management software can help you manage a Scrum project?

Ans:

Your usual Agile Scrum interview not only tests your theoretical understanding of the methodologies but also how you can implement it realistically. 

And part of that is knowing what kinds of software can support an Agile project manager.

While you have many options available in the market, you deserve nothing but the best. 

58.What are the key Scrum ceremonies?

Ans:

Every team needs occasions to come together: to communicate, plan ahead, and reflect. 

And there’s a Scrum ceremony for each of these purposes.

The five key Scrum ceremonies are:

Sprint planning meeting :

These meetings kickstart the sprints and are usually spearheaded by the product owner. The sprint planning meeting gives the team the sprint backlog and a clearly defined sprint goal to work towards. 

Daily standup or daily Scrum :

A standup or a daily Scrum meeting is how each day begins for a Scrum team. The team stands together for up to 20 mins around the Scrum board to discuss the day’s agenda and any roadblocks they might be experiencing. 

Product backlog refinement:

Here, the team comes together to discuss if they’re dealing with each product backlog item in the right order. Led by the product owner, any changes to the product backlog are made in these meetings.

Sprint review :

Once the sprint is over, the team meets with the key stakeholders to present a working version of the software and receive their feedback. 

Sprint retrospective :

In a sprint retrospective, the team does an internal review of their processes and performance during the sprint.

59.What is the Scrum methodology? 

Scrum is an Agile management framework that emphasizes customer collaboration to speed up software development.

While it has its roots in the tech world, the Scrum framework has also proven to be effective in teams like marketing and sales. 

The Scrum methodology is made up of 3 important elements:

• Scrum artifacts: help keep the Scrum team as well as the stakeholders on the same page about the development process. These artifacts include the product backlog, sprint backlog, and product increment.
• Scrum roles: include the product or project owner, Scrum master, and the development team
• Scrum events: frequent events that tie the whole project together. Also known as Scrum ceremonies, it includes the sprint planning meeting, daily Scrum, product backlog refinement, sprint review, and the sprint retrospective.

With all these various elements, the Agile Scrum methodology can foster better collaboration among the team and adapt to any challenge in its way.