[ INFOSYS ] scrum master interview question I scrum master interview questions and answers

preview_player
Показать описание
In This Video, we shared REAL scrum master interview questions and answers I scrum master interview questions I agile interview asked during the Actual Interview.
⭐🦸🏻‍♂️Helpful Agile Books which every scrum master should have🦸🏻‍♂️⭐
----

#ScrumMaster #scrummaster #interviewquestions #agile @CareersTalk #scrummaster #agilecoach #agilescrum #interviewquestionsforscrummaster
00:00 Intro
02:00 scrum master interview questions ,
07:00 basic scrum master interview questions,
10:00 scrum interview questions,
17:00 scrum master interview questions and answers,
25:00 scrum master interview,
26:00 advanced level scrum master interview questions,
28:00 agile scrum interview questions,
29:00 real world based scrum master interview questions,
30:00 project manager interview questions,
31:00 agile interview questions,
32:00 how to prepare for a scrum master interview.
scrum master job description, master person specification, scrum master, scrum master role, scrum master exam, agile scrum master, scrum master roles, what is scrum master, scrum master training, scrum master tutorial, certified scrum master, scrum master explained, scrum master full course, scrum master simplilearn, professional scrum master, scrum master
Рекомендации по теме
Комментарии
Автор

⭐🦸🏻‍♂️Helpful Agile Books which every scrum master should have🦸🏻‍♂️⭐
----

CareersTalk
Автор

60 story points need 3 sprints then The Average velocity is 20, so to complete 120 story points, we need another 6 sprints. Since agile works in an adaptive way, velocity can improve by continuous improvement, and it can finish earlier or maybe late up to 7 sprints due to other factors like team size, prioritization, blockers, uncertainty, and complexity.

AshishSingh-tycs
Автор

First and foremost we need to check if it is a similar type of feature technically based on complexity, so can use relative estimation. Here Avg velocity is 20 ( which includes the buffer, Planned leaves of the team) If there are no major changes in the capacity and have no external dependencies, The feature should be completed in less than or equal to 6 sprints considering it's a similar work done earlier.

bhanuchander
Автор

The velocity is 20, so to complete 120, by arithmetic should take another 6 sprints. But it depends of lot of other factors, stories prioritization etc. Since agile works in adoptive way, velocity can improve by continuous improvement, and it can finish earlier too.

bipulbhattacharya
Автор

I would say six sprints but I will tell 7 with the keep in mind extra sprint in case of any technical debt, dependencies or vuca( volatility, uncertainty, complexity and ambiguity) of the features.

worldtraveller
Автор

Efficiency factor for the cone of uncertainty is one thing I consider along with historical velocity while calculating future sprints.

Ex: if efficiency factor is 0.8 then the planning velocity becomes 16.

Now then the number of sprints needed for completing the epic = 120/16 = around 8 sprints.

suhasbankapur
Автор

If you take the average, it will be completed in 6 sprints keeping these factors in mind: historical velocity, team capacity, skillset, story complexity, dependencies and any unforseen risks

sabaakhter
Автор

As per provided data it will take around 6 sprints ... factors like capacity of the developers (if some devloper join and leave the team or if someone take holidays for some reason ), nature of story pints or tasks, upcoming holidays etc. can affect this prediction ..

deeptitrivedi
Автор

First, we have to take into consideration if there are no high priority stories lined up for incoming sprints and there are no external dependency for this feature so as avg. velocity is 20, ideally it shall take 6 sprints to complete it.
But as we take into consideration the non-availability of resources in release date planning for the complete project and not specific stories/features so we also have to see if the resources who are responsible in creating that feature are available over the next 6 sprints.

rajatchilana
Автор

Main information missing here is 60 is 3 sprints but breakup by each sprint is very much required to get a better prediction.

srinivasmallik
Автор

Using the data provided, In order to complete the 120 story points we will estimate to the work to be completed in 2 sprints considering that the capacity does not change during this time, no new member is being added to the team and no one left the team. Also no dependencies arising and no additional feature is brought in by the PO

peterebane
Автор

I will be able to confirm that it might take 5 to 6 Sprints as the 20 SPs are burned at the end of early sprints. Which also involves on the capacity, Tech depts and risk factor will taken to consideration.

ramarajnm
Автор

Sprint acceleration can count and estimated

SrikanthM_
Автор

6 sprint required as per the current runrate. it also depends velocity, Complexity and dependency of remaining story points

DfFg-qhub
Автор

We know how many team members work in past sprints and we need to check the release plan. So that we can plan for the upcoming sprints and resource. If we have enought time will go with same team with out any change in scrum team will complete in 6 to 7 sprint or we need find the experience person to support the team to meet the time line.

MrMunna
Автор

Considering no change in capacity, no major blockers or dependencies the feature will be ready after another 6 sprints.

savvy
Автор

20 so per sprint..for 120 it will be 6 sprint. Addition 1 sprint in case holidays and capacity issue😊

nitinrao
Автор

It would require 6 sprints as there is no change in resources and no new requirements added by stalkholder/ PO

Ananya-mb
Автор

3 sprints for 60 story points ' for another 120 story points..an average of 6 sprints is required .but what shud be in production ?

vasanth