Interview Questions.

Scrum Master Interview Questions and Answers


Scrum Master Interview Questions and Answers

Q1. What is the scrum manner?

Ans: Scrum is an agile way to manage a mission, generally software improvement. Agile software development with Scrum is regularly perceived as a methodology; however as opposed to viewing Scrum as methodology, consider it as a framework for managing a procedure.

Q2. What form of process is a Scrum Master?

Ans: Scrum Master Job Descriptions and Responsibilities In Agile Methodology. ...Scrum grasp is a hard function and needs to understood in keeping with precedence set by means of the product proprietor. Scrum Master must execute the backlog as wanted by product owner, ensuring that deliverables are on time with production nice.

Q3. How is scrum specific from waterfall?

Ans: The most important variations are:

The remarks from client is obtained at an early degree in Scrum than waterfall, wherein the remarks from customer is received toward the give up of development cycle.

To accommodate the new or changed requirement in scrum is easier than waterfall.

Scrum makes a speciality of collaborative development than waterfall wherein the entire development cycle is split into levels.

At any point of time we are able to roll again the changes in scrum than in waterfall.

Test is taken into consideration as section in waterfall unlike scrum.

Q4. How do you make sure that the scrum crew has get entry to to a challenge’s stakeholders?

Ans: The candidate ought to take into account that there is no manner to ensure get entry to to stakeholders. All that may be achieved is to inspire stakeholders to interact in meaningful communique by being transparent and useful. Sprint demos are a beneficial mechanism for this, often promoting better relationships between one of a kind departments and commercial enterprise devices — improving a scrum team’s access to their initiatives’ stakeholders.

Q5. How is scrum different from Iterative version?

Ans: Scrum is a type of iterative version most effective however it's miles iterative + incremental.

Q6. Who need to be writing consumer testimonies?

Ans: Writing consumer stories have to be a joint effort made by means of the complete scrum crew. If it is now not, the team may not experience that they've ownership of the testimonies — inevitably main to less or no purchase-in, decreased motivation… and in the long run a lower-fine product.

Q7. What are the ceremonies you perform in scrum

Ans: There are 3 predominant ceremonies completed in Scrum:-

Planning Meeting – Where the whole scrum teams at the side of the scrum grasp and product owner meets and speak each object from the product backlog that they can work on the dash. When the story is expected and is well understood through the team, the story then movements into the Sprint Backlog.

Review Meeting – Where the scrum team demonstrates their paintings finished to the stake holders

Retrospective meeting – Where the scrum teams along with the scrum grasp and product proprietor meets and retrospect the ultimate dash they worked on. They majorly talk about three things:

What went nicely?

What can be accomplished better?

Action Items

Q8. What do you speak in Daily arise assembly?

Ans: We talk three things:-

What did I do these days?

What I plan to do the following day?

Any impediments / roadblock

Q9. What are the distinctive artifacts in scrum?

Ans: There are  artifacts maintained in Scrum:

Product Backlog – Containing the prioritized list of business necessities

Sprint Backlog – Contains the user tales to be performed through the scrum team for a sprint.

Q10. How do you measure the work accomplished in a dash?

Ans: It’s measured through Velocity.

Q11. What is Velocity?

Ans: Velocity is the sum of story points that a scrum team completes (meets the definition of done) over a sprint.

Q12. So in scrum which entity is answerable for deliverable? Scrum master or Product owner

Ans: Neither the scrum master, now not the product proprietor. It’s the duty of the group who owns the deliverable.

Q12. How do you measure the complexity or attempt in a dash? Is there a manner to determine and represent it?

Ans: Complexity and effort is measured via “Story Points”. In scrum it’s encouraged to apply Fibonacci series to represent it.

Q13. How do you music your progress in a sprint?

Ans: The development is tracked through a “Burn-Down chart”.

Q14. How do you create the burn down chart?

Ans: Burn down chart is a graph which indicates the expected v/s real attempt of the scrum responsibilities.

