1.
Describe a time you had to help a team transition from scrum to Kanban
because the nature of their work changed.
[Link] me about a time you had to dig into the technical details to uncover
the root cause of a recurring impediment that developers had missed.
what wee the learnings from doing it
[Link] a scenario where you used direct customer feedback to
convince the product ownere to pivot the priorities in the midle of life
cycle
[Link] a time you have to deal with team member who was cherry
picking all the easy tasks leaving the complex ones for the end of the
sprint.
[Link] the developers don't want daily scrum. What will you do
[Link] the scrum team together finds retrospective meetings as waste of
time even after your coaching,what solid points you present in fromnt of
them apart from actionable items.
[Link] do you deal with PO who is coming with scope changes very
frequently even after 4 to 5 sprints
[Link]
SOmetimes customers make unreasonable [Link] me about a time
when you have had to push back or say no
to a customer request
In one product I worked on,Customer asked for different report which was
already there in dashboard format.
Like the status of loan based on some input [Link] dashboard
which we have designed has got 6 to form of reports and the customer
expected some new report which is required for auditing .Since they are
huge data and changes to be done in multiple end,frontend,back end,
optimisation to be checked by [Link] Po we worked on alternatives,
like providing one time custom report like quick export in excel format
within shorter duration of [Link] is something added in middle of the
sprint and we just created a simple link with optimised query and
delivered in adhoc manner.
We then moved the above request with requiremets from customer,
created a backlog and moved the above report for the next sprint and
delivered it successfully
2.A new team member joins in the middle of the [Link] would you
onboard them effectively without distrupting the current flow
I d onboard them in a way that integrates them gradually without
distrupting the sprint [Link] orientation will be given with KT [Link]
usually record all the Kt to new joiners and the recorded sessions will be
moved across the corresponding folders based on POD [Link] includes
which access and access required for the team members .The newbie will
be able to understand the basic KT recording sessions,documents without
needing deep details upfront.
Pair them with experienced team members (buddy system)for hands on
[Link] start with low risk tasks in first 2 sprints like bug
fixes,configuration changes,documentation or shadowing ongoing
[Link] ensure PO is aligned so that expectations are realistic and and
we don't overload new joiners or disrupt [Link] the new team
member into the flow step by step.
Regular sync up with new team member to keep them focussed .
The only issue or risk is the velocity will go down initially based on
capacity as there is new change in team
[Link] Stakeholders request in frequently changing and timeline is critical
how we can negotiate w.r to quality/timeline
[Link] a time you had to help a team transition from scrum to Kanban
because the nature of their work changed
[Link] me about a time you had to dig into technical details to uncover the
root cause of a recurring impediment that developers had [Link]
were the learnings from it.
In one of the projects LOS system Based on Loan type the fee details will
be populated in grid format and in addition to that we can add more fee
type from fee drop [Link] populating the fee type in drop down the
process was slow and need to identify root [Link] issue was ignored
for a long time and while doing testing in lower environment it was too
[Link] is was identified in performance environment and decided to
look into the slowness.
As I have technical knowledge though of digging it and identified the root
[Link] is because of JavaScript file and where they have defined the sql
script with improper query [Link] this was the very old file no one
was ready to touch and debug the [Link] the Query clause got
changed the dropdown issue got resolved
[Link] is the role of SM in PI planning?How do you ensure your team sets
common goals and stays aligned with other teams
In PI planning scrum master acts as faciliatotr,alignment
enabler,impediment remover,ensuring the team is prepared with refined
backlog,clear capcity,known dependencies,while guiding discussions
owards realistic commitments and clear Pi [Link] the event
they help team to identify the dependencies,surface and ROAM
risks(Resolve,Own,Accept,Mitigate) and collaboatre effectively with other
[Link] maintain alignment they actively support cross team
coordination through sync events,ensure objective are otcome
driven .Enable teams to operate as cohesive system raher than isolated
units.