EXL Service Interview Questions and Answers

We cater risks, releases and planning by implementing a comprehensive project management approach.

• Identify potential risks and develop mitigation strategies

• Create a detailed project plan with clear timelines and milestones

• Regularly review and adjust the plan as needed

• Use agile methodologies to facilitate frequent releases and adapt to changing requirements

• Communicate effectively with stakeholders to ensure alignment and manage expectations

Client change requests during sprint require careful consideration and communication.

• Assess the impact of the change request on the sprint goals and timeline.

• Discuss the change request with the product owner and development team to determine feasibility and prioritize.

• Communicate the potential impact of the change request to the client and negotiate a solution.

• Update the sprint backlog and adjust sprint goals and timeline if necessary.

• Ensure that all stakeholders are informed...read more

Class is a blueprint for creating objects. Objects are instances of a class. 2nd maximum can be found by sorting array and returning the second last element. Stack data structure is used in browser history, undo-redo operations, etc.

• Class is a template for creating objects with similar properties and methods

• Objects are instances of a class that can have unique values for their properties

• To get 2nd maximum from an array, sort it in descending order and return the second elemen...read more

MoSCoW prioritisation is a technique used to prioritize requirements based on their importance.

• MoSCoW stands for Must have, Should have, Could have, and Won't have.

• Must have requirements are critical and must be included in the project.

• Should have requirements are important but not critical.

• Could have requirements are desirable but not necessary.

• Won't have requirements are not included in the project.

• This technique helps in making informed decisions about which requirements t...read more

Dependencies can be identified by analyzing the relationships between tasks and their impact on each other.

• Review project scope and objectives to identify tasks

• Determine which tasks are dependent on others

• Identify the impact of one task on another

• Use a dependency matrix or network diagram to visualize dependencies

• Communicate dependencies to team members and stakeholders