Filter interviews by
I applied via Job Portal and was interviewed in Nov 2023. There were 2 interview rounds.
I applied via Referral and was interviewed in Aug 2024. There was 1 interview round.
Experienced Scrum Master with a background in software development and a passion for facilitating team collaboration and continuous improvement.
Over 5 years of experience as a Scrum Master in various software development teams
Certified Scrum Master (CSM) with strong knowledge of Agile principles and practices
Facilitated daily stand-up meetings, sprint planning, sprint reviews, and retrospectives
Worked closely with Prod...
I handle a team of 7 members and manage them by facilitating daily stand-ups, sprint planning, retrospectives, and removing impediments.
Facilitate daily stand-ups to keep the team aligned and focused on sprint goals
Lead sprint planning meetings to prioritize tasks and set achievable goals
Conduct retrospectives to reflect on what went well and what can be improved for the next sprint
Remove impediments that are blocking ...
Scrum is time-boxed with fixed iterations, while Kanban is continuous flow with no fixed time-boxes.
Scrum has fixed iterations called sprints, while Kanban has no fixed time-boxes.
Scrum focuses on completing a set amount of work within a sprint, while Kanban focuses on continuous delivery of work.
Scrum limits work in progress by setting a sprint goal, while Kanban limits work in progress based on capacity and flow.
Scru...
Resolved conflicts related to task prioritization, communication issues, and team member disagreements.
Facilitated discussions to prioritize tasks based on business value and team capacity.
Addressed communication breakdowns by encouraging open dialogue and active listening.
Mediated conflicts between team members by helping them understand each other's perspectives.
Implemented team agreements and ground rules to prevent...
Managed risks in sprints by identifying, assessing, and mitigating potential issues to ensure successful delivery.
Identified potential risks at the beginning of the sprint through team discussions and retrospectives
Assessed the impact and likelihood of each risk to prioritize mitigation efforts
Mitigated risks by implementing proactive measures such as adjusting sprint scope or increasing communication
Example: Identifie...
KPIs are Key Performance Indicators used to measure the success of a project. Examples include velocity, sprint burndown, and team happiness.
KPIs are metrics used to evaluate the performance and success of a project
Common KPIs in Agile projects include velocity, sprint burndown, and team happiness
KPIs help teams track progress, identify areas for improvement, and make data-driven decisions
I applied via Approached by Company and was interviewed in May 2024. There were 4 interview rounds.
Team success in Scrum can be measured through various metrics such as velocity, sprint burndown charts, and team satisfaction.
Velocity: Measure the amount of work completed in each sprint. A consistent increase in velocity indicates team success.
Sprint burndown charts: Monitor how well the team is progressing towards completing the sprint goal. A steady burndown chart shows success.
Team satisfaction: Conduct regular re...
I applied via LinkedIn and was interviewed in Sep 2024. There was 1 interview round.
Agile principles are a set of values and beliefs that guide the Agile methodology in software development.
Customer satisfaction through early and continuous delivery of valuable software
Welcome changing requirements, even late in development
Deliver working software frequently, with a preference for shorter timescales
Collaboration between business people and developers throughout the project
Supportive and trusting envir...
Agile ceremonies are regular meetings that help teams collaborate, plan, and review progress in Agile projects.
Examples include Daily Standup, Sprint Planning, Sprint Review, and Retrospective
These ceremonies help teams stay aligned, communicate effectively, and continuously improve
Each ceremony has a specific purpose and timebox to ensure efficiency and productivity
I applied via Naukri.com and was interviewed in May 2024. There was 1 interview round.
I applied via Approached by Company and was interviewed in Jan 2024. There was 1 interview round.
The Agile Manifesto talks about the anti-pattern of excessive documentation.
The Agile Manifesto values 'Working software over comprehensive documentation'.
This principle emphasizes the importance of focusing on delivering working software rather than spending excessive time on documentation.
Excessive documentation can lead to delays, miscommunication, and reduced flexibility in responding to change.
Teams should aim to ...
I applied via Approached by Company and was interviewed in Jan 2024. There was 1 interview round.
The product backlog is a prioritized list of user stories, features, and enhancements that need to be developed.
It is a dynamic document that evolves throughout the project.
Items in the backlog are ordered based on their value and priority.
The backlog is constantly refined and updated by the product owner and development team.
It serves as a communication tool between the stakeholders and the development team.
Examples o...
Sprint review is a Scrum event where the development team presents the completed work to stakeholders.
Sprint review is held at the end of each sprint
It is an opportunity for the development team to showcase the completed work to stakeholders
Stakeholders provide feedback and suggest changes
The product owner determines what to do with the feedback and updates the product backlog accordingly
The outcome of the sprint revie
The sprint backlog is a list of tasks that the development team plans to complete during a sprint.
It is created during the sprint planning meeting.
It contains the user stories or product backlog items that will be worked on during the sprint.
Each task in the sprint backlog is estimated and assigned to a team member.
The sprint backlog is a dynamic document that can be updated throughout the sprint.
It helps the team to t...
CI/CD process automates software delivery and deployment
Continuous Integration (CI) involves developers regularly merging their code changes into a shared repository
Continuous Deployment (CD) automates the deployment of code changes to production after passing automated tests
CI/CD pipelines use tools like Jenkins, GitLab CI/CD, or GitHub Actions to automate the process
Benefits include faster delivery, reduced errors, a
fresher
3
salaries
| ₹1.7 L/yr - ₹6.5 L/yr |
TCS
Accenture
Wipro
Cognizant