It is a tracking mechanism by using which for a selected dash; each day duties are tracked to test whether the tales are progressing toward the final touch of the dedicated story points or not. Here we ought to understand that the efforts are measured in terms of person memories and not hours.

Q15. What do you do in a dash assessment and retrospective?

Ans: During Sprint evaluation we walk via and show the function or tale implemented via the scrum crew to the stake holders.

During retrospective, we try to identify in a collaborative way what went nicely, what will be completed higher and movement gadgets to have continuous development.

Q16. What does a very good person story appear to be? What is its structure?

Ans: A suitable user story:

 has a description,

defines recognition standards,

can be introduced inside a single sprint, has all UI deliverables available,

has all (possibly) dependencies identified,

defines overall performance criteria,

defines tracking standards, and

is expected by using the group.

Q17. How do you address a product owner that assigns person memories or obligations to individual crew contributors?

Ans: Assigning duties to person team members does no longer paintings in any respect and desires to be stopped. The assignment of user testimonies is the scrum group’s prerogative. Preventing man or woman task undertaking, if possibly to occur, need to be one of the Scrum Master’s maximum urgent issues

Q18. Where does automation match into scrum?

Ans: Automation performs a essential role in Scrum. In order to have non-stop feedback and make certain a first-class deliverable we must try and put in force TDD, BDD and ATDD method all through our development. Automation in scrum isn't best associated with trying out however it is for all aspect of software improvement. As I said before introducing TDD, BDD and ATDD will speed up our improvement procedure along side retaining the high-quality requirements; automating the construct and deployment system will also speed up the function availability in exceptional surroundings – QA to manufacturing. As a long way as trying out is concerned, regression testing must be the only so that it will have maximum attention. With development of every dash, the regression suit continues on growing and it will become practically very difficult to execute the regression in shape manually for each sprint. Because we have the sprint duration of two – four weeks, automating it might be imperial.

Q19. Apart from making plans, review and retrospective, do  another ceremony in scrum?

Ans: We have the Product backlog refinement assembly (backlog grooming meeting) in which the crew, scrum grasp and product proprietor meets to apprehend the commercial enterprise requirements, splits it into consumer testimonies, and estimating it.

Q20. What is DoD? How is that this achieved?

Ans: DoD stands for Definition of achieved. It is achieved when

the story is improvement whole,

QA whole,

The tale meets and fulfill the reputation standards

regression around the tale is whole

The feature is eligible to be shipped / deployed in production.

Q21. What is MVP in scrum?

Ans: A Minimum Viable Product is a product which has simply the naked minimum required function which may be demonstrated to the stakeholders and is eligible to be shipped to manufacturing.

Q22. What are Epics?

Ans: Epics are equivocal person testimonies or we can say those are the consumer stories which aren't defined and are kept for destiny sprints.

Q23. How do you calculate a story factor?

Ans: A Story point is calculated by using taking into the consideration the improvement effort+ trying out effort + resolving dependencies and other factors that might require to complete a story.

Q24. Is it feasible that you come upon exceptional story factor for improvement and checking out efforts? In that case how do you clear up this struggle?

Ans: Yes, this is a very common scenario. There can be a danger that the story factor given by the development group is, say three however the tester offers it 5. In that case each the developer and tester must justify their story factor, have discussion inside the meeting and collaborate to conclude a common story point.

Q25. You are inside the middle of a dash and unexpectedly the product proprietor comes with a brand new requirement, what's going to you do?

Ans: In best case, the requirement will become a tale and moves to the backlog. Then based totally on the priority, group can take it up within the next sprint. But if the concern of the requirement is really high, then the crew will ought to accommodate it inside the sprint however it has to very well communicated to the stakeholder that incorporating a story inside the center of the dash may also result in spilling over few memories to the following dash.

Q26. In case you receive a story at the closing day of the dash to test and also you locate there are defects, what will you do? Will you mark the tale to achieved?

Ans: A tale is executed most effective while it's far development complete + QA whole + acceptance standards is met + it is eligible to be shipped into manufacturing. In this situation if there are defects, the tale is partly done and no longer completely completed, so I will spill it over to next sprint